From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)
Date: Fri, 20 Jul 2012 11:47:49 +0200 [thread overview]
Message-ID: <20120720094748.GA16598@redhat.com> (raw)
In-Reply-To: <CA+icZUWXire09owq2Q9bN=C+VKuzSG+48Cz3-Ex+ZaTtGrEmQA@mail.gmail.com>
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.
Stanislaw
next prev parent reply other threads:[~2012-07-20 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 18:06 linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?) Sedat Dilek
2012-07-20 9:47 ` Stanislaw Gruszka [this message]
2012-07-20 9:53 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120720094748.GA16598@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).