lkml.org 
[lkml]   [2010]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: CPU #1 not responding Problem
From: Jacek J <69rydzyk69@gmail.com>
Date: Tue, May 25, 2010 at 07:55:52PM +0200

> thanks for your response. Dmesg is in attachment. Error is almost
> unreproducable, seems random. I use 2.6.33 kernel from Arch
> distribution.

So what looks suspicious to me is this

May 23 22:44:54 connexion1 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
May 23 22:44:54 connexion1 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
May 23 22:44:54 connexion1 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
May 23 22:44:54 connexion1 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
May 23 22:44:54 connexion1 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
May 23 22:44:54 connexion1 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
May 23 22:44:54 connexion1 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
May 23 22:44:54 connexion1 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
May 23 22:44:54 connexion1 kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
May 23 22:44:54 connexion1 kernel: IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23

and more specifically, the ioapic's id is 2 and it overlaps with the
lapic id 2 of core 2. This could explain why in the broken case you
get only 1 core up. The solution to that is to update your BIOS and
hope that Gigabyte (your board maker) have fixed it already. We've
seen similar initialization problems with b0rked Gigabyte boards, see
https://bugzilla.kernel.org/show_bug.cgi?id=15289 and there the apic
id's were also overlapping.

HTH.

--
Regards/Gruss,
Boris.


\
 
 \ /
  Last update: 2010-05-26 15:59    [W:0.176 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site