linux-kernel - Re: 7ad6e9435596f692ff65f399da12816c94960185 breaks AMD f10h.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100917145056.GB4335@kryptos.osrc.amd.com>
Date:	Fri, 17 Sep 2010 16:50:56 +0200
From:	Borislav Petkov <borislav.petkov@....com>
To:	Andi Kleen <ak@...ux.intel.com>
CC:	Conny Seidel <conny.seidel@....com>,
	Huang Ying <ying.huang@...el.com>,
	Len Brown <len.brown@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 7ad6e9435596f692ff65f399da12816c94960185 breaks AMD f10h.

From: Andi Kleen <ak@...ux.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/