From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.34-mm2 kernel BUG at sched.c:944! only with CONFIG_PREEMPT=y
Date: 12 Sep 2002 13:46:45 -0600 [thread overview]
Message-ID: <1031860005.1990.394.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1031840041.1990.378.camel@spc9.esa.lanl.gov>
On Thu, 2002-09-12 at 08:14, Steven Cole wrote:
> I got the following BUG at sched.c:944! with 2.5.34-mm2 and PREEMPT on.
> This was repeatable.
>
> With no PREEMPT, 2.5.34-mm2 booted and is running fine. Some other
> options used: SMP, HUGETLB_PAGE, HIGHPTE, HIGHMEM4G.
The above also occurred with no SMP.
I backed out Changeset 1.606 which did this in kernel/sched.c:
- if (unlikely(in_interrupt()))
+ if (unlikely(in_atomic()))
and 2.5.34-mm2 was able to boot with CONFIG_PREEMPT=y.
Obviously, this is not a fix of any kind, but shows that the scheduler
may be being called with a preemption lock.
Steven
next prev parent reply other threads:[~2002-09-12 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 14:14 2.5.34-mm2 kernel BUG at sched.c:944! only with CONFIG_PREEMPT=y Steven Cole
2002-09-12 19:46 ` Steven Cole [this message]
2002-09-13 20:41 ` Arador
2002-09-13 21:20 ` Steven Cole
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=1031860005.1990.394.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=akpm@zip.com.au \
--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;
as well as URLs for NNTP newsgroup(s).