From: Dave Jones <davej@codemonkey.org.uk>
To: Scott Robert Ladd <scott@coyotegulch.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel for Pentium 4 hyperthreading?
Date: Sun, 15 Dec 2002 19:17:48 +0000 [thread overview]
Message-ID: <20021215191748.GA24207@suse.de> (raw)
In-Reply-To: <FKEAJLBKJCGBDJJIPJLJGEIHDLAA.scott@coyotegulch.com>
On Sun, Dec 15, 2002 at 12:40:59PM -0500, Scott Robert Ladd wrote:
> Dave Jones wrote:
> > Ah, apologies. Yes. In this case, you win. I bit the same problem you
> > had btw with this box in 2.4. You need an updated BIOS. Contact Intel.
>
> I'll ask Intel if there's a BIOS update. Computers are almost as bad as
> games now; the first thing you need to do before using them is patch!
>
> What evokes my curiosity is that the 2.5.51 kernel detects and correctly
> uses the processor siblings, while 2.4.20 does not. Given that 2.5.51 is
> running quite well, I think I'll just stay on the bleeding edge of Linux for
> a while.
I think the problem was a missing MP table in the factory-shipped BIOS.
2.5 used ACPI to enumerate the siblings, whereas the 2.4 ACPI is a
little out of date in that department.
At least that was my random guess when I hit that problem.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-12-15 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 0:52 Linux-2.4.20: bug with radeonfb José Luis Tallón
2002-12-15 0:56 ` Adrian Bunk
2002-12-15 1:11 ` Kernel for Pentium 4 hyperthreading? Scott Robert Ladd
2002-12-15 13:44 ` Dave Jones
2002-12-15 15:07 ` Scott Robert Ladd
2002-12-15 15:47 ` Vergoz Michael (SYSDOOR)
2002-12-15 15:58 ` Dave Jones
2002-12-17 19:39 ` Bill Davidsen
2002-12-15 15:57 ` Dave Jones
2002-12-15 17:40 ` Scott Robert Ladd
2002-12-15 19:17 ` Dave Jones [this message]
2002-12-15 11:55 ` Linux-2.4.20: bug with radeonfb - solved José Luis Tallón
2002-12-15 16:19 ` Adrian Bunk
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=20021215191748.GA24207@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@coyotegulch.com \
/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.