From: Andrea Arcangeli <andrea@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: oopsen with rc3-aa3
Date: Tue, 30 Jul 2002 01:44:33 +0200 [thread overview]
Message-ID: <20020729234433.GL1201@dualathlon.random> (raw)
In-Reply-To: <20020729231203.GA6314@714-cm.cps.unizar.es>
On Tue, Jul 30, 2002 at 01:12:03AM +0200, J.A. Magallon wrote:
> But -rc3-jam3 bombed on the dual-p4xeon box, but works on a PIII laptop.
I decored the oops and in short rq_target->idle is NULL, so then
resched_task bugs out while reading p->need_resched.
it's the hyperthreading support that bugs out infact.
I had a look and this should fix it (the first one is just a theorical
bug, since it's under an ifdef i386 cpu_number_map is an identity, the
++ thing was the reason I think). Can you test it?
--- 2.4.19rc3aa3/kernel/sched.c.~1~ Sun Jul 28 18:12:19 2002
+++ 2.4.19rc3aa3/kernel/sched.c Tue Jul 30 01:42:08 2002
@@ -490,7 +490,7 @@ static inline void pull_task(runqueue_t
*/
static inline int find_idle_package(int this_cpu)
{
- int i = this_cpu + 1;
+ int i = cpu_number_map(this_cpu) + 1;
if (i == smp_num_cpus)
i = 0;
@@ -500,7 +500,7 @@ static inline int find_idle_package(int
physical = cpu_logical_map(i);
sibling = cpu_sibling_map[physical];
- if (i++ == smp_num_cpus)
+ if (++i == smp_num_cpus)
i = 0;
if (idle_cpu(physical) && idle_cpu(sibling))
return physical;
Andrea
next prev parent reply other threads:[~2002-07-29 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 17:42 oopsen with rc3-aa3 J.A. Magallon
2002-07-29 18:10 ` Andrea Arcangeli
2002-07-29 22:35 ` J.A. Magallon
2002-07-29 22:42 ` J.A. Magallon
2002-07-29 22:47 ` Andrea Arcangeli
2002-07-29 23:12 ` J.A. Magallon
2002-07-29 23:44 ` Andrea Arcangeli [this message]
2002-07-30 0:21 ` J.A. Magallon
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=20020729234433.GL1201@dualathlon.random \
--to=andrea@suse.de \
--cc=jamagallon@able.es \
--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.