linux-kernel - Re: how to Identify and determine NMI sourcing in GHES.c ? for example , knowing a NMI error is caused by pcie error

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

Message-ID: <CANuKePmkw3=aXoB-y4m_ULnePR-PsYH2yUApd3K7fs4Qxt4FBw@mail.gmail.com>
Date:	Tue, 17 Jan 2012 11:58:25 +0800
From:	Lin-Bao Zhang <2004.zhang@...il.com>
To:	ying.huang@...el.com, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: how to Identify and determine NMI sourcing in GHES.c ? for
 example , knowing a NMI error is caused by pcie error

> In firmware first mode (BIOS hold AER service control), AER will be reported via
> APEI HEST Generic Hardware Error Source, AER will be logged by kernel there.
> AER recovery can be triggered there too, but the code has not been merged by
> Linux kernel upstream yet.

Wow! ,from LKML , I have found your patches here :
http://www.spinics.net/lists/linux-acpi/msg34003.html
I check the latest code from
http://lxr.linux.no/linux+v3.2.1/drivers/acpi/apei/ghes.c ,this patch
has been not adopted by upstream.

another question :
for corrected error , hardware can correct it.
but for uncorrected error, especially fatal error , machines need to
be restarted immediately, but for OS ,for different error (NMI
sourcing) ,OS needs to do different ready works before restarting
machine ?

thanks .

-Bob Zhang
--
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/