Thread (3 messages) 3 messages, 2 authors, 2012-07-20

Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)

From: Stanislaw Gruszka <hidden>
Date: 2012-07-20 09:48:08
Also in: linux-next, linux-wireless, lkml

On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote:
On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell [off-list ref] wrote:
quoted
Hi all,

Changes since 20120716:
Not sure what the root cause of this issue is.

I see the following call-trace in linux-next (next-20120717).

[   23.431889] ------------[ cut here ]------------
[   23.431896] WARNING: at lib/debugobjects.c:261 debug_print_object+0x8e/0xb0()
[   23.431897] Hardware name: <HIDDEN>
[   23.431901] ODEBUG: free active (active state 0) object type:
timer_list hint: delayed_work_timer_fn+0x0/0x40
There are few delayed works on hci_dev structure, it's hard to say which
one is not stopped before kfree.
# CONFIG_DEBUG_OBJECTS_WORK is not set
If you enable that option, it should show which delayed work is causing trouble.

Stanislaw
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help