From owner-freebsd-stable Tue Dec 30 07:37:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00216 for stable-outgoing; Tue, 30 Dec 1997 07:37:15 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from adsight.com (adsight.com [207.86.2.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00205 for ; Tue, 30 Dec 1997 07:37:11 -0800 (PST) (envelope-from webadmin@adsight.com) Received: from localhost (webadmin@localhost) by adsight.com (8.8.7/8.8.7) with SMTP id KAA11222 for ; Tue, 30 Dec 1997 10:37:17 -0500 (EST) Date: Tue, 30 Dec 1997 10:37:08 -0500 (EST) From: Sam Magee To: freebsd-stable@FreeBSD.ORG Subject: Re: Errors with DEC 21040 NIC in 2.2-stable In-Reply-To: <199712291806.TAA15038@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > 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