Re: EtherExpress 16 Errors

Brian May (bmay@share.cs.monash.edu.au)
Fri, 17 Sep 1999 15:58:35 +1000

On Fri, Sep 17, 1999 at 11:46:21AM +1000, Brian May wrote:
> Hello,
>
> I am getting the following errors, from a 486 computer
> with ISA EtherExpress 16:
>
> Sep 14 15:50:57 share kernel: eth0: transmit aborted, too many collisions
> Sep 14 15:51:31 share kernel: eth0: tx interrupt but no status
> Sep 14 15:52:02 share last message repeated 2 times
> Sep 14 15:52:27 share last message repeated 3 times
> Sep 14 15:52:54 share kernel: eth0: transmit aborted, too many collisions
> Sep 14 15:57:51 share kernel: eth0: tx interrupt but no status
> Sep 14 15:58:04 share kernel: eth0: tx interrupt but no status
> Sep 14 15:58:37 share kernel: eth0: tx interrupt but no status
>
> thats over a ten minute period. It is possible that the "too
> many collisions" is from an overloaded network, but it looks
> suspicious to me. (how can I tell?)
>
> It might be possible that this errors are preventing me from
> making reliable ftp transmissions. However, I haven't
> isolated this problem yet, and it may be elsewhere. Everything
> else seems to work fine.
>
> I have the Etherexpress 16 driver compiled into the kernel
> (not as a module). It reports, when loading:
>
> Sep 3 08:27:26 share kernel: eth0: EtherExpress 16 at 0x300 (IRQ 5, RJ45 connector, 16-bit bus, 32k RAM)
>
> I have:
>
> share:~# uname -a
> Linux share 2.2.12 #2 Thu Sep 2 09:37:30 EST 1999 i486 unknown
>
> ifconfig reports only 39 errors for 14 days, which seems small
> compared with the number of messages I get in /var/log/kern.log

Even more serious are these messages (which I hoped would be
fixed with 2.2.12 :-( )

share login: eth0: CU wedged, status 0140 0000, resetting...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 not responding, giving up.
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 not responding, giving up.
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 not responding, giving up.

The Ethernet just crashed.

...hmmm this looks very similar to my NE2000 adaptor
playing up (or another completely different computer).
Coincidence???
Even more serious are these messages (which I hoped would be
fixed with 2.2.12 :-( )

share login: eth0: CU wedged, status 0140 0000, resetting...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 not responding, giving up.
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 not responding, giving up.
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 reset timed out, kicking...
eth0: i82586 not responding, giving up.

The Ethernet just crashed.

those messages keep repeating.

...hmmm this looks very similar to my NE2000 adaptor
playing up (or another completely different computer).
Coincidence???

> PS. Please CC replies to me.

Now to reboot, so hopefully I can send this message.

-- 
Brian May <bmay@share.cs.monash.edu.au>


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/