On 02/19/2014 12:16 AM, SomeSuSEUser wrote:
> lwfinger;2625733 Wrote:
>> Two quick ways to check the number of CPUs is to ‘cat /proc/interrupts’,
>> ‘dmesg | grep smpboot’. If you truly have only one running, you need to
>> the output of dmesg to see why.
> JeepNut@linux-twnw:~> cat /proc/interrupts
> 0: 120 XT-PIC-XT-PIC timer
> 1: 2 XT-PIC-XT-PIC i8042
> 2: 0 XT-PIC-XT-PIC cascade
> 5: 17146 XT-PIC-XT-PIC ohci_hcd:usb2, sata_sil24, snd_hda_intel, snd_cmipci
> 6: 3 XT-PIC-XT-PIC floppy
> 7: 5090 XT-PIC-XT-PIC ehci_hcd:usb1
> 8: 0 XT-PIC-XT-PIC rtc0
> 9: 0 XT-PIC-XT-PIC acpi
> 10: 54644 XT-PIC-XT-PIC nouveau, firewire_ohci
> 11: 58496 XT-PIC-XT-PIC sata_nv, sata_nv
> 12: 4 XT-PIC-XT-PIC i8042
> 14: 0 XT-PIC-XT-PIC pata_amd
> 15: 0 XT-PIC-XT-PIC pata_amd
> 21: 11435 PCI-MSI-edge enp2s0
> NMI: 158 Non-maskable interrupts
> LOC: 3877186 Local timer interrupts
> SPU: 0 Spurious interrupts
> PMI: 158 Performance monitoring interrupts
> IWI: 597918 IRQ work interrupts
> RTR: 0 APIC ICR read retries
> RES: 0 Rescheduling interrupts
> CAL: 0 Function call interrupts
> TLB: 0 TLB shootdowns
> TRM: 0 Thermal event interrupts
> THR: 0 Threshold APIC interrupts
> MCE: 0 Machine check exceptions
> MCP: 102 Machine check polls
> ERR: 1
> MIS: 0
> JeepNut@linux-twnw:~> dmesg | grep smpboot
> 0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
> 0.017102] smpboot: weird, boot CPU (#0) not listed by the BIOS
> 0.017104] smpboot: SMP motherboard not detected
> 0.018000] smpboot: SMP disabled
> 0.025006] smpboot: Total of 1 processors activated (4822.15 BogoMIPS)
> So I’ve only got one CPU responding… => why?
> Could this be a “bad load” of some sort during installation?
> Would there be any reason to suspect a fresh download and
> reinstalling the OS might resolve?
I do not think a bad install is responsible. Hold off on re-installation for the
> How do you prove that 1 core is “dead” in a CPU?
> …or do CPUs even fail like that?
Yes, one core could fail in any number of ways. Whether it would do that without
the BIOS complaining is a question that only the BIOS authors could answer.
> Interesting messages from the code above…
> “boot CPU (#0) not listed by the BIOS”… is that a clue?
> SMP disabled… is that a bad thing?
SMP disabled is a symptom, not the cause. The real reason is that the BIOS only
listed #1 and not #0. When the kernel only found one CPU, there was no reason to
> … what kind of tale do those outputs tell?
What you can do, however, is boot the installation media. In fact, the 12.2
media would be best. If it is the Live ISO, then open a terminal and run the
above tests. For the NET and DVD ISOs, boot into rescue mode and do the same.
Does this show SMP? If 12.2 is still OK, then try the 13.1 media. It is always
possible that a kernel bug has been introduced that keeps only your
configuration from working with multiple CPUs. Unlikely, but possible.
If none of these steps show both CPUs, then enter the BIOS and reset to factory
defaults. You will need to reset the time, any boot medium settings, and
anything else that you know has been changed. Did that help?
The final thing would be to try to reload or update the BIOS. Of course, that is
always a risky step that may brick the motherboard if it fails.