[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120720094748.GA16598@redhat.com>
Date: Fri, 20 Jul 2012 11:47:49 +0200
From: Stanislaw Gruszka <sgruszka@...hat.com>
To: Sedat Dilek <sedat.dilek@...il.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux-bluetooth@...r.kernel.org, linux-usb@...r.kernel.org,
wireless <linux-wireless@...r.kernel.org>
Subject: Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb
related?)
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@...b.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.
Stanislaw
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists