From: Borislav Petkov <bp@alien8.de>
To: Jacek J <69rydzyk69@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPU #1 not responding Problem
Date: Wed, 26 May 2010 15:56:28 +0200 [thread overview]
Message-ID: <20100526135628.GA9127@a1.tnic> (raw)
In-Reply-To: <AANLkTinVaesYF60kbSHnASQUuO2g_LdN58EBpouYUqXT@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-05-26 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 22:14 Jacek J
2010-05-24 6:59 ` Borislav Petkov
2010-05-25 17:55 ` Jacek J
2010-05-26 13:56 ` Borislav Petkov [this message]
2010-05-26 15:18 ` Jacek J
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100526135628.GA9127@a1.tnic \
--to=bp@alien8.de \
--cc=69rydzyk69@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®