Bug#647004: Realtek Ethernet adapters (r8169 driver)

[Jonathan Nieder <jrnieder@gmail.com>]

Hi again,

Jonathan Nieder wrote:
> HacKurx wrote:

>> NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> [...]
>> The R8169 driver in kernel 3.1 fixes the problem :

Hm.

Some of the more interesting changes between 3.0 and 3.1:

 92fc43b4159b r8169: modify the flow of the hw reset
 70090424e596 r8169: support RTL8111E-VL
 d4ed95d796e5 r8169: fix wake on lan setting for non-8111E
  (not relevant for these symptoms, of course)
 aaa89c08d9ff r8169: don't enable rx when shutdown (likewise)
 106633897e08 r8169: fix WOL setting for 8105 and 8111evl (likewise)
 649b3b8c4e86 r8169: fix driver shutdown WoL regression (fixes a
  regression introduced by the hw reset rework)
 e542a2269f23 r8169: adjust the RxConfig settings
  1687b5667988 r8169: fix sticky accepts packet bits in RxConfig
 93a3aa259334 r8169: Add support for D-Link 530T rev C1
 c28aa3856710 r8169 : MAC address change fix for the 8168e-vl
 c2b0c1e7fb69 r8169: fix the reset setting for 8111evl
 e03f33af79f0 r8169: remove erroneous processing of always set bit
 2544bfc0eb25 r8169: do not enable the TBI for anything but the
  original 8169
 1b23a3e3d1b9 r8169: fix wrong eee setting for rlt8111evl

Knowing which chip you have would narrow things down further.  Can you
attach "dmesg" output from booting up and loading the r8169 driver?
Even better would be the same from a kernel built with

	#define RTL8169_DEBUG

added near the top of drivers/net/r8169.c (or
drivers/net/ethernet/realtek/r8169.c if you are using a newer kernel).

Curious,
Jonathan