From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 and hyperthreading
Date: Sat, 03 Jan 2004 13:45:52 -0500 [thread overview]
Message-ID: <bt71ub$cfr$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20031229214508.GG916@mail.muni.cz>
Lukas Hejtmanek wrote:
> 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)
You *may* be able to change from MPS 1.4 to 1.1 in the BIOS. Hard to
believe that a m/b which knows about HT doesn't know about SMP, but it
certainly could be buggy.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2004-01-03 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 21:45 2.6.0 and hyperthreading Lukas Hejtmanek
2004-01-03 18:45 ` Bill Davidsen [this message]
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='bt71ub$cfr$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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