From: Robert Love <rml@tech9.net>
To: thunder7@xs4all.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: pre-empt and smp in 2.5.37 - is it supposed to work?
Date: 20 Sep 2002 16:09:22 -0400 [thread overview]
Message-ID: <1032552562.966.832.camel@phantasy> (raw)
In-Reply-To: <20020920200441.GA3677@middle.of.nowhere>
On Fri, 2002-09-20 at 16:04, Jurriaan wrote:
> I get a large screen full of hex addresses even before my framebuffer
> activates, so I wonder if breakage when using preempt and smp is a known
> issue in 2.5.37 or not?
You need this yet-to-be-merged patch. It should work fine with it.
It is just an overzealous debugging test..
Robert Love
diff -urN linux-2.5.37/kernel/sched.c linux/kernel/sched.c
--- linux-2.5.37/kernel/sched.c Fri Sep 20 11:20:32 2002
+++ linux/kernel/sched.c Fri Sep 20 15:49:05 2002
@@ -940,8 +940,17 @@
struct list_head *queue;
int idx;
- if (unlikely(in_atomic()))
- BUG();
+ /*
+ * Test if we are atomic. Since do_exit() needs to call into
+ * schedule() atomically, we ignore that path for now.
+ * Otherwise, whine if we are scheduling when we should not be.
+ */
+ if (likely(current->state != TASK_ZOMBIE)) {
+ if (unlikely(in_atomic())) {
+ printk(KERN_ERR "bad: scheduling while atomic!\n");
+ dump_stack();
+ }
+ }
#if CONFIG_DEBUG_HIGHMEM
check_highmem_ptes();
next prev parent reply other threads:[~2002-09-20 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 20:04 pre-empt and smp in 2.5.37 - is it supposed to work? Jurriaan
2002-09-20 20:09 ` Robert Love [this message]
2002-09-20 21:02 ` pre-empt and smp in 2.5.37 - is it supposed to work? [contains 2 oopses, one in set_cpus_allowed, one in md code] Jurriaan
2002-09-20 21:29 ` Robert Love
2002-09-21 5:43 ` Jurriaan
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=1032552562.966.832.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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