From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 20 Jul 2012 11:47:49 +0200 From: Stanislaw Gruszka To: Sedat Dilek Cc: Stephen Rothwell , linux-next@vger.kernel.org, LKML , linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org, wireless Subject: Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?) Message-ID: <20120720094748.GA16598@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote: > On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell 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: > [ 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