public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@hell.sks3.muni.cz>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0 and hyperthreading
Date: Mon, 29 Dec 2003 22:45:09 +0100	[thread overview]
Message-ID: <20031229214508.GG916@mail.muni.cz> (raw)

Hello,

is it possible to use Hyperthreading on the processor that supports
hypperthreading but motherboard has no idea about SMP?

I have in dmesg:
238MB LOWMEM available.
found SMP MP-table at 000f63f0
hm, page 000f6000 reserved twice.
hm, page 000f7000 reserved twice.
hm, page 0009f000 reserved twice.
hm, page 000a0000 reserved twice.
On node 0 totalpages: 61152
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 57056 pages, LIFO batch:13
  HighMem zone: 0 pages, LIFO batch:1
DMI present.
ACPI: RSDP (v000 PTLTD                                     ) @ 0x000f6420
ACPI: RSDT (v001 PTLTD  Montara  0x06040000  LTP 0x00000000) @ 0x0eee5e05
ACPI: FADT (v001 Acer   Yuhina   0x06040000 PTL  0x00000001) @ 0x0eeeaed2
ACPI: BOOT (v001 PTLTD  $SBFTBL$ 0x06040000  LTP 0x00000001) @ 0x0eeeafd8
ACPI: DSDT (v001   ANNI   Yuhina 0x06040000 MSFT 0x0100000e) @ 0x00000000
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
SMP mptable: bad signature [0x0]!
BIOS bug, MP table errors detected!...
... disabling SMP support. (tell your hw vendor)
Building zonelist for node : 0
Kernel command line: ro root=/dev/hda1 noapic vga=0x318 
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 2398.193 MHz processor.
Console: colour VGA+ 80x25
Memory: 237880k/244608k available (2134k kernel code, 6016k reserved, 829k data,
 160k init, 0k highmem)
Calibrating delay loop... 4734.97 BogoMIPS
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: bfebf9ff 00000000 00000000 00000000
CPU:     After vendor identify, caps: bfebf9ff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 128K
CPU: Hyper-Threading is disabled
CPU:     After all inits, caps: bfebf9ff 00000000 00000000 00000080
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU0: Intel(R) Celeron(R) CPU 2.40GHz stepping 09
per-CPU timeslice cutoff: 365.58 usecs.
task migration cache decay timeout: 1 msecs.
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Starting migration thread for cpu 0
CPUS done 8


Could be Hyper-Threading enabled in some way? (I use noapic otherwise kernel
hangs during boot after uncompressing kernel message)

-- 
Lukáš Hejtmánek

             reply	other threads:[~2003-12-29 21:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29 21:45 Lukas Hejtmanek [this message]
2004-01-03 18:45 ` 2.6.0 and hyperthreading Bill Davidsen
2004-01-08 18:39 ` 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=20031229214508.GG916@mail.muni.cz \
    --to=xhejtman@hell.sks3.muni.cz \
    --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