Re: 2.6.12 breaks 8139cp

[Ed Sweetman <safemode@comcast.net>]

Note: this is not with 8139cp, but with 8139too, particularly 8139b

in 2.6.12, 2.6.12-mm1 and 2.6.12-RT-V0.7.49-01
With preempt enabled/disabled/rt/voluntary...
With mmio and pio in 8139too , with old rx reset and combinations of 
enabled and disabled

Even changed ethernet cables ... nothing stopped my Tx problems.
This is all occurring on a box that until yesterday, had an uptime of 
over 410 days on 2.6.0-mm1, so it's not the hardware, also, reverting to 
that kernel remedied the problem.

Here is a snip from dmesg

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0c 0055 c07f media 00.
eth0: Tx queue start entry 78  dirty entry 74.
eth0:  Tx descriptor 0 is 0008a03c.
eth0:  Tx descriptor 1 is 0008a03c.
eth0:  Tx descriptor 2 is 0008a03c. (queue head)
eth0:  Tx descriptor 3 is 0008a03c.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

I'm not sure if this is exactly related to the thread, but it seemed too 
much of a coincidence to think that it's not. 

The symptoms of the problem is short bursts of traffic with 30 second or 
so pauses of absolutely no response, repeating. The higher the bandwidth 
the worse the situation, but it occurs regardless. 

No other errors are reported or seen on the box except this Tx problem.  
I'm tempted to go ahead and try 2.6.11, but haven't yet.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/