Re: r8169, 3.5.0, does't work at all

[Denys Fedoryshchenko <denys@visp.net.lb>]

On 2012-07-26 22:56, Francois Romieu wrote:
> Denys Fedoryshchenko <denys@visp.net.lb> :
>> Just pushed new kernel to test cluster and got this:
> [...]
>> [    1.606212] r8169 0000:03:00.0: eth1: RTL8168b/8111b at
>> 0xf8606000, 00:08:54:57:7a:33, XID 18000000 IRQ 44
>> [    1.606366] r8169 0000:03:00.0: eth1: jumbo features [frames:
>> 4080 bytes, tx checksumming: ko]
>> ....
>> [   20.406090]     input device check on
>> [   20.406177]     Actions configured
>> [   21.526836] r8169 0000:02:00.0: eth0: link up
>> [   28.038386] ------------[ cut here ]------------
>> [   28.038438] WARNING: at net/sched/sch_generic.c:255
>> dev_watchdog+0xd6/0x12a()
>> [   28.038489] Hardware name:
>> [   28.038534] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed
>
> Right at startup.
>
> Which kernel did you previously use ?
>
> This is exactly the primary device I use to access my test computer.
>
> .config and .dmesg will be welcome as well.
http://www.nuclearcat.com/dmesg.txt
http://www.nuclearcat.com/config.txt

There ifplugd also running, and udhcpc, both from busybox.
Now machine are deployed to production , working fine with 3.4.6 
kernel. I can do limited tests on it,
and i can search for more machines with similar cards.

---
Denys Fedoryshchenko, Network Engineer, Virtual ISP S.A.L.