Re: r8169 NETDEV WATCHDOG: eth0: transmit timed out [0/8]

Re: r8169 NETDEV WATCHDOG: eth0: transmit timed out [0/8]

[David Dillow]

On Sat, 2009-08-29 at 12:16 +0300, roma1390 wrote:
> Using 3 different r8169 devices on 2 servers (from 2 server so 100% of
> population) we getting
> 
> NETDEV WATCHDOG: eth0: transmit timed out

You're running an old version of the kernel, and the driver was patched
to fix that issue in 2.6.30. It is also in the 2.6.29.x stable series,
and I think maybe the 2.6.28.x series -- please try those and see if you
problem is resolved.

We're aware of a possible issue with the fix in those kernels, and are
working it in another thread. A quick search of the archives should turn
it up. Will you be willing to test patches?

>From your dmesg, it looks like you have 8169c's, running in MSI mode.
Can you please confirm this by sending your /proc/interrupt info:
	cat /proc/interrupts | grep eth0

Also, in the future, please cc netdev on network bug reports.
Thanks!

Re: r8169 NETDEV WATCHDOG: eth0: transmit timed out [0/8]

[Francois Romieu]

David Dillow <dave@thedillows.org> :
> On Sat, 2009-08-29 at 12:16 +0300, roma1390 wrote:
> > Using 3 different r8169 devices on 2 servers (from 2 server so 100% of
> > population) we getting
> > 
> > NETDEV WATCHDOG: eth0: transmit timed out
> 
> You're running an old version of the kernel, and the driver was patched
> to fix that issue in 2.6.30. It is also in the 2.6.29.x stable series,
> and I think maybe the 2.6.28.x series -- please try those and see if you
> problem is resolved.

The fix in 2.6.28.x targets the netdev watchdog problem at boot time only.
2.6.28.x does not include something similar to
f11a377b3f4e897d11f0e8d1fc688667e2f19708 so 2.6.28.x will almost surely
not fit.

-- 
Ueimor