From: Robert Love <rml@tech9.net>
To: Simon Michael <simon@joyful.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM 2.5.52] PREEMPT broken (was "bad: scheduling while atomic!" errors during boot)
Date: 23 Dec 2002 15:33:13 -0500 [thread overview]
Message-ID: <1040675593.962.6.camel@icbm> (raw)
In-Reply-To: <87vg1kwnv2.fsf_-_@joyful.com>
On Mon, 2002-12-23 at 14:12, Simon Michael wrote:
> Yup, that's what I meant. Thanks to another private emailer for the idea.
>
> Robert, I think you are the one who'll want to hear of this.
The problem is actually unrelated to preempt, but only with preempt can
we detect it. So, yes, disabling CONFIG_PREEMPT merely hides the debug
message.
I got your post from earlier, thanks. The relevant maintainers need to
work on it.
Robert Love
prev parent reply other threads:[~2002-12-23 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 23:19 [PROBLEM 2.5.52] "bad: scheduling while atomic!" errors during boot of 2.5.52, 2.5.51, 2.5.50 Simon Michael
2002-12-23 8:20 ` Simon Michael
2002-12-23 19:12 ` [PROBLEM 2.5.52] PREEMPT broken (was "bad: scheduling while atomic!" errors during boot) Simon Michael
2002-12-23 20:33 ` Robert Love [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=1040675593.962.6.camel@icbm \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@joyful.com \
/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