Here's a (retyped) snippet of the kernel boot log when it fails to
activate all four cores.  This is incomplete, and it's just what remains
on the screen when it hangs on boot:

[        0.010000] CPU 1/0x1 -> Node 0
[        0.010000] CPU:  Physical Processor ID: 0
[        0.010000] CPU: Processor Core ID:  1
[        0.010000] mce:  CPU supports 6 MCE banks
[        0.010000] x86 PAT enabled:  cpu 1, old 0x7040600070406, new 
0x7010600070106
[        0.180554] CPU1:  AMD Phenom(tm) 9950 Quad-Core Processor stepping 03
[        0.182409] checking TSC synchronization [CPU#0 -> CPU#1]:  passed.
[        0.190055] Booting processor 2 APIC 0x2 ip 0x6000
[        0.010000] Initializing CPU#2
[        0.010000] Calibrating delay using timer specific routine.. 5174.78 
BogoMIPS (lpj=25873929)
[        0.010000] CPU:  L1 I Cache:  64K (64 bytes/line), D cache 64K (64 
bytes/line)
[        0.010000] CPU:  L2 Cache:  512K (64 bytes/line)
[        0.010000] CPU:  2/0x2 -> Node 0
[        0.010000] CPU:  Physical Processor ID:  0
[        0.010000] CPU:  Processor Core ID: 3
[        0.010000] mce:  CPU supports 6 MCE banks
[        0.010000] x86 PAT enabled:  cpu 2, old 0x7040600060406, new 
0x7010600070106
[        0.350647] CPU2:  AMD Phenom(tm) 9950 Quad-Core Processor stepping 03
[        0.351196] checking TSC synchronization [CPU#0 -> CPU#2]: passed.
[        0.360051] Booting processor 3 APIC 0x3 ip 0x6000
[        5.804396] Not responding
[        5.804518] Brought up 3 CPUs
[        5.804576] Total of 3 processors activated (15550.23 BogoMIPS)

At this point, the system just hangs.  It never continues beyond this.
Sometimes, I get the dreaded "Not responding" message on the second
core, most of the time when that happens it continues to boot in single
core mode.  If it stops on the third or fourth cores, it never boots.
If I don't get the "Not responding" message, it boots rather quickly,
and all four cores are brought up.

-- 
SMP kernel fails to boot most of the time
https://bugs.launchpad.net/bugs/515270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to