[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120726195658.GA14668@electric-eye.fr.zoreil.com>
Date: Thu, 26 Jul 2012 21:56:58 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: Denys Fedoryshchenko <denys@...p.net.lb>
Cc: netdev@...r.kernel.org
Subject: Re: r8169, 3.5.0, does't work at all
Denys Fedoryshchenko <denys@...p.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.
--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists