public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: linux-kernel@vger.kernel.org
Subject: Problems with hyper-threading on Asus P4T533 / Linux 2.4.20
Date: Wed, 12 Feb 2003 15:03:59 +0100	[thread overview]
Message-ID: <m365rpegts.fsf@quimbies.gnus.org> (raw)

We've just gotten an Asus P4T533-based machine with a 3.06GHz P4 CPU,
bios version 1005.  (P4T533 is i850e-based.)  The bios claims that the
P4 has hyper-threading, and as you can see from the cpuinfo output
below, "ht" is among the flags.  (And the manual says that P4T533 is
ht-enabled.)

I've tried booting with acpismp=force and without, and it doesn't
seem to make much difference: Linux still only sees a single CPU.
I've also tried 2.4.21-pre4 and -ac4, which doesn't seem to make any
difference, either.

Anybody got any ideas why I can't get this to work?

buto:~# uname -a
Linux buto 2.4.20 #3 SMP Wed Feb 12 14:28:49 CET 2003 i686 unknown
buto:~# cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 3.06GHz
stepping        : 7
cpu MHz         : 3073.691
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 6134.16


-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


             reply	other threads:[~2003-02-12 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 14:03 Lars Magne Ingebrigtsen [this message]
2003-02-12 15:56 ` Problems with hyper-threading on Asus P4T533 / Linux 2.4.20 Balram Adlakha
     [not found] <mng==m365rpegts.fsf@quimbies.gnus.org>
2003-02-12 15:30 ` Thorsten Leemhuis
2003-02-12 16:09   ` Lars Magne Ingebrigtsen

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=m365rpegts.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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