From: Keith Mannthey <kmannth@gmail.com>
To: Bharath Ramesh <krosswindz@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Only one processor detected in 8-Way opteron in 32-bit mode
Date: Fri, 2 Dec 2005 14:07:47 -0800 [thread overview]
Message-ID: <a762e240512021407p5a31c0daid902352625701ca2@mail.gmail.com> (raw)
In-Reply-To: <c775eb9b0512020732v3f41f91fpb3b4b61b0b539d92@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
Welcome to hardware bring up. Ok I looked a little closer at the
story. In x86_64 the only check for valid apic is apicid < MAX_APICS
which make sense to me.
I386 has this concept of version. Where the valid check is diffrent
if (version >= 0x14)
return apicid < 0xff;
else
return apicid < 0xf;
Now the patch is sent before was a litle in haste. Your apic version
is 16. The valid check returns false because apicid is greater that
0xf (0x15). Most likey the bios entry for the apic version is wrong
but I don't know much about that or why it matters.
So what does this all mean. Legacy.....
Give this patch a whirl.
Thanks,
Keith
[-- Attachment #2: apicid.fix --]
[-- Type: application/octet-stream, Size: 348 bytes --]
--- arch/i386/kernel/mpparse.c.orig 2005-12-01 15:20:51.000000000 -0800
+++ arch/i386/kernel/mpparse.c 2005-12-01 15:21:19.000000000 -0800
@@ -112,9 +112,10 @@
#else
static int MP_valid_apicid(int apicid, int version)
{
- if (version >= 0x14)
+/* if (version >= 0x14)
return apicid < 0xff;
else
+*/
return apicid < MAX_APICS;
}
#endif
next prev parent reply other threads:[~2005-12-02 22:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 21:15 Only one processor detected in 8-Way opteron in 32-bit mode Bharath Ramesh
2005-12-01 23:27 ` Keith Mannthey
2005-12-02 0:51 ` Bharath Ramesh
2005-12-02 1:12 ` Bharath Ramesh
2005-12-02 1:42 ` Keith Mannthey
2005-12-02 2:32 ` Bharath Ramesh
2005-12-02 15:32 ` Bharath Ramesh
2005-12-02 22:07 ` Keith Mannthey [this message]
[not found] ` <c775eb9b0512021534y693f3bf3i4b85b7cb0dcb08b6@mail.gmail.com>
[not found] ` <a762e240512021701q4ea436d9u563704c4daeb7584@mail.gmail.com>
2005-12-03 2:06 ` Bharath Ramesh
2005-12-06 21:32 ` Bill Davidsen
2005-12-14 2:02 ` Bharath Ramesh
2005-12-03 22:21 ` Andi Kleen
2005-12-04 14:24 ` Bharath Ramesh
2005-12-04 17:27 ` Matti Aarnio
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=a762e240512021407p5a31c0daid902352625701ca2@mail.gmail.com \
--to=kmannth@gmail.com \
--cc=krosswindz@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 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.