LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Quel Qun <kelk1@comcast.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>, Ingo Molnar <mingo@elte.hu>,
marcel@holtmann.org
Subject: Re: Kernel oops with bluetooth usb dongle
Date: Mon, 18 Feb 2008 14:12:25 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802181245370.7583@apollo.tec.linutronix.de> (raw)
In-Reply-To: <021820080001.29293.47B8CAD10009FD170000726D2207000953CE05040A05@comcast.net>
On Mon, 18 Feb 2008, Quel Qun wrote:
Added bluetooth wizards to CC
> > Can you please enable CONFIG_SLUB_DEBUG=y and CONFIG_SLUB_DEBUG_ON=y
> > and give it another try?
> >
> > If we can not catch it that way, I'll whip up a patch which points us
> > to the code which added the offending timer.
> >
> Hi,
>
> Note: I switched to 2.6.25-rc2. The only new thing I see is this message:
>
> hci_cmd_task: hci0 command tx timeout
>
> This comes from net/bluetooth/hci_core.c, line 1547
>
> There is indeed a timeout message in the log (at the end of this
> email). I tried to boot with slub_debug but did not get anything
> more. slabinfo -v does not report anything either.
>
> Crash log:
>
> hci_cmd_task: hci0 command tx timeout
> BUG: unable to handle kernel paging request at 6b6b6b6b
We got some more info ---------------------------^^^^^^^^
#define POISON_FREE 0x6b /* for use-after-free poisoning */
So the timer is in an allocated data structure, which is
freed without having removed the timer first.
> Sorry for the meager yield.
Hey, we know already more :)
Marcel, any idea on this one ?
Thanks,
tglx
next prev parent reply other threads:[~2008-02-18 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 0:01 Quel Qun
2008-02-18 12:43 ` Sebastian Siewior
2008-02-18 13:12 ` Thomas Gleixner [this message]
2008-02-19 21:07 ` Marcel Holtmann
2008-02-20 0:14 ` Thomas Gleixner
2008-02-20 8:11 ` Thomas Gleixner
2008-02-21 7:30 ` Dave Young
-- strict thread matches above, loose matches on Subject: below --
2008-02-26 15:49 Quel Qun
2008-02-26 0:03 Quel Qun
2008-02-26 3:13 ` Marcel Holtmann
2008-02-28 1:03 ` Dave Young
2008-02-28 1:37 ` Dave Young
2008-02-22 2:40 Quel Qun
2008-02-22 3:23 ` Dave Young
2008-02-22 7:23 ` Thomas Gleixner
2008-02-22 11:34 ` David Woodhouse
2008-02-22 11:43 ` Thomas Gleixner
2008-02-21 16:49 Quel Qun
2008-02-21 19:37 ` Thomas Gleixner
2008-02-16 21:37 Quel Qun
2008-02-16 23:59 ` Thomas Gleixner
2008-02-16 0:41 Quel Qun
2008-02-16 11:05 ` Jiri Kosina
2008-02-16 11:50 ` Thomas Gleixner
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=alpine.LFD.1.00.0802181245370.7583@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=jkosina@suse.cz \
--cc=kelk1@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mingo@elte.hu \
--subject='Re: Kernel oops with bluetooth usb dongle' \
/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
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).