Messages in this thread | | | Date | Fri, 20 Jul 2012 11:53:20 +0200 | Subject | Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?) | From | Sedat Dilek <> |
| |
On Fri, Jul 20, 2012 at 11:47 AM, Stanislaw Gruszka <sgruszka@redhat.com> wrote: > On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote: >> On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: >> > 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. >
OK, thanks for the explanations & hints! I will activate that kconfig-option.
FYI: With yesterday's linux-next (next-20120719) I didn't trap into this regression (same kernel-config + several bootups).
- Sedat -
> Stanislaw
| |