From: Nathan Lynch <nathanl@austin.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>,
Dave Hansen <haveblue@us.ibm.com>,
"Matthew C. Dobson [imap]" <colpatch@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sched domains bringup race?
Date: Thu, 22 Jul 2004 16:55:40 -0500 [thread overview]
Message-ID: <1090533339.3041.13.camel@booger> (raw)
In-Reply-To: <40FB78D5.1070604@yahoo.com.au>
On Mon, 2004-07-19 at 02:31, Nick Piggin wrote:
> Keshavamurthy Anil S wrote:
> > Even on my system which is Intel 865 chipset (P4 with HT enabled system)
> > I see a bug check somewhere in the schedular_tick during boot.
> > However if I move the sched_init_smp() after do_basic_setup() the
> > kernel boots without any problem. Any clue here?
>
> There shouldn't be any problem doing that if we have to, obviously we
> need to know why. Is it possible that cpu_sibling_map, or one of the
> CPU masks isn't set up correctly at the time of the call?
In 2.6.8-rc1-mm1 at least, backing this patch out fixed it for me on
ppc64:
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.8-rc1/2.6.8-rc1-mm1/broken-out/detect-too-early-schedule-attempts.patch
Code with statements of the form:
if (system_state == SYSTEM_BOOTING)
/* do something boot-specific */
else
/* do something assuming system_state == SYSTEM_RUNNING */
is broken by this change. Parts of the cpu bringup code in arch/ppc64
do this (and thus need to be fixed if the above change is kept).
Chances are there is similar code in some x86 setups.
Nathan
next prev parent reply other threads:[~2004-07-22 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 2:13 sched domains bringup race? Dave Hansen
2004-07-16 3:03 ` Nick Piggin
2004-07-16 3:30 ` Dave Hansen
2004-07-16 3:46 ` Nick Piggin
2004-07-16 5:27 ` Nick Piggin
2004-07-18 20:45 ` Keshavamurthy Anil S
2004-07-19 7:31 ` Nick Piggin
2004-07-22 21:55 ` Nathan Lynch [this message]
2004-07-22 23:23 ` Keshavamurthy Anil S
2004-07-23 0:33 ` Nick Piggin
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=1090533339.3041.13.camel@booger \
--to=nathanl@austin.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=colpatch@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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