From: Len Brown <len.brown@intel.com>
To: Phil White <cerise@littlegreenmen.armory.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 doesn't see my 2nd CPU
Date: 25 Feb 2004 15:24:00 -0500 [thread overview]
Message-ID: <1077740640.5913.433.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F2BC9@hdsmsx402.hd.intel.com>
> CONFIG_HIGHMEM64G=y
> CONFIG_X86_PAE=y
> ACPI: S3 and PAE do not like each other for now, S3 disabled.
Try disabling PAE mode -- it only slows down your 1GB system anyway and
who knows -- maybe that is what broke.
> Booting processor 1/1 eip 2000
> Unable to handle kernel paging request<1>Unable to handle kernel
> paging request at virtual address 3f83ec0d
re: acpi=force
ACPI and MPS both recognize your 2nd processor as LAPIC ID 1, and the
smpboot code that tries to start it up and fails is common to both modes
-- so I don't see an MPS or ACPI-specific issue here.
> Another update. The second processor still isn't working,
> but with args noapic, noirqbalance, and
> maxcpus=4 (even though there's only 2 cpus),
> the APIC problems go away. They're replaced with
> spurious interrupts however.
I don't see these options having any effect on the root problem, which
is that the kernel faults when starting the 2nd processor. Note that
"noapic" technically isn't supported on an MPS compliant SMP system.
-Len
next parent reply other threads:[~2004-02-25 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F2BC9@hdsmsx402.hd.intel.com>
2004-02-25 20:24 ` Len Brown [this message]
2004-02-25 7:33 2.6.3 doesn't see my 2nd CPU Phil White
-- strict thread matches above, loose matches on Subject: below --
2004-02-21 3:17 Phil White
2004-02-21 4:12 ` Zwane Mwaikambo
2004-02-21 4:22 ` Andrew Morton
2004-02-21 21:52 ` Phil White
2004-02-22 4:46 ` 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=1077740640.5913.433.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=cerise@littlegreenmen.armory.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