From owner-freebsd-bugs Thu Jun 4 08:27:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26467 for freebsd-bugs-outgoing; Thu, 4 Jun 1998 08:27:34 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26437 for ; Thu, 4 Jun 1998 08:27:24 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA05944; Thu, 4 Jun 1998 11:27:16 -0400 (EDT) Date: Thu, 4 Jun 1998 11:27:16 -0400 (EDT) From: "Matthew N. Dodd" To: Hans Zuidam cc: freebsd-bugs@FreeBSD.ORG Subject: Re: if_ed/tcpdump problem In-Reply-To: <199806040758.JAA10331@truk.brandinnovators.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 4 Jun 1998, Hans Zuidam wrote: > Jun 4 08:54:54 truk /kernel: ed1: NIC memory corrupt - invalid packet length 4299 > Jun 4 08:54:55 truk /kernel: ed1: NIC memory corrupt - invalid packet length 8439 > Jun 4 08:54:55 truk /kernel: ed1: NIC memory corrupt - invalid packet length 8434 I've got a box with a generic NE2000 that does the same thing. (Its running arpwatch and some other things that use promisc mode.) I just ignore it as it doesn't seem to cause problems. On a machine with a WD8003E it would cause NFS mounts to time out. I solved this problem by replacing the E with an EP. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message