2009-01-17 18:49:39

by Sitsofe Wheeler

[permalink] [raw]
Subject: warn_slowpath in dev_watchdog

On an ever so slightly modified 2.6.28. I think this only happens when
the upstream router/switch goes out to lunch and packets are being sent.
It is reproducible but only appears on a home network...

[ 204.704065] ------------[ cut here ]------------
[ 204.704074] WARNING: at net/sched/sch_generic.c:226 dev_watchdog
+0x22b/0x240()
[ 204.704080] NETDEV WATCHDOG: eth0 (atl2): transmit timed out
[ 204.704087] Pid: 0, comm: swapper Not tainted 2.6.28skw-00025-gaee9cf6
#7
[ 204.704092] Call Trace:
[ 204.704103] [<c0126373>] warn_slowpath+0x63/0x80
[ 204.704114] [<c0140030>] ? timekeeping_resume+0xc0/0xf0
[ 204.704125] [<c022366e>] ? strlcpy+0x1e/0x60
[ 204.704132] [<c037bf5b>] dev_watchdog+0x22b/0x240
[ 204.704141] [<c03e5fb7>] ? _spin_unlock_irq+0x27/0x30
[ 204.704149] [<c014a04f>] ? trace_hardirqs_on_caller+0x7f/0x150
[ 204.704157] [<c014a12b>] ? trace_hardirqs_on+0xb/0x10
[ 204.704166] [<c012eafd>] run_timer_softirq+0x14d/0x1b0
[ 204.704173] [<c037bd30>] ? dev_watchdog+0x0/0x240
[ 204.704181] [<c012aadd>] ? __do_softirq+0x3d/0x110
[ 204.704188] [<c037bd30>] ? dev_watchdog+0x0/0x240
[ 204.704196] [<c012ab06>] __do_softirq+0x66/0x110
[ 204.704203] [<c012abd8>] ? do_softirq+0x28/0x60
[ 204.704211] [<c012ac05>] do_softirq+0x55/0x60
[ 204.704218] [<c012af67>] irq_exit+0x67/0x80
[ 204.704226] [<c0105745>] do_IRQ+0x65/0xc0
[ 204.704233] [<c0103ea8>] common_interrupt+0x28/0x30
[ 204.704241] [<c014007b>] ? sync_cmos_clock+0x1b/0xb0
[ 204.704251] [<c0277f13>] ? acpi_idle_enter_bm+0x1f2/0x223
[ 204.704259] [<c0337928>] cpuidle_idle_call+0x68/0xc0
[ 204.704265] [<c0101f2b>] cpu_idle+0x3b/0x80
[ 204.704273] [<c03da22d>] rest_init+0x4d/0x60
[ 204.704278] ---[ end trace 2f4b380121b45313 ]---

--
Sitsofe


2009-01-18 01:41:11

by J. K. Cliburn

[permalink] [raw]
Subject: Re: [atl2] warn_slowpath in dev_watchdog

[Modifying subject line and cc'ing netdev]

On Sat, 17 Jan 2009 18:49:18 +0000 (UTC)
Sitsofe Wheeler <[email protected]> wrote:

> On an ever so slightly modified 2.6.28. I think this only happens
> when the upstream router/switch goes out to lunch and packets are
> being sent. It is reproducible but only appears on a home network...
>
> [ 204.704065] ------------[ cut here ]------------
> [ 204.704074] WARNING: at net/sched/sch_generic.c:226 dev_watchdog
> +0x22b/0x240()
> [ 204.704080] NETDEV WATCHDOG: eth0 (atl2): transmit timed out

Please provide your complete dmesg output.

What do you do to reproduce this?

Can you briefly describe the device immediately upstream of the system producing
the warning?

Thanks,
Jay