lkml.org 
[lkml]   [1998]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjecteth0: Transmit timed out
I can cause these quite easily on a fairly busy nameserver running 2.0.34,
using an EtherExpressPro100, running 10BT half-duplex.

Relevant bits of dmesg output follow.

eepro100.c:v0.99B 4/7/98 Donald Becker linux-eepro100@cesdis.gsfc.nasa.gov
eth0: Intel EtherExpress Pro 10/100 at 0xe000, 00:A0:C9:20:65:89, IRQ 10.
Board assembly 352509-003, Physical connectors present: RJ45
Primary interface chip DP83840 PHY #1.
DP83840 specific setup, setting register 23 to 8462.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x49caa8d6).
Receiver lock-up workaround activated.
[...]
eth0: Transmit timed out: status 0050 command 0000.
eth0: Trying to restart the transmitter...
eth0: Transmit timed out: status 0050 command 0000.
eth0: Trying to restart the transmitter...
[many of those]

We've got a script that runs nightly and reverse resolves the day's
webserver access logs, and produces a largish number of such timeouts. I
don't recall ever seeing one in the 6 months or so the machine had been
running 2.0.33. There's also a brief networking stall accompanying each
message. It's not causing any problems, I'm just putting it out here
because the only other references I've seen referring to tx timeouts were
with the 3c59x driver and I wanted to add a data point.

A cursory scan of the past couple weeks' posts to the list didn't offer
any solutions, if I missed something, a quick "go search the archives"
reply will do.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

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