From: cinap_lenrek@gmx.de
To: 9fans@cse.psu.edu
Subject: [9fans] Plan9 on Intel Pentiul D Dualcore (D94RPLrn)
Date: Mon, 25 Feb 2008 23:07:06 +0100 [thread overview]
Message-ID: <ab273224f99d7d712826aae25db004df@gmx.de> (raw)
dumping the mptable shows that here is just one PCMPprocessor enty
and nothing else so this is the reason here is no busses found and
mpintrenablex fails.
Plan 9
E820: 00000000 0009fc00 memory
E820: 0009fc00 000a0000 reserved
E820: 000e0000 00100000 reserved
E820: 00100000 3fe60000 memory
E820: 3fe60000 3fee9000 acpi nvs
E820: 3fee9000 3feed000 memory
E820: 3feed000 3feff000 acpi reclaim
E820: 3feff000 3ff00000 memory
mp found 0xfe680
found mp table 0xfe680
pcmp->length=40
pcmp->version=4
pcmp->checksum=81
pcmp->oemtable=0
pcmp->oemlength=0
pcmp->entry=1
pcmp->lapicbase=fee00000
pcmp->xlength=0
pcmp->xchecksum=0
126 holes free
00018000 0009f000 552960
003ef000 10000000 264310784
264863744 bytes free
cpu0: 2999MHz GenuineIntel P4 (cpuid: AX 0x0F62 DX 0xBFEBFBFF)
ELCR: 0E00
LAPIC: fee00000 e0000000
mptable: f00fe6bc-f00fe6d0
0 0 14 3 62 F 0 0 FF FB EB BF 0 0 0 0 0 0 0 0
f00fe6bc processor...
processor p->apicno=0
processor p->version=14
processor p->flags=3
processor p->feature=bfebfbff 0x1
mpintrenable: out of choices -1 -1
intrenable: couldn't enable irq 1, tbdf 0xFFFFFFFF for kbd
ioapicirq: can't find bus type 12
mpintrenable: out of choices -1 -1
intrenable: couldn't enable irq 11, tbdf 0xC040000 for ether0
i guess the processor has some hyperthreading feature-flag set,
but if here are no bus entries in the mptable, how is it supposed
to work?
cinap
next reply other threads:[~2008-02-25 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 22:07 cinap_lenrek [this message]
2008-02-26 3:34 ` erik quanstrom
2008-02-26 5:16 ` Uriel
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=ab273224f99d7d712826aae25db004df@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).