From: Ashok Raj <ashok.raj@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
ntl@pobox.com, ashok.raj@intel.com, olel@ans.pl,
venkatesh.pallipadi@intel.com, linux-kernel@vger.kernel.org,
suresh.b.siddha@intel.com, rajesh.shah@intel.com, ak@muc.de,
zwane@arm.linux.org.uk
Subject: Re: More than 8 CPUs detected and CONFIG_X86_PC cannot handle it on 2.6.16-rc6
Date: Wed, 15 Mar 2006 10:09:29 -0800 [thread overview]
Message-ID: <20060315100928.A19557@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060314233138.009414b4.akpm@osdl.org>; from akpm@osdl.org on Tue, Mar 14, 2006 at 11:31:38PM -0800
On Tue, Mar 14, 2006 at 11:31:38PM -0800, Andrew Morton wrote:
> > > see:
> > >
> > > Subject: i386 cpu hotplug bug - instant reboot when onlining secondary
> > >
> > > http://lkml.org/lkml/2006/2/19/186
> > Works for me. But I saw a warning.
>
> Guys, will you please stop being so cryptic? What worked for you? What
> warning? wtf is going on? Who owns this problem, whatever it is?
Nathan's problem is different, its nothing related to this thread.
Appears that a PIII box had trouble to bring a CPU back online after it was
just offlined. Iam not able to reproduce it with the systems i have here.
I have tried a PIII box itself, and also a x86_64 system booting a i386 kernel
and all seems to work ok.
Zwane was attempting to trace Nathan's issue with some experimental patches
but dont think it went far along yet.
> > - gdt = (struct desc_struct *)get_zeroed_page(GFP_KERNEL);
> > + gdt = (struct desc_struct *)get_zeroed_page(GFP_ATOMIC);
>
It might help to post with the actual warning, so we can understand why this
fix is necessary.
--
Cheers,
Ashok Raj
- Open Source Technology Center
next prev parent reply other threads:[~2006-03-15 18:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 2:04 More than 8 CPUs detected and CONFIG_X86_PC cannot handle it on 2.6.16-rc6 Krzysztof Oledzki
2006-03-12 5:03 ` Andrew Morton
2006-03-12 11:04 ` Krzysztof Oledzki
2006-03-12 11:25 ` Andrew Morton
2006-03-12 13:05 ` Krzysztof Oledzki
2006-03-12 15:35 ` Venkatesh Pallipadi
2006-03-12 21:13 ` Krzysztof Oledzki
2006-03-12 22:30 ` Andrew Morton
2006-03-13 19:36 ` Ashok Raj
2006-03-13 19:51 ` Andrew Morton
2006-03-13 20:05 ` Ashok Raj
2006-03-13 22:22 ` Andrew Morton
2006-03-13 23:04 ` Ashok Raj
2006-03-15 5:44 ` Nathan Lynch
2006-03-15 6:18 ` Shaohua Li
2006-03-15 7:31 ` Andrew Morton
2006-03-15 9:37 ` [PATCH] No need to protect current->group_info in sys_getgroups(), in_group_p() and in_egroup_p() Eric Dumazet
2006-03-20 19:09 ` [PATCH] Use unsigned int types for a faster bsearch Eric Dumazet
2006-03-22 5:06 ` [PATCH] Use __read_mostly on some hot fs variables Eric Dumazet
2006-03-22 5:15 ` Nick Piggin
2006-03-22 6:23 ` [RFC, PATCH] avoid some atomics in open()/close() for monothreaded processes Eric Dumazet
2006-03-22 6:41 ` Andrew Morton
2006-03-22 6:59 ` Eric Dumazet
2006-03-22 7:03 ` Andrew Morton
2006-03-15 18:09 ` Ashok Raj [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-15 10:50 More than 8 CPUs detected and CONFIG_X86_PC cannot handle it on 2.6.16-rc6 Chuck Ebbert
2006-03-15 15:44 ` Krzysztof Oledzki
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=20060315100928.A19557@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntl@pobox.com \
--cc=olel@ans.pl \
--cc=rajesh.shah@intel.com \
--cc=shaohua.li@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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