From owner-freebsd-current Fri Nov 28 02:21:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA05983 for current-outgoing; Fri, 28 Nov 1997 02:21:02 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA05959 for ; Fri, 28 Nov 1997 02:20:56 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id LAA25231 for freebsd-current@FreeBSD.ORG; Fri, 28 Nov 1997 11:20:54 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id LAA05417; Fri, 28 Nov 1997 11:18:47 +0100 (MET) Message-ID: <19971128111846.44639@uriah.heep.sax.de> Date: Fri, 28 Nov 1997 11:18:46 +0100 From: J Wunsch To: freebsd-current@FreeBSD.ORG Subject: Re: de driver problem Reply-To: Joerg Wunsch References: <199711280210.LAA11210@access.sfc.wide.ad.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199711280210.LAA11210@access.sfc.wide.ad.jp>; from Masafumi NAKANE/?$BCf:,2mJ8?(B on Fri, Nov 28, 1997 at 11:10:26AM +0900 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Masafumi NAKANE/?$BCf:,2mJ8?(B wrote: > And I get message like following very frequently. > > de0: receive: 00:00:a2:cb:5d:74: alignment error > > There are some ``bad crc'' as well. I think they should be logged with log(LOG_DEBUG, ...) (if at all). printf'ing them is ridiculous, one of our servers is printing all kernel hardware error messages on paper, using an old dot-matrix printer, and while the paper consumption was rather low in the past, it substantially grew up recently after switching the server to a DEC-based card. (We've also got two offenders in the company occasionally sending bad packets, or maybe it's the cable wiring that's poor in that floor.) > And could someone give me some suggestion how I can find out what may > be causing this? (I've been playing with tcpdump and netstat in a > hope that I may find some clue. But so far, no luck.) Sure, the driver has dropped the packets before they could reach BPF. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)