From: Ashok Raj <ashok.raj@intel.com>
To: jensmh@gmx.de
Cc: Ashok Raj <ashok.raj@intel.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.1 lost cpu, was: 2.6.16-rc5 'lost' cpu
Date: Fri, 7 Apr 2006 13:53:27 -0700 [thread overview]
Message-ID: <20060407135327.A27253@unix-os.sc.intel.com> (raw)
In-Reply-To: <200604072227.58594.jensmh@gmx.de>; from jensmh@gmx.de on Fri, Apr 07, 2006 at 10:27:56PM +0200
On Fri, Apr 07, 2006 at 10:27:56PM +0200, jensmh@gmx.de wrote:
> Ashok Raj writes:
> > On Fri, Apr 07, 2006 at 06:45:36PM +0200, jensmh@gmx.de wrote:
> >
> > Oh well, seems like that CPU has trouble booting, per message below
> > we seemed to start it, but processor didnt run startup code... Suspect its a
> > failing part probably..
> >
> > > CPU1: Intel P4/Xeon Extended MCE MSRs (12) available
> > > CPU1: Thermal monitoring enabled
> > > CPU1: Intel(R) Xeon(TM) CPU 2.80GHz stepping 09
> > > Booting processor 2/6 eip 2000
>
> shouldn't that be "Booting processor 2/_4_ eip 2000"?
I agree the message is not clear.. but the number is the APIC id of the cpu
its trying to boot..
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
-----------------------------------^^^^^^^
Processor #6 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
Processor #1 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
Processor #7 15:2 APIC version 20
next prev parent reply other threads:[~2006-04-07 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 5:05 2.6.16-rc5 'lost' cpu jensmh
2006-03-02 12:21 ` Geert Uytterhoeven
2006-03-02 15:41 ` Zwane Mwaikambo
2006-03-02 21:37 ` jensmh
2006-03-03 17:54 ` Zwane Mwaikambo
2006-03-03 18:30 ` Ashok Raj
2006-04-07 16:45 ` 2.6.16.1 lost cpu, was: " jensmh
2006-04-07 20:22 ` Ashok Raj
2006-04-07 20:27 ` jensmh
2006-04-07 20:53 ` Ashok Raj [this message]
2006-04-08 11:55 ` Zwane Mwaikambo
2006-03-06 20:23 ` Bill Davidsen
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=20060407135327.A27253@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=jensmh@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.