Re: Dual Xeon w/ HT: Kernel can't find second CPU

Patrick R. McManus (mcmanus@ducksong.com)
Mon, 16 Dec 2002 09:42:43 -0500


> > Sent: Friday, December 06, 2002 6:57 PM
> > To: linux-kernel@vger.kernel.org
> > Subject: Re: Dual Xeon w/ HT: Kernel can't find second CPU

I have a similar (but different) problem that I was hoping for help
with.

I can't build a kernel for my dual xeon e7500 board, with
hyperthreading enabled, that sees 4 logical processors. I can boot the
redhat 8 kernel and that sees 4, but my build of 2.4.20-ac2 gets me
'warning sibling not found' messages and just 2 cpus.

It is built for P4 and has SMP on. Is there anything else I should
have to do? acpismp=force doesn't help (not that it should on 2.4.20
from what I read.)

[..]
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
CPU: Common caps: 3febfbff 00000000 00000000 00000000
CPU0: Intel(R) XEON(TM) CPU 2.40GHz stepping 04
per-CPU timeslice cutoff: 1462.99 usecs.
task migration cache decay timeout: 10 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/2 eip 2000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 4797.23 BogoMIPS
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 3
Intel machine check reporting enabled on CPU#1.
CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
CPU: Common caps: 3febfbff 00000000 00000000 00000000
CPU1: Intel(R) XEON(TM) CPU 2.40GHz stepping 04
Total of 2 processors activated (9581.36 BogoMIPS).
WARNING: No sibling found for CPU 0.
WARNING: No sibling found for CPU 1.
[...]

-Patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/