From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lin-Bao Zhang <2004.zhang@gmail.com> Subject: Re: how to Identify and determine NMI sourcing in GHES.c ? for example , knowing a NMI error is caused by pcie error Date: Tue, 17 Jan 2012 11:58:25 +0800 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-gx0-f174.google.com ([209.85.161.174]:62468 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750855Ab2AQD6Z (ORCPT ); Mon, 16 Jan 2012 22:58:25 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: ying.huang@intel.com, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org > 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