Date: Tue, 30 Dec 1997 10:37:08 -0500 (EST) From: Sam Magee <webadmin@adsight.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: Errors with DEC 21040 NIC in 2.2-stable Message-ID: <Pine.BSF.3.96.971230103458.11208B-100000@adsight.com> In-Reply-To: <199712291806.TAA15038@dorifer.heim3.tu-clausthal.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Hi, > > I recently upgraded a dedicated FreeBSD box with a DEC 21040- > based network card from 2.1.7.1-RLEASE to 2.2-971223-SNAP. > > It was running with 2.1.7.1 about one year without problems. > Since the upgrade to 2.2-971223, I get the following syslog > messages every now and then: > > Dec 29 18:18:19 dorifer /kernel: de0: receive: 00:e0:f7:8a:8d:41: alignment error > Dec 29 18:25:37 dorifer /kernel: de0: receive: 00:00:e8:0d:8d:6f: bad crc > > As far as I can tell, nothing else has changed (same network > card, mainboard, CPU, RAM). Is this a problem with the "de" > driver? Or is this just normal, and the 2.1.7.1 driver just > didn't report it? Or did my network card break at the same > time I upgraded to 2.2-971223? Please tell me if I should > provide any additional information. > > Regards > Oliver > > PS: The errors don't seem to affect data integrity, therefore > I think the affected packets are retransmitted. > > PPS: No need to cc replies to me; I'm reading the list via a > news gateway. > > -- > Oliver Fromme, Leibnizstr. 18-61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) > I once got messages like that from a de card, and it turned out to be some other machine on my local network that wasn't working well. Track down those mac addresses and that will help isolate where the problem is from. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971230103458.11208B-100000>