From: Borislav Petkov <borislav.petkov@amd.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Conny Seidel <conny.seidel@amd.com>,
Huang Ying <ying.huang@intel.com>,
Len Brown <len.brown@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 7ad6e9435596f692ff65f399da12816c94960185 breaks AMD f10h.
Date: Fri, 17 Sep 2010 16:50:56 +0200 [thread overview]
Message-ID: <20100917145056.GB4335@kryptos.osrc.amd.com> (raw)
In-Reply-To: <4C936FFF.5030303@linux.intel.com>
From: Andi Kleen <ak@linux.intel.com>
Date: Fri, Sep 17, 2010 at 03:41:19PM +0200
> On 9/17/2010 2:56 PM, Conny Seidel wrote:
> >Hi,
> >
> >Kernel v2.6.36-rc4-134-g03a7ab0 breaks with the OOPS below.
> >
> >Reverting the commitid in the subject fixes the issue.
> >This is because APEI is selected by default on X86 (X86&& ACPI),
> >maybe a vendor check in the hest_init() might make sense.
>
> It looks like your system has a duplicated hest source ID. They are supposed
> to have unique identifiers.
>
> The kernel should not oops of course, but it's really a BIOS bug imho.
We're looking into the BIOS issue. But right you are, the kernel should
not oops on a BIOS bug - it's not like BIOS bugs are something which
never happens :)
--
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-09-17 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 12:56 7ad6e9435596f692ff65f399da12816c94960185 breaks AMD f10h Conny Seidel
2010-09-17 13:41 ` Andi Kleen
2010-09-17 14:50 ` Borislav Petkov [this message]
2010-09-19 0:14 ` Huang Ying
2010-09-19 13:09 ` Conny Seidel
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=20100917145056.GB4335@kryptos.osrc.amd.com \
--to=borislav.petkov@amd.com \
--cc=ak@linux.intel.com \
--cc=conny.seidel@amd.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.com \
/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