![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
On Mon, Apr 7, 2008 at 10:22 PM, David C. Rankin
List, Jan:
Still wrestling with my MCE fun, I am passing the kernel parameters "noapic" and "nolapic". Scrolling through dmesg, I have run across something that looks real strange. It may not be. I may just not yet know what I'm reading, but I would like for someone to confirm that the kernel is respecting the nolapic setting. kernel is: 2.6.23.17-ccj64-default. Specifically, my command line is:
Command line: root=/dev/mapper/nvidia_hacfgfda_part7 vga=0x31a resume=/dev/mapper/nvidia_hacfgfda_part6 splash=0 apic=verbose noapic nolapic
[ 0.000000] Initializing CPU#0 <snip>
[ 37.799957] Using local APIC timer interrupts. [ 37.845175] result 12558028 [ 37.845176] Detected 12.558 MHz APIC timer. [ 37.846233] SMP alternatives: switching to SMP code [ 37.846663] Booting processor 1/2 APIC 0x1 [ 37.856841] Initializing CPU#1
I can't say for sure, and probably only the kernel hackers can. But I wonder if your machine can't run in smp mode without apic? I have nohpet on my command line (since opensuse 10.1) and yet I see the current kernel puts this line in the boot.msg: <7>Force enabled HPET at base address 0xfed00000 Command line parms are fleeting at best and rather poorly documented in my opinion.
Next, why is my kernel using Intel MultiProcessor Specification v1.4 with an AMD Opteron 180 processor?
Because Intel developed this particular MultiProcessor spec, AMD stole it and developed Dual Core CPUs, and Intel stole it back. All under cross licensing agreements - supposedly. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org