From: Borislav Petkov <borislav.petkov@amd.com>
To: Heinz Diehl <htd@fancy-poultry.org>
Cc: Michal Schmidt <mschmidt@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
Shaohua Li <shaohua.li@intel.com>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/2] x86: fix keeping track of AMD C1E
Date: Sun, 18 Jul 2010 20:17:36 +0200 [thread overview]
Message-ID: <20100718181736.GA10886@aftab> (raw)
In-Reply-To: <20100718162239.GA21151@fancy-poultry.org>
From: Heinz Diehl <htd@fancy-poultry.org>
Date: Sun, Jul 18, 2010 at 12:22:39PM -0400
> On 15.07.2010, Michal Schmidt wrote:
>
> > This suggests that another way to fix my problem would be this (tested):
> [....]
>
> Did apply this patch to stock 2.6.35-rc5, it does _not_ fix my C1E problem.
> It takes a lot of key pressing in the boot process to get the system up,
> just as it has been before.
Well, no wonder it wouldn't work - you seem to have that funny Gigabyte
BIOS which botches lapic and ioapic id enumeration and obviously
enabling C1E in the SMI handler (excerpt from your dmesg):
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
See how the IOAPIC's and the third LAPIC's ids are the same?
That's wrong. There are couple people with the same problem:
https://bugzilla.kernel.org/show_bug.cgi?id=15289. And as comment #53
says, we're trying to talk to Gigabyte to fix this and the C1E problem.
For now, you can disable C1E in the BIOS, use "idle=mwait" and put
yourself on the CC list of that bug. Sorry, I wish I could give you
better news.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-07-18 18:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 18:59 [PATCH 0/2] x86: AMD C1E fix and cleanup Michal Schmidt
2010-07-13 18:59 ` [PATCH 1/2] x86: fix keeping track of AMD C1E Michal Schmidt
2010-07-13 20:05 ` H. Peter Anvin
2010-07-13 20:32 ` Borislav Petkov
2010-07-14 16:07 ` Borislav Petkov
2010-07-14 21:22 ` Michal Schmidt
2010-07-14 21:31 ` Michal Schmidt
2010-07-15 16:57 ` Borislav Petkov
2010-07-16 4:25 ` H. Peter Anvin
2010-07-16 6:39 ` Borislav Petkov
2010-07-15 21:56 ` H. Peter Anvin
2010-07-16 7:22 ` Borislav Petkov
2010-07-16 16:02 ` H. Peter Anvin
2010-07-16 16:25 ` Borislav Petkov
2010-07-16 22:28 ` H. Peter Anvin
2010-07-17 10:21 ` Borislav Petkov
2010-07-22 15:02 ` Borislav Petkov
2010-07-18 16:22 ` Heinz Diehl
2010-07-18 18:17 ` Borislav Petkov [this message]
2010-07-19 19:34 ` Borislav Petkov
2010-07-20 15:14 ` Heinz Diehl
2010-09-08 20:29 ` Andreas Herrmann
2010-09-10 6:04 ` Heinz Diehl
2010-07-18 16:39 ` Heinz Diehl
2010-07-13 19:00 ` [PATCH 2/2] x86: remove c1e_mask Michal Schmidt
[not found] <909896077.345011279054483129.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2010-07-13 21:01 ` [PATCH 1/2] x86: fix keeping track of AMD C1E Michal Schmidt
2010-07-14 1:36 ` john stultz
2010-07-18 14:48 ` Heinz Diehl
2010-07-18 16:24 ` Heinz Diehl
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=20100718181736.GA10886@aftab \
--to=borislav.petkov@amd.com \
--cc=Andreas.Herrmann3@amd.com \
--cc=hpa@zytor.com \
--cc=htd@fancy-poultry.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mschmidt@redhat.com \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.