From: Paul Fulghum <paulkf@microgate.com>
To: Christian Kujau <evil@g-house.de>
Cc: Klaus Dittrich <kladit@t-online.de>,
linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-bk5 scheduling while atomic
Date: 23 Jun 2004 12:01:59 -0500 [thread overview]
Message-ID: <1088010119.2017.1.camel@deimos.microgate.com> (raw)
In-Reply-To: <40D864BF.9000304@g-house.de>
On Tue, 2004-06-22 at 11:56, Christian Kujau wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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, "me too". but i was not able to get the messages flushed to the
> disk. this is 2.6.7-BK kernel from 2004-06-21 (around 4p.m., GMT+1).
2.6.7-bk6 fixes it for me.
--
Paul Fulghum
paulkf@microgate.com
prev parent reply other threads:[~2004-06-23 17:02 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
2004-06-22 16:56 ` Christian Kujau
2004-06-23 17:01 ` Paul Fulghum [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=1088010119.2017.1.camel@deimos.microgate.com \
--to=paulkf@microgate.com \
--cc=evil@g-house.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.