3c59x transmit timed out, take 3

[Seva]

> > Included is the syslog output right before I get this:
> 
> What was the message before this?

I had it attached in the last message... Here's the log again...

May  9 23:37:41 null kernel: upt, status e000. 
May  9 23:37:41 null kernel: >eth0: In interrupt loop, status e011. 
May  9 23:37:43 null kernel: ing interrupt, status e000. 
May  9 23:37:44 null kernel: tatus 0062. 
May  9 23:37:45 null kernel: ceiving packet size 98 status 0062. 
May  9 23:37:49 null kernel: h0: In interrupt loop, status e011. 
May  9 23:37:51 null kernel: 9, latency 2 ticks. 
May  9 23:37:52 null kernel: t loop, status e011. 
May  9 23:37:52 null kernel: . 
May  9 23:37:53 null kernel: ket(), status e011, rx_status 0062. 
May  9 23:37:54 null kernel: 7>Receiving packet size 98 status 0062. 
May  9 23:38:02 null kernel: . 
May  9 23:38:04 null kernel: 11. 
May  9 23:38:05 null kernel: rrupt loop, status e011. 
May  9 23:38:05 null kernel: 0: exiting interrupt, status e000. 
May  9 23:38:05 null kernel: 011, rx_status 0062. 
May  9 23:38:05 null kernel: x_packet(), status e011, rx_status 0062. 
May  9 23:38:06 null kernel: g packet size 98 status 0062. 
May  9 23:38:06 null kernel: et(), status eicks. 
May  9 23:38:09 null kernel:  status e000. 
May  9 23:38:15 null kernel: In interrupt loop, status e011. 
May  9 23:38:18 null kernel:  In interrupt loop, status e011. 
May  9 23:38:22 null kernel:   In rx_packet(), status e011, rx_status 0062. 
May  9 23:38:29 null kernel: s 0062. 
May  9 23:38:31 null kernel: t, status e009, latency 1 ticks. 
May  9 23:38:34 null kernel:  interrupt, status e000. 
May  9 23:38:36 null kernel: exiting interrupt, status e000. 
May  9 23:38:36 null kernel: 062. 
May  9 23:38:36 null kernel: exiting interrupt, status e000. 
May  9 23:38:39 null kernel: atus e000. 
May  9 23:38:39 null kernel: cy 1 ticks. 
May  9 23:38:41 null kernel: eth0: interrupt, status e009, latency 2 ticks. 
May  9 23:38:44 null kernel: exiting interrupt, status e000. 
May  9 23:38:44 null kernel: cy 1 ticks. 
May  9 23:38:45 null kernel: 7>Receiving packet size 98 status 0062. 
May  9 23:38:45 null kernel: exiting interrupt, status e000. 
May  9 23:38:47 null kernel: cy 2 ticks. 
May  9 23:38:49 null kernel: x_packet(), status e011, rx_status 0062. 
May  9 23:38:51 null kernel: exiting interrupt, status e000. 
May  9 23:38:55 null last message repeated 4 times
May  9 23:38:56 null kernel: 7>Receiving packet size 98 status 0062. 
May  9 23:38:57 null kernel: 7>eth0: exiting interrupt, status e000. 
May  9 23:38:58 null kernel: , latency 2 ticks. 
May  9 23:38:59 null kernel: 062. 
May  9 23:38:59 null kernel: 2. 
May  9 23:39:00 null kernel: cy 2 ticks. 
May  9 23:39:01 null kernel: exiting interrupt, status e000. 
May  9 23:39:02 null kernel: exiting interrupt, status e000. 
May  9 23:39:04 null kernel: >eth0: In interrupt loop, status e011. 
May  9 23:39:06 null kernel: exiting interrupt, status e000. 
May  9 23:39:08 null kernel: 0: exiting interrupt, status e000. 
May  9 23:39:08 null kernel: exiting interrupt, status e000. 
May  9 23:39:08 null kernel: exiting interrupt, status e000. 
May  9 23:39:09 null kernel: cy 3 ticks. 
May  9 23:39:09 null kernel: exiting interrupt, status e000. 
May  9 23:39:11 null kernel: 00. 
May  9 23:39:15 null kernel: oop, status e011. 
May  9 23:39:16 null kernel: , latency 1 ticks. 
May  9 23:39:20 null kernel:  interrupt, status e000. 
May  9 23:39:21 null kernel: cy 2 ticks. 
May  9 23:39:25 null kernel: 7>Receiving packet size 98 status 0062. 
May  9 23:39:28 null kernel: exiting interrupt, status e000. 
May  9 23:39:28 null kernel: 062. 
May  9 23:39:29 null kernel: : interrupt, status e011, latency 2 ticks. 
May  9 23:39:29 null kernel: exiting interrupt, status e000. 
May  9 23:46:57 null kernel: o<7>eth0: interrupt, status e011, latency 2 ticks. 
May  9 23:53:44 null kernel: eth0: transmit timed out, tx_status 00 status e000. 
May  9 23:54:14 null last message repeated 6 times

> 
> > May  9 23:53:44 null kernel: eth0: transmit timed out, tx_status 00 status
> > e000.
> ..
> > problem to the developers? Any workarounds? This usually occurs during large
> > INCOMING connections, and happens during the 1st TX overrun...
> 
> Tx overrun?  Do you mean Rx overrun, or Tx underrun?  Or some other error?

# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:A0:24:8B:AD:A1
          inet addr:128.248.5.205  Bcast:128.248.5.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21221 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15413 errors:0 dropped:0 overruns:0 carrier:0
          collisions:8 txqueuelen:100
          Interrupt:10 Base address:0xef20

In the TX row, field labeled overruns:... when that goes from 0 to 1 this
problem occurs...

/Simon