linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lin-Bao Zhang <2004.zhang@gmail.com>
To: ying.huang@intel.com, linux-kernel@vger.kernel.org,
	linux-acpi@vger.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
Date: Tue, 17 Jan 2012 11:58:25 +0800	[thread overview]
Message-ID: <CANuKePmkw3=aXoB-y4m_ULnePR-PsYH2yUApd3K7fs4Qxt4FBw@mail.gmail.com> (raw)
In-Reply-To: <CANuKePk9LWEuFe3zrh0RiKtau85DAEBHbd+Qow10Py80xzYYtg@mail.gmail.com>

> 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

      reply	other threads:[~2012-01-17  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17  3:17 how to Identify and determine NMI sourcing in GHES.c ? for example , knowing a NMI error is caused by pcie error Lin-Bao Zhang
2012-01-17  3:58 ` Lin-Bao Zhang [this message]

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='CANuKePmkw3=aXoB-y4m_ULnePR-PsYH2yUApd3K7fs4Qxt4FBw@mail.gmail.com' \
    --to=2004.zhang@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).