[lkml]   [2001]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectHow to debug a 2.4.4 tulip problem?


I'm having a small intermittent problem with the tulip driver in linux
2.4.4, and I'm looking for some guidance on how to debug it.

What happens is that on one of my boxes the card ocasionally gets wedged.
That is, network traffic gets painfully slow, e.g. pinging another host on
the same segment causes each ping to take (almost exactly) 1 second,
rather than the usual 200 usecs or so. Executing ifup/ifdown unwedges the

Some relevant details about this box:
eth0: Lite-On 82c168 PNIC rev 32 at 0xb800, 00:C0:F0:2D:3D:8A, IRQ 17.
MSI-6321 motherboard (VIA Apollo Pro)

Now I have a similar box that I think does not show the problem (not 100%
sure). It has:
eth0: Lite-On 82c168 PNIC rev 33 at 0xe800, 00:A0:CC:3F:33:32, IRQ 18.
Tekram P6B40D-A5 motherboard (Intel 440BX)

As a wild guess, it seems like when the card is wedged, some interrupt is
getting lost, so that the transmit or send doesn't occur until a timer
times out. Perhaps there is a bug in rev 32 of this card that is not in
rev 33.

What information should I gather when the card is wedged to aid in
debugging? Is 'lspci -xxx' enough? Any suggestions would be welcome.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.029 / U:0.356 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site