Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.uwa.edu.au!nodecg.ncc.telecomwa.oz.au!netbsd08.dn.itg.telecom.com.au!orca1.vic.design.telecom.com.au!picasso.cssc-syd.tansu.com.au!wabbit.cc.uow.edu.au!metro!news.cs.su.oz.au!news.adelaide.edu.au!gateway.dircsa.org.au!cleese.apana.org.au!apanix.apana.org.au!hart
From: hart@apanix.apana.org.au (Leigh Hart)
Newsgroups: comp.os.386bsd.questions
Subject: Re: NetBSD-current and ed0: NIC memory corrupt errors
Date: 7 May 94 14:32:04 GMT
Organization: Apanix Public Access Unix, +61 8 373 5485 (5 lines)
Lines: 44
Message-ID: <hart.768321124@apanix.apana.org.au>
References: <2qcbag$f5t@aggedor.rmit.EDU.AU> <2qg7hf$c50@cleese.apana.org.au>
NNTP-Posting-Host: seldon.apanix.apana.org.au
newton@cleese.apana.org.au (Mark Newton) writes:
>In article <2qcbag$f5t@aggedor.rmit.EDU.AU>, Glen Pill (rxtgep@geppc.xx.rmit.edu.au) wrote:
> > Has anyone found a solution to this problem...
> > ed0: NIC memory corrupt - invalid packet length 65535
> > ed0: is a SMC Ultra
> > ed0 at isa0 port 0x280-0x29f iomem 0xe0000-0xe3fff irq 10:
> > address 00:00:c0:ce:a8:83, type SMC8216/SMC8216C (16-bit)
>I get the same thing with an NE2000:
>Apr 27 01:18:03 cleese /386bsd: ed0: remote transmit DMA failed to complete
>Apr 27 01:18:03 cleese /386bsd: ed0: NIC memory corrupt - invalid packet length 19969
>Apr 27 01:18:03 cleese last message repeated 4 times
>Apr 27 01:18:19 cleese /386bsd: ed0: remote transmit DMA failed to complete
>Apr 27 01:18:19 cleese /386bsd: ed0: NIC memory corrupt - invalid packet length 19969
>Apr 27 01:18:19 cleese last message repeated 2 times
>Apr 27 01:18:19 cleese /386bsd: ed0: NIC memory corrupt - invalid packet length 20225
I get exactly the same with my NE2000 (FreeBSD also)
>It doesn't appear to actually do any harm; the system continues to
>network just fine after the errors appear on the console (I should hope
>so! It's acting as a mail and news hub for 60-odd other systems :-).
In my case it does do plenty of harm, ftp seems to be the main cause
of these errors (or fast traffic anyway) and it only happens in one
direction - the transfers bog down to 1-2k/second and sometimes
lockup completely.
>Is it worth worrying about?
It is in my case :(
Cheers
Leigh
--
Leigh Hart
C/- PO Box 758
North Adelaide SA 5006
hart@eppie.apana.org.au hart@apanix.apana.org.au hart@cleese.apana.org.au