*BSD News Article 71837


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!usenet.ins.cwru.edu!agate!howland.reston.ans.net!nntp.coast.net!fu-berlin.de!zib-berlin.de!irz401!orion.sax.de!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: network problem
Date: 23 Jun 1996 19:52:15 GMT
Organization: Private BSD site, Dresden
Lines: 21
Message-ID: <4qk79f$9hc@uriah.heep.sax.de>
References: <31CA6E3B.41C67EA6@pike.phil.uni-passau.de>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
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

Gerald Anleitner <anleitne@pike.phil.uni-passau.de> wrote:

> I am not sure if I am right in this group, but at the momen,
> I did not find something better for my question:
> 
> ed0: NIC memory corrupt - invalid packet length 9984

At which point does it happen?  Is it reproducible?  Does it affect
the operation of your system?

I've seen it happen lately whenever an AMC PCnet machine was active on
the local Ethernet.  All the `ed' driver listeners complained about
these bad packets.  The error was benign however, and it couldn't be
reproduced well enough to understand it.

-- 
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. ;-)