From owner-freebsd-hackers Tue Apr 1 17:14:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA20751 for hackers-outgoing; Tue, 1 Apr 1997 17:14:13 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA20745 for ; Tue, 1 Apr 1997 17:14:10 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id RAA07907 for ; Tue, 1 Apr 1997 17:14:09 -0800 (PST) Date: Tue, 1 Apr 1997 17:14:09 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: de driver problems/ CRC errors with 2.2.1-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Digital HX6000, P6200/512, 32MB RAM, onboard Adaptec 7880, UW's, Toshiba 12X CDROM, 1 2GB seagate Barracude (wide), 1 SMC dual port 10/100 card. This box is hooked to a 3COM Superstack II Switch 3000, (A 100MB switch). Any heavy NFS access (like via iozone on NFS partition) generates kazillions of CRC align errors, at the rate of 30-40/second. (At least, according to the 3com switch, and the output of netstat). lighter access doesn't seem to do it. For example, running bonnie, the putc phase generates oodles of errors, but the rewrite phase generates maybe 1 or 2 per page of output. Any tips appreciated, I've been happy with the de driver, but this is not acceptable or usable. BTW, I took a box with a much older 2.2 kernel, from around October or so, and plugged it in, and zero problems. So it seems like a moderately recent development.