From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: mingo@elte.hu, lkml <linux-kernel@vger.kernel.org>,
Zwane Mwaikambo <zwane@zwane.ca>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: 2.6.7-rc1-bk: SMT scheduler bug / crashes on kernel boot
Date: Wed, 26 May 2004 21:45:03 +1000 [thread overview]
Message-ID: <40B4833F.1060700@yahoo.com.au> (raw)
In-Reply-To: <1085571285.2666.75.camel@imp.csi.cam.ac.uk>
Anton Altaparmakov wrote:
> On Wed, 2004-05-26 at 12:28, Nick Piggin wrote:
>
>>Anton Altaparmakov wrote:
>>
>>
>>>The kernel shows a warning about the number of siblings being 2 but only
>>>1 being detected. Perhaps this is the cause of the problem. Even if
>>
>>Probably this is the cause of the problem.
>>
>>What is the exact message?
>
>
> You can see it in the PNG I attached in the original post. But here it
> is copied out:
>
> WARNING: 1 siblings found for CPU0, should be 2
>
OK thanks... I think I even wrote that :P
The problem is smp_num_siblings is set to 2, but phys_proc_id
doesn't seem to be set up right (or it could be cpu_callout_map).
That would cause the sched-domains to get set up wrong, sure. Maybe
we should just go bug in this case? Or try to fix up?
Anyone have any idea why this is happening?
next prev parent reply other threads:[~2004-05-26 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1085568719.2666.53.camel@imp.csi.cam.ac.uk>
2004-05-26 11:13 ` 2.6.7-rc1-bk: SMT scheduler bug / crashes on kernel boot Nick Piggin
[not found] ` <1085572902.2666.105.camel@imp.csi.cam.ac.uk>
2004-05-26 12:10 ` Nick Piggin
[not found] ` <1085569838.2666.60.camel@imp.csi.cam.ac.uk>
2004-05-26 11:28 ` Nick Piggin
[not found] ` <1085571285.2666.75.camel@imp.csi.cam.ac.uk>
2004-05-26 11:44 ` Ingo Molnar
2004-05-26 11:45 ` Nick Piggin [this message]
2004-05-26 15:54 Nakajima, Jun
2004-05-26 20:52 ` Zwane Mwaikambo
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=40B4833F.1060700@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=aia21@cam.ac.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zwane@zwane.ca \
/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