Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!sgi!vjs From: vjs@rhyolite.SGI.COM (Vernon Schryver) Newsgroups: comp.sys.sgi Subject: Re: Strange enp0 errors on 4D60Turbo Summary: it's bad ether Message-ID: <16645@sgi.SGI.COM> Date: 28 Jun 88 17:26:46 GMT References: <967@eos.UUCP> Sender: daemon@sgi.SGI.COM Distribution: na Organization: Silicon Graphics Inc, Mountain View, CA Lines: 16 In article <967@eos.UUCP>, timelord@eos (G. Murdock Helms) writes: > In January of this year we purchased an SGI 4D60Turbo. Around February or > March of this year, this strange error began popping up on the console: > > enp0: bad recieve packet length of 0 This means that an invalidly small packet came in from the ether. Future releases of the driver will have a printf based on: "if_enp%d: packet too small (length = %d)\n" We infrequently get flurries of these in our network. They mean something is broken or not yet working somewhere on the wire. Vernon Schryver Silicon Graphics vjs@sgi.com or {pyramid,allegra,research,sun,pacvax}!sgi!vjs