From owner-freebsd-stable Sun Nov 2 12:48:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11514 for stable-outgoing; Sun, 2 Nov 1997 12:48:37 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.91.116]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11508 for ; Sun, 2 Nov 1997 12:48:30 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.7/8.6.10) with SMTP id PAA07848 for ; Sun, 2 Nov 1997 15:48:24 -0500 (EST) Date: Sun, 2 Nov 1997 15:48:24 -0500 (EST) From: Robert Watson Reply-To: Robert Watson To: freebsd-stable@freebsd.org Subject: SMC EtherPower card + CRC errors 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 I recently upgraded one of my server machines from FreeBSD 2.2.1 (with a 2.2.2 kernel and a few other patches.) The card holds an SMC EtherPower card described by dmesg as the following: FreeBSD 2.2.5-STABLE #0: Sat Nov 1 14:32:43 EST 1997 robert@cyrus.watson.org:/usr/src/sys/compile/FLEDGE CPU: Pentium (119.75-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 100663296 (98304K bytes) ... de0 rev 33 int a irq 9 on pci0:14 de0: SMC 21041 [10Mb/s] pass 2.1 de0: address 00:e0:29:0e:b6:dd de0: enabling 10baseT port Since the upgrade, we've been getting a fair number of the following message: de0: receive: ff:ff:ff:ff:ff:ff: bad crc de0: receive: ff:ff:ff:ff:ff:ff: bad crc de0: receive: ff:ff:ff:ff:ff:ff: bad crc de0: receive: ff:ff:ff:ff:ff:ff: bad crc de0: receive: ff:ff:ff:ff:ff:ff: bad crc de0: receive: 00:60:97:61:ba:39: bad crc de0: receive: ff:ff:ff:ff:ff:ff: bad crc de0: receive: ff:ff:ff:ff:ff:ff: bad crc Mostly on the broadcast address. None of the other BSD machines on the network are giving this error. While it's possible that the card has gone bad, the timeliness of the new error with regards to the stable upgrade is convenient :). Does anyone have a pointers, or suggestions as to a cause? I have not been following changes to the de driver. Robert N Watson Junior, Logic+Computation, Carnegie Mellon University http://www.cmu.edu/ Network Administrator, SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org rwatson@safeport.com http://www.watson.org/~robert/