From owner-freebsd-stable Sun Nov 2 15:01:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16583 for stable-outgoing; Sun, 2 Nov 1997 15:01:55 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from biceps.gymnet.com (qmailr@biceps.gymnet.com [204.216.82.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA16577 for ; Sun, 2 Nov 1997 15:01:51 -0800 (PST) (envelope-from rwl@gymnet.com) Received: (qmail 15830 invoked from network); 2 Nov 1997 23:02:30 -0000 Received: from triceps.gymnet.com (HELO mail.gymnet.com) (204.216.82.51) by biceps.gymnet.com with SMTP; 2 Nov 1997 23:02:30 -0000 Date: Sun, 2 Nov 1997 15:01:08 -0800 From: Robert Luce X-Mailer: The Bat! (v1.00 Preview 1) Registered to Robert Luce Reply-To: Robert Luce Organization: Gymnet Communications Priority: Normal Message-ID: <1625.971102@gymnet.com> To: Robert Watson CC: freebsd-stable@freebsd.org Subject: Re: SMC EtherPower card + CRC errors References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm seeing very similar problems, also with an SMC card (de0). Nov 2 11:12:08 flex /kernel: de0: receive: 00:a0:24:80:09:33: bad crc I'm also seeing many more of the following since cvsupping FreeBSD 2.2.5-STABLE: Nov 2 11:24:25 flex /kernel: Out of mbuf clusters - increase maxusers! > 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/ ---- Bob Luce "Il faut supporter deux ou trois chenilles System/News Administrator si on veut connaitre les papillons.." - Antoine de Saint-Exupery Finger rwl@gymnet.com for PGP Public Key Block