Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280()

WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280() · Alex Villacís Lasso <hidden> · 2012-04-21
Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280() · Alex Villacís Lasso <hidden> · 2012-05-02
Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280() · Alex Villacís Lasso <hidden> · 2012-05-02
Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280() · Francois Romieu <romieu@fr.zoreil.com> · 2012-05-02
Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280() · Alex Villacís Lasso <hidden> · 2012-05-02
Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280() · Francois Romieu <romieu@fr.zoreil.com> · 2012-05-03

From: Francois Romieu <romieu@fr.zoreil.com>
Date: 2012-05-03 06:53:22

(please avoid posting twice)

Alex Villacís Lasso [off-list ref] :
[...]

I am currently away from the target computer. How should I check for this? lspci?

lspci can not tell much. Use 'dmesg | grep XID' instead.

A complete dmesg would be welcome.

It could help to know a few things :
- does the problem qualify as a regression since some kernel version ?
  If so which one ?
- can it be reproduced with a kernel that has not been vbox tainted ?
- does networking recover ?

Thanks.

-- 
Ueimor

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help