tulip.c 0.91g lockup ...

[Donald Becker]

On Fri, 29 Oct 1999, Gerhard Wiesinger wrote:

> I've used tulip.c 0.90 (and previous) with 2 network interfaces for years
> WITHOUT any problems so far.
> 
> I've upgraded to tulip.c 0.91g and one interface can not transmit after
> some work (Depends on: from minutes up to hours until this occours)
> 
> Oct 29 19:06:30 bbs kernel: eth1: 21140 transmit timed out, status
> fc6988c5, SIA ffffff0b ffffffff 1c09fdc0 fffffec8, resetting... 

The driver might attempt to media switching during transmit timeouts.
The exact action taken depends on the chip type, the transceiver type, if a
EEPROM media table exists, and the media table contents.  So we need to know
the driver detection message for your specific cards. 

It *does* appear that the Tulip chip in the message above was trying to
raise an interrupt that wasn't handled.  You should check /proc/interrupts
for an increasing count.  I'm guessing that the real problem here is an APIC
bug with interrupt line assignment in a new kernel, not a driver media
selection problem. 

> eth0 is 100BaseTX, eth1 is 10BASE-T, Adapter cards are Accton EN1207
> (without anything like TX, B, C, ...).

Donald Becker
Scyld Computing Corporation, and
USRA-CESDIS,   becker@cesdis.gsfc.nasa.gov