Brief summary: I just put together an AMD K6-2 300 system on an EPOX board
with the VIA VP3 chipset. I had a bunch of little problems for a while, but
now I am just left with one. The PCNet32 NIC does not seem to like
something. I've had no luck with 2.1.122, 2.0.34, or Win98 on the K6-2
system. It DOES work on my PII-266 (Win98) at work. I have swapped out the
hub and 2 cables I use at home with just a single "nun-modem" 10baseT cable
that I have used before for direct transfers. Whatever the case, I get this
message.
Sep 14 14:48:06 denali kernel: eth0: transmit timed out, status 007a,
resetting.
Sep 14 14:48:06 denali kernel: Ring data dump: dirty_tx 0 cur_tx 16 (full)
cur_rx 0.
Sep 14 14:48:06 denali kernel: 80358000 0608 0000 80358608 0608 0000
80358c10 0608 0000 80359218 0608 0000
Sep 14 14:48:06 denali kernel: 80359820 0608 0000 80359e28 0608 0000
8035a430 0608 0000 8035aa38 0608 0000
Sep 14 14:48:06 denali kernel: 8035b040 0608 0000 8035b648 0608 0000
8035bc50 0608 0000 8035c258 0608 0000
Sep 14 14:48:06 denali kernel: 8035c860 0608 0000 8035ce68 0608 0000
8035d470 0608 0000 8035da78 0608 0000
Sep 14 14:48:06 denali kernel: 8334dec2 006e 0000 83350608 006e 0000
83350c10 006e 0000 83351218 006e 0000
Sep 14 14:48:06 denali kernel: 83351820 006e 0000 83351e28 00ff 0000
83352430 006e 0000 83352a38 006e 0000
Sep 14 14:48:06 denali kernel: 83353040 006e 0000 83353648 006e 0000
83353c50 006e 0000 83354258 006e 0000
Sep 14 14:48:06 denali kernel: 83354860 006e 0000 83354e68 006e 0000
83355470 006e 0000 83355a78 006e 0000
Sep 14 14:53:36 denali kernel: eth0: transmit timed out, status 007b,
resetting.
Sep 14 14:53:36 denali kernel: Ring data dump: dirty_tx 0 cur_tx 16 (full)
cur_rx 0.
Sep 14 14:53:36 denali kernel: 80358000 0608 0000 80358608 0608 0000
80358c10 0608 0000 80359218 0608 0000
Sep 14 14:53:36 denali kernel: 80359820 0608 0000 80359e28 0608 0000
8035a430 0608 0000 8035aa38 0608 0000
Sep 14 14:53:36 denali kernel: 8035b040 0608 0000 8035b648 0608 0000
8035bc50 0608 0000 8035c258 0608 0000
Sep 14 14:53:36 denali kernel: 8035c860 0608 0000 8035ce68 0608 0000
8035d470 0608 0000 8035da78 0608 0000
Sep 14 14:53:36 denali kernel: 83350000 006e 0000 83350608 006e 0000
83350c10 006e 0000 83351218 006e 0000
Sep 14 14:53:36 denali kernel: 83351820 00ff 0000 83351e28 00ff 0000
83352430 005c 0000 83352a38 005c 0000
Sep 14 14:53:36 denali kernel: 83353040 005c 0000 83353648 005c 0000
83353c50 00e7 0000 83354258 00e7 0000
Sep 14 14:53:36 denali kernel: 83354860 00e7 0000 83354e68 00e7 0000
83355470 00e7 0000 83355a78 006e 0000
That is an old one from messages. I usually just get the first line, but I
included this one because it has more info (although I doubt the dump will
help much.)
I don't have my ifconfig dump (sorry), but it shows only errors
transmitting. I once managed to completely reboot the box running Win98 by
pinging it from the other box. I'm still not convinced the tested cable did
not go bad, so I'm going to swap out the 2 cables and hub with a friend's
stuff and try again. I am at a complete loss as to what the problem is.
I was given a patch by Thomas Bogendoerfer with 2.1.122 to try and I tried
it last night. I applied the patch by hand since it didn't seem to want to
go on using patch (I had forwarded it from Outlook Express.) Nothing new.
Any advice would be greatly appreciated. Since the problem is OS dependent,
I am obviously still thinking hardware at this point.
-Eric ;-)
-- Eric Princen Micro Analysis & Design http://www.maad.com/~eprincen "I believe you should live each day as if it were your last, which is why I don't have any clean laundry, because, let's face it, who wants to wash clothes on the last day of their life? "
- 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/