From: Stan Hoeppner on
Got this error message stream on a server today. Never seen this before.
Does this mean my NIC is going south? Or is something else going on? I
tried manualy bringing the NIC back up but ifdown/up didn't fix the problem.
Had to reboot the server to fix it. eth0 seems to be working fine now.

Mar 31 17:04:54 greer kernel: ------------[ cut here ]------------
Mar 31 17:04:54 greer kernel: WARNING: at net/sched/sch_generic.c:261
dev_watchdog+0xf7/0x186()
Mar 31 17:04:54 greer kernel: Hardware name:
Mar 31 17:04:54 greer kernel: NETDEV WATCHDOG: eth0 (e100): transmit queue 0
timed out
Mar 31 17:04:54 greer kernel: Modules linked in:
Mar 31 17:04:54 greer kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9 #1
Mar 31 17:04:54 greer kernel: Call Trace:
Mar 31 17:04:54 greer kernel: [<c101ef08>] ? warn_slowpath_common+0x5e/0x8a
Mar 31 17:04:54 greer kernel: [<c101ef66>] ? warn_slowpath_fmt+0x26/0x2a
Mar 31 17:04:54 greer kernel: [<c1181dd0>] ? dev_watchdog+0xf7/0x186
Mar 31 17:04:54 greer kernel: [<c10171ee>] ? __wake_up+0x29/0x39
Mar 31 17:04:54 greer kernel: [<c102af1e>] ? __queue_work+0x4d/0x5a
Mar 31 17:04:54 greer kernel: [<c1181cd9>] ? dev_watchdog+0x0/0x186
Mar 31 17:04:54 greer kernel: [<c1025c5c>] ? run_timer_softirq+0x115/0x168
Mar 31 17:04:54 greer kernel: [<c1022b5d>] ? __do_softirq+0x78/0xe5
Mar 31 17:04:54 greer kernel: [<c1022bed>] ? do_softirq+0x23/0x27
Mar 31 17:04:54 greer kernel: [<c100ed45>] ? smp_apic_timer_interrupt+0x6c/0x76
Mar 31 17:04:54 greer kernel: [<c1003096>] ? apic_timer_interrupt+0x2a/0x30
Mar 31 17:04:54 greer kernel: [<c1006e88>] ? default_idle+0x2a/0x3d
Mar 31 17:04:54 greer kernel: [<c1001ab9>] ? cpu_idle+0x37/0x4e
Mar 31 17:04:54 greer kernel: [<c12656de>] ? start_kernel+0x233/0x236
Mar 31 17:04:54 greer kernel: ---[ end trace 9c92c0e4b7673ea9 ]---
Mar 31 17:04:55 greer kernel: e100 0000:00:0d.0: firmware: using built-in
firmware e100/d101m_ucode.bin
Mar 31 17:04:55 greer kernel: e100: eth0 NIC Link is Up 100 Mbps Full Duplex
Mar 31 17:46:17 greer kernel: e100 0000:00:0d.0: firmware: using built-in
firmware e100/d101m_ucode.bin
Mar 31 17:46:17 greer kernel: e100: eth0 NIC Link is Up 100 Mbps Full Duplex
Mar 31 18:19:54 greer kernel: e100 0000:00:0d.0: firmware: using built-in
firmware e100/d101m_ucode.bin
Mar 31 18:19:55 greer kernel: e100: eth0 NIC Link is Up 100 Mbps Full Duplex
Mar 31 19:01:12 greer kernel: e100 0000:00:0d.0: firmware: using built-in
firmware e100/d101m_ucode.bin
Mar 31 19:01:13 greer kernel: e100: eth0 NIC Link is Up 100 Mbps Full Duplex
Mar 31 19:34:52 greer kernel: e100 0000:00:0d.0: firmware: using built-in
firmware e100/d101m_ucode.bin
Mar 31 19:34:53 greer kernel: e100: eth0 NIC Link is Up 100 Mbps Full Duplex
Mar 31 20:16:24 greer kernel: e100 0000:00:0d.0: firmware: using built-in
firmware e100/d101m_ucode.bin
Mar 31 20:16:25 greer kernel: e100: eth0 NIC Link is Up 100 Mbps Full Duplex
Mar 31 20:54:10 greer kernel: e100 0000:00:0d.0: firmware: using built-in
firmware e100/d101m_ucode.bin
Mar 31 20:54:11 greer kernel: e100: eth0 NIC Link is Up 100 Mbps Full Duplex

--
Stan


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BB408D1.9060402(a)hardwarefreak.com
From: briand on
On Wed, 31 Mar 2010 21:45:37 -0500
Stan Hoeppner <stan(a)hardwarefreak.com> wrote:

> Got this error message stream on a server today. Never seen this
> before. Does this mean my NIC is going south? Or is something else
> going on? I tried manualy bringing the NIC back up but ifdown/up
> didn't fix the problem. Had to reboot the server to fix it. eth0
> seems to be working fine now.

can't comment on the problem, however, if the driver is a module you
might want to try unloading and reloading the module. that might reset
the card and wouldn't need to reboot.



Brian


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100331200631.0ecd6635(a)windy.deldotd.com
From: Stan Hoeppner on
briand(a)aracnet.com put forth on 3/31/2010 10:06 PM:
> On Wed, 31 Mar 2010 21:45:37 -0500
> Stan Hoeppner <stan(a)hardwarefreak.com> wrote:
>
>> Got this error message stream on a server today. Never seen this
>> before. Does this mean my NIC is going south? Or is something else
>> going on? I tried manualy bringing the NIC back up but ifdown/up
>> didn't fix the problem. Had to reboot the server to fix it. eth0
>> seems to be working fine now.
>
> can't comment on the problem, however, if the driver is a module you
> might want to try unloading and reloading the module. that might reset
> the card and wouldn't need to reboot.

The driver is built into the kernel. Thanks for the suggestion though.

--
Stan


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BB410D7.9090306(a)hardwarefreak.com
From: Aioanei Rares on
Stan Hoeppner wrote:
> briand(a)aracnet.com put forth on 3/31/2010 10:06 PM:
>
>> On Wed, 31 Mar 2010 21:45:37 -0500
>> Stan Hoeppner <stan(a)hardwarefreak.com> wrote:
>>
>>
>>> Got this error message stream on a server today. Never seen this
>>> before. Does this mean my NIC is going south? Or is something else
>>> going on? I tried manualy bringing the NIC back up but ifdown/up
>>> didn't fix the problem. Had to reboot the server to fix it. eth0
>>> seems to be working fine now.
>>>
>> can't comment on the problem, however, if the driver is a module you
>> might want to try unloading and reloading the module. that might reset
>> the card and wouldn't need to reboot.
>>
>
> The driver is built into the kernel. Thanks for the suggestion though.
>
>
My 2 cents : it's a software problem aka kernel bug which should be
reported.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BB483A0.4000902(a)gmail.com