From: Andrew Morton <akpm@linux-foundation.org>
To: j_kernel@hoblitt.com
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 11543] New: kernel panic: softlockup in tick_periodic() ???
Date: Thu, 11 Sep 2008 19:57:08 -0700 [thread overview]
Message-ID: <20080911195708.f975e9b6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080912025458.GF27054@hoblitt.com>
On Thu, 11 Sep 2008 16:54:58 -1000 j_kernel@hoblitt.com wrote:
> > The panic code called the kexec code which called mutex_trylock() which
> > called spin_lock_mutex() which then stupidly went and blurted a load of
> > debug stuff because of in_interrupt().
> >
> > Something like this:
> >
> > --- a/include/linux/debug_locks.h~a
> > +++ a/include/linux/debug_locks.h
> > @@ -17,7 +17,7 @@ extern int debug_locks_off(void);
> > ({ \
> > int __ret = 0; \
> > \
> > - if (unlikely(c)) { \
> > + if (!oops_in_progress && unlikely(c)) { \
> > if (debug_locks_off() && !debug_locks_silent) \
> > WARN_ON(1); \
> > __ret = 1; \
> > _
> >
> > might prevent the debugging code from preventing us from finding bugs :(
>
> Do you want me to give that patch a try or sit tight for a bit?
It's be good if you can try it please, see if we can get a cleaner
trace.
next prev parent reply other threads:[~2008-09-12 2:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11543-10286@http.bugzilla.kernel.org/>
2008-09-12 0:02 ` [Bugme-new] [Bug 11543] New: kernel panic: softlockup in tick_periodic() ??? Andrew Morton
2008-09-12 2:54 ` j_kernel
2008-09-12 2:57 ` Andrew Morton [this message]
2008-09-12 9:13 ` Ingo Molnar
2008-09-13 0:13 ` Joshua Hoblitt
2008-09-15 21:06 ` Joshua Hoblitt
2008-09-16 2:54 ` Joshua Hoblitt
2008-09-16 14:14 ` Thomas Gleixner
2008-09-16 17:56 ` Cyrill Gorcunov
2008-09-16 17:57 ` Cyrill Gorcunov
2008-09-17 2:43 j_kernel
2008-09-17 7:13 ` Cyrill Gorcunov
2008-09-17 9:20 ` j_kernel
2008-09-17 9:38 ` Cyrill Gorcunov
2008-09-17 12:59 ` Cyrill Gorcunov
2008-09-17 13:13 ` Ingo Molnar
2008-09-17 13:29 ` Cyrill Gorcunov
2008-09-17 16:27 ` Cyrill Gorcunov
2008-09-17 20:48 ` j_kernel
2008-09-18 7:09 ` Cyrill Gorcunov
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=20080911195708.f975e9b6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=j_kernel@hoblitt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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