From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [BUG -rt] Double OOPs - thread_info free race / printk recursive lock
Date: Fri, 4 Aug 2006 14:10:11 -0700 [thread overview]
Message-ID: <20060804211011.GA20342@gnuppy.monkey.org> (raw)
In-Reply-To: <200608041043.06446.dvhltc@us.ibm.com>
On Fri, Aug 04, 2006 at 10:43:05AM -0700, Darren Hart wrote:
> We've seen very rarely over the last few months, on various -rt kernels. The
> latest reproduction is on 2.6.16-rt22 (+some minor fixups). Analysis of the
> vmcore produced by kdump suggests two problems:
> 1) An invalid pointer dereference in cache_flusharray() which causes the page
> fault.
My guess is that this is after some bogus stuff going on after the real event.
> 2) Then printk calls kmalloc when trying to print the oops, which grabs a
> recursive lock and prints a different oops.
Can't say for sure, but this sounds a lot like the problem I've been dealing
with in free_task(). The stack trace is pretty contorted and it's been difficult
to unwind it in any meaningful manner, although I'm making progress. Writing
some tools to deal with this now.
bill
prev parent reply other threads:[~2006-08-04 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 17:43 Darren Hart
2006-08-04 21:10 ` Bill Huey [this message]
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=20060804211011.GA20342@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--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
Powered by JetHome