From: Shaohua Li <shaohua.li@intel.com>
To: Kevin Baradon <kevin.baradon@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc1: kernel only boots one CPU on HT system
Date: Tue, 25 Apr 2006 09:53:48 +0800 [thread overview]
Message-ID: <1145930028.19994.68.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <200604241926.25239.Kevin.Baradon@gmail.com>
On Mon, 2006-04-24 at 19:26 +0200, Kevin Baradon wrote:
> Le Lundi 24 Avril 2006 03:57, Shaohua Li a écrit :
> > Hi,
>
> Hello,
> >
> > On Sun, 2006-04-23 at 14:15 -0700, Andrew Morton wrote:
> > > Kevin Baradon <kevin.baradon@gmail.com> wrote:
> > > > Hello,
> > > >
> > > > Starting with kernel 2.6.17-rc1 (also happens with 2.6.17-rc2), second
> > > > logical-CPU of my Hyperthreading system no longer boots.
> > > >
> > > > I tracked up changes in APIC code, and it appears reverting commit
> > > > 7c5c1e427b5e83807fd05419d1cf6991b9d87247 fixes this bug.
> > >
> > > That helps heaps, thanks.
> >
> > The commit doesn't look like the root cause to me. BIOS already assigns
> > unique id to ioapic, and the cpu family is 15, so with/without the patch
> > the code path hasn't any difference. Kevin, can you please make a clean
> > build and check if the patch is the real cause?
> >
>
> You were right. Reverting this commit helps sometimes, but doesn't work
> reliably. When my computer booted this morning, I've had only one CPU
> detected. I've tried booting several times, even with a complete power down.
> Nothing changed.
>
> I've also tried with kernel 2.6.16-rc6, which booted fine and detected two
> CPUs.
>
> I've applied your small patch. Debugging output is attached.
>
> If you want, I can apply this small patch also to kernel 2.6.16-rc6, and send
> you debugging output.
>
> > If it still doesn't work, you might apply a small change below to
> > include/asm-i386/apic.h, and attach the dmesg, so we could analyze it.
> >
>
> File attached.
The CPU doesn't startup. Sometime ago somebody reported a similar issue
for 2.6.16.1. But the failure isn't reliably triggered. IIRC, there
isn't a solution.
Thanks,
Shaohua
next prev parent reply other threads:[~2006-04-25 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 12:34 Kevin Baradon
2006-04-23 21:15 ` Andrew Morton
2006-04-24 1:57 ` Shaohua Li
2006-04-24 17:26 ` Kevin Baradon
2006-04-25 1:53 ` Shaohua Li [this message]
2006-05-15 21:26 ` Kevin Baradon
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=1145930028.19994.68.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=akpm@osdl.org \
--cc=kevin.baradon@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®