Transmit timeouts

[Jay Freeman (saurik)]

Since no one else (that I have seen) has actually provided any real data or
evidence of the problem, I have put together everything I have been able to
find out below (using the program mentioned on the eepro100 website for
diagnostic purposes):

I am getting the same "Transmit timed out" problem, I am running a Tyan
S1836DLUAN Thunder 100 motherboard with a built on Intel 82558.  I am
running a system very close to RedHat Rawhide version 19990901, however I
have a custom 2.2.12 kernel with the 19990824 RAID patches, a restricted
/proc patch, the international crypto patches, support for /dev/parport*
devices, and a patch for ip firewall modules (not that I expect any of that
matters, nor would it do anyone any good, but just in case... doesn't take
long to list).  I am using the eepro100 version 1.08 driver.  The hub I used
for this is a LinkSys 10/100 Etherport 10/100 8-port EZXS88 autoswitching
hub, however I get the problem with all the hubs I have tried it with
(including a 100BaseT only and a 10BaseT only).  I have not tried going back
to the 1.06 driver yet (didn't think of it really until I read a message
posted a few days ago).

>From my syslog:

Sep  4 23:28:50 ironclad kernel: eth0: Transmit timed out: status 0050  0000
at 1631107/1631121 command 000c0000.
Sep  4 23:28:50 ironclad kernel: eth0: Trying to restart the transmitter...

I got the mii-diag program, and was able to get the following additional
information:

[root(2)@ironclad EEPro]# mii-diag -w
Using the default interface 'eth0'.
Basic registers of MII PHY #1:  3000 782d 02a8 0150 05e1 41e1 0001 ffff.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner can do 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
23:26:11.-1073742  Baseline value of MII BMSR (basic mode status register)
is 782d.
23:28:50.-1073742  MII BMSR now 7809:   no link, NWay busy, No Jabber
(0000).
23:28:52.-1073742  MII BMSR now 7829:   no link, NWay done, No Jabber
(41e1).
   New link partner capability is 41e1 0003: 100baseTx-FD 100baseTx
10baseT-FD 10baseT.
23:28:52.-1073742  MII BMSR now 782d: Good link, NWay done, No Jabber
(41e1).

Just tried switching it into the higher debug mode, got the following
output:

[root(2)@ironclad EEPro]# mii-diag -w -D
DEBUG: argc=3, optind=3 and argv[optind] is (null).
Using the default interface 'eth0'.
 3000 782d 02a8 0150 05e1 41e1 0001 ffff ffff ffff ffff ffff ffff ffff ffff
ffff 0203 0000 0001 e820 0000 0000 ffff 0000 00c0 0000 0000 0000 ffff ffff
ffff ffff
Basic registers of MII PHY #1:  3000 782d 02a8 0150 05e1 41e1 0001 ffff.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner can do 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
23:56:30.1074813  Baseline value of MII BMSR (basic mode status register) is
782d.
23:59:20.1074813  MII BMSR now 7809:   no link, NWay busy, No Jabber (0000).
23:59:22.1074813  MII BMSR now 7829:   no link, NWay done, No Jabber (41e1).
   New link partner capability is 41e1 0003: 100baseTx-FD 100baseTx
10baseT-FD 10baseT.
23:59:22.1074813  MII BMSR now 782d: Good link, NWay done, No Jabber (41e1).

Sincerely,
Jay Freeman (saurik)
<saurik@saurik.com>