new info WAS: Re: [tulip] LNE100TX version 4.1 timeouts on tx

[Erik Steffl]

Donald Becker wrote:
> 
> On Sun, 26 Nov 2000, Erik Steffl wrote:
> 
> >   after having problems described below I tried to move the LNE100TX to
> > different PCI slot and now it's all different. Soundcard works OK (it
> > used to play only about 1 second of sound when network card used to be
> > in original slot).
> 
> That's the symptom of a sound card on a blocked or invalid interrupt line.

  that was my guess too but /proc/interrupts said that the soundcard is
on 5 and network card is on 9 (just like now when soundcard is working).
in addition to that soundcard is ISA and network card is PCI.

> >   however, now the network card hangs up, not sure if it's tx or rx
> > (probably tx judging by the messages below).
> 
> You have just moved the configuration problem from your sound card to the
> network card.
> 
> >   I get plenty of messages like this one (all of them are exactly the
> > same):
> >
> > eth0: Transmit timed out, status fc664010, CSR12 00000000, resetting...
> 
> Run 'tulip-diag'.

jojda:/home/erik/skusobna/lne100tx/diag/tulip-diag# ./tulip-diag -m
tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-P adapter at 0x6100.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 128.
 The Comet MAC registers are 12782000 ffffcc14 filter 0000000000000000.
 MII PHY found at address 1, status 0x786d.
 MII PHY found at address 2, status 0x786d.
 MII PHY found at address 3, status 0x786d.
 MII PHY found at address 4, status 0x786d.
jojda:/home/erik/skusobna/lne100tx/diag/tulip-diag# 

  this with a change from Dan Hollis (addded line:

  outl( (inl(ioaddr + 0x88) | 0x01), ioaddr + 0x88);

  in case COMET: init_media() in tulip.c)

  additional info:

  the other side (windows computer) now says there are errors, there
used to be no errors before (even though there obviously were timeouts),

  it says half duplex in tulip-diag output but the status on windows
computer says full duplex (they are connected using crossover cable)

  also, after the change described above (added line) the network seems
to be much slower then it used to be (I have no exact numbers though)
but there are NO hang-ups (so far, I am running it for few hours, it
used to work only few minutes).

  I am not sure which output from tulip-diag would be most useful - the
one above, the one without added line in tulip.c before hang or after
the card is hang. Let me know if there's any info that might help to
solve the problem.

  thanks a lot.

	erik