From: Paul Fulghum <paulkf@microgate.com>
To: Klaus Dittrich <kladit@t-online.de>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-bk5 scheduling while atomic
Date: 22 Jun 2004 10:02:06 -0500 [thread overview]
Message-ID: <1087916526.2004.3.camel@deimos.microgate.com> (raw)
In-Reply-To: <20040622135529.GA838@xeon2.local.here>
On Tue, 2004-06-22 at 08:55, Klaus Dittrich wrote:
> System smp (2 x XEON, I7505) preemptive
>
> With kernel-2.6.7-bk5 I get a lot of
> "kernel: bad: scheduling while atomic!" messages
> during startup.
>
> 2.6.7 runs fine using the basically the same configuration.
>
> Did anybody else see this ?
Yes, same here.
kernel-2.6.7-bk5
SMP (2 x Pentium II)
2.6.7 runs fine.
> Here is an excerpt of /var/log/messages ..
The specific messages are different in my log
but the structure is the same: floods of
scheduling while atomic messages.
--
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2004-06-22 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 13:55 2.6.7-bk5 scheduling while atomic Klaus Dittrich
2004-06-22 15:02 ` Paul Fulghum [this message]
2004-06-22 16:56 ` Christian Kujau
2004-06-23 17:01 ` Paul Fulghum
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=1087916526.2004.3.camel@deimos.microgate.com \
--to=paulkf@microgate.com \
--cc=kladit@t-online.de \
--cc=linux-kernel@vger.kernel.org \
/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