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>
Subject: Re: Kernel oops with bluetooth usb dongle
Date: Sun, 17 Feb 2008 00:59:37 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802162353210.7583@apollo.tec.linutronix.de> (raw)
In-Reply-To: <021620082137.23325.47B757B400051FE100005B1D2209224627CE05040A05@comcast.net>
On Sat, 16 Feb 2008, Quel Qun wrote:
> > Please also enable CONFIG_DEBUG_LIST=y, which should catch the place
> > where a list corruption happens.
>
> Thank you for the hand holding. I must admit I do not anything
> about kernel debugging.
>
> With or without nohz=off, the crashes are very similar. It looks
> like it fails to execute list_add_tail(&timer->entry, vec), line 294
> of kernel/timer.c.
Yup, that's what I suspected. The list is corrupted:
> list_add corruption. prev->next should be next (c047e704), but was 00000000. (prev=ddcca118).
> list_add corruption. prev->next should be next (c047e77c), but was 00000001. (prev=f644bd98).
Unfortunately we only see that the list is corrupted but not which
code caused it. This looks like something forgot to delete the timer
before freeing the datastructure which contains it.
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.
Thanks,
tglx
next prev parent reply other threads:[~2008-02-17 0:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 21:37 Quel Qun
2008-02-16 23:59 ` Thomas Gleixner [this message]
-- 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-18 0:01 Quel Qun
2008-02-18 12:43 ` Sebastian Siewior
2008-02-18 13:12 ` Thomas Gleixner
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
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.0802162353210.7583@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=jkosina@suse.cz \
--cc=kelk1@comcast.net \
--cc=linux-kernel@vger.kernel.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).