linux-kernel - Re: [PATCH v4] acpi, apei: add Boot Error Record Table (BERT) support

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>] [day] [month] [year] [list]

Message-ID: <CADyBb7sZU=rbimwo-PHSWj3uyiiGd5n1HOEQgdy7V3XFkcNssg@mail.gmail.com>
Date:	Tue, 19 Jan 2016 15:12:27 +0800
From:	Fu Wei <fu.wei@...aro.org>
To:	"Abdulhamid, Harb" <harba@...eaurora.org>
Cc:	Borislav Petkov <bp@...en8.de>, Tony Luck <tony.luck@...el.com>,
	"Chen, Gong" <gong.chen@...el.com>,
	Huang Ying <ying.huang@...el.com>,
	Tomasz Nowicki <tomasz.nowicki@...aro.org>,
	Tomasz Nowicki <tn@...ihalf.com>, tbaicar@...eaurora.org,
	rruigrok@...eaurora.org,
	"Abdulhamid, Harb" <harba@....qualcomm.com>,
	G Gregory <graeme.gregory@...aro.org>,
	Al Stone <al.stone@...aro.org>,
	Hanjun Guo <hanjun.guo@...aro.org>,
	LKML <linux-kernel@...r.kernel.org>, linux-acpi@...r.kernel.org,
	Linaro ACPI Mailman List <linaro-acpi@...ts.linaro.org>,
	Jon Masters <jcm@...hat.com>,
	Mark Rutland <mark.rutland@....com>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	Rafael Wysocki <rjw@...ysocki.net>,
	"Chen, Gong" <gong.chen@...ux.intel.com>
Subject: Re: [PATCH v4] acpi, apei: add Boot Error Record Table (BERT) support

Hi Borislav, Harb,

On 19 January 2016 at 01:38, Abdulhamid, Harb <harba@...eaurora.org> wrote:
>
>
> On 1/18/2016 11:08 AM, Borislav Petkov wrote:
>> On Mon, Jan 18, 2016 at 10:08:00AM -0500, Abdulhamid, Harb wrote: >> Here
>> is my crack at massaging the language a bit more: "Under >> normal
>> circumstances, when a hardware error occurs, the kernel gets >> notified via
>> an NMI, MCE or some other method. When the error has a >> fatal severity or
>> is unrecoverable, the kernel would normally >> panic. > > So this is still
>> not exact. It all depends on what the hardware > does. Even more
>> importantly, does the hardware even run the error > handler and let it
>> access MCA banks to find about the error or does > it directly warm-reset
>> the system. > > The error can happen, it is critical, *nothing* might be
>> visible in > the MCA registers (this is x86-specific) and the machine would
>> reset. > Only when you warm-reset, you may or may not see anything in there.
>> > > In reading the BERT explanation in the ACPI spec, I have to say, it >
>> sounds pretty ok to me: > > "18.3.1 Boot Error Source > > Under normal
>> circumstances, when a hardware error occurs, the error > handler receives
>> control and processes the error. This gives OSPM a > chance to process the
>> error condition, report it, and optionally > attempt recovery. In some
>> cases, the system is unable to process an > error. For example, system
>> firmware or a management controller may > choose to reset the system or the
>> system might experience an > uncontrolled crash or reset.The boot error
>> source is used to report > unhandled errors that occurred in a previous
>> boot. This mechanism is > described in the BERT table." > > I think we
>> should take that text. :)
> Agreed. That would be best.

Thanks, guys.
Will use this instead.


>
> Apologies for the format of the last email.
>
> --
> Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
> Foundation Collaborative Project



-- 
Best regards,

Fu Wei
Software Engineer
Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch
Ph: +86 21 61221326(direct)
Ph: +86 186 2020 4684 (mobile)
Room 1512, Regus One Corporate Avenue,Level 15,
One Corporate Avenue,222 Hubin Road,Huangpu District,
Shanghai,China 200021