On Tue, 6 Jun 2000, Marco Colombo wrote:
> I must admit i can't tell. As soon as i finish with the GA-71XE tests,
> I'll try the K7V again. But i'm sure the card can receive packets
> (*after* the timeout messages start).
> I could see that running the driver with debug=7. It's just the TX queue
> which is stalled. The frames are enqueued into the ring buffer, but
> never get transmitted (no TX activity logging by the driver and the other
Ok. It doesn't give me any bright ideas either way :) just trying to
understand what is happening. But then it is the same behaviour as the
other problem.
Your idea about PCI wierdness is probably the best one yet, but it could
be lots of things (tx ring being overwritten by wild pointer ... nah).
> side sees no activity on the ethernet, with tcpdump).
> So i guest it does get interrupts, for incoming packets, at least.
One thing you could try looking at is Donald Becker's hardware diagnostic
tool for the "rhine" on http://www.scyld.com/diag/. It can be very useful.
% ./via-diag -aa
This will dump the register contents of the chip. By comparing the values
when the card is working and when it is not might show something. Maybe
even if the card thinks that it is supposed to send anything.
You can get the (rather minimalistic) datasheet from
http://www.via.com.tw/pdf/productinfo/vt86c100a.pdf
and try and decode it (the first 2 lines are the current descriptors 0x00
- 0x1f is rx, 0x20 - 0x3f is tx, same format as the rx_desc/tx_desc
structs in the driver source) or send me the output of a few good and bad
register contents.
And since you can get this with 2.2 and different versions of Donalds
driver (or am I confused again) he may be interested too (unless you've
already mentioned this to him).
/Urban
-
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/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:26 EST