From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: Markus Schoder <lists@gammarayburst.de>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM with 2.6.18: BUG: scheduling while atomic
Date: Wed, 27 Sep 2006 22:07:13 +0200 [thread overview]
Message-ID: <20060927200713.GA20282@elte.hu> (raw)
In-Reply-To: <20060927124904.1a0d94c2.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> > Sep 24 13:29:24 gondolin kernel: [<ffffffff8026ef30>] default_idle+0x0/0x60
> > Sep 24 13:29:24 gondolin kernel: [<ffffffff8024f276>] cpu_idle+0x96/0xb0
> > Sep 24 13:29:24 gondolin kernel: [<ffffffff805e5641>] start_secondary+0x4f1/0x500
>
> This might indicate that some code somewhere forgot to do
> spin_unlock/preempt_enable/kunmap_atomic/whatever.
>
> Ingo, do you have a current version of the patch which allows us to
> locate the culprit?
first the nvidia thing needs to be removed from that kernel. (wouldnt be
the first time it messes up the preempt count)
i have the PREEMPT_TRACE feature in the latency-tracer patch-queue. I've
merged it to 2.6.18-mm1 and have uploaded a combo patch to:
http://redhat.com/~mingo/latency-tracing-patches/latency-tracing-2.6.18-mm1.patch
CONFIG_DEBUG_PREEMPT should be enabled, that will activate
CONFIG_PREEMPT_TRACE. No need to enable latency tracing itself.
Ingo
prev parent reply other threads:[~2006-09-27 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 12:44 PROBLEM with 2.6.18: BUG: scheduling while atomic Markus Schoder
2006-09-27 19:49 ` Andrew Morton
2006-09-27 20:07 ` Ingo Molnar [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=20060927200713.GA20282@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@gammarayburst.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