From: Manish <manishmj1111@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Re: WHEA Support in Linux
Date: Wed, 27 Feb 2013 19:00:53 +0000 (UTC) [thread overview]
Message-ID: <loom.20130227T195852-926@post.gmane.org> (raw)
In-Reply-To: 20130227023235.GB29624@gchen.bj.intel.com
Thanks a lot for your quick response.
How can we verify that a particular version of Linux supports WHEA or not?
In Windows, OSC method returns supported for the Whea Guid. Is it applicable
also for Linux?
Also, In Windows, Error Injection is verifed using WHEA HCT tool and the Errors
are logged in Windows Event Viewer.
Is there any such facility/tool available to verify Error Injection (EINJ) stack
in Linux?
Also, Is there any thing similar to Event Viewer of Windows in Linux where the
WHEA errors are logged?
(I'm getting the following message in dmesg log from RHEL:
"ERST: Could not register with persistent Store"
You don't compile pstore support/not loaded it as a module/no NVRAM, UEFI
runtime space etc. to support pstore.)
As far as the above ERST dmesg is concerned, We are allocating a Flash Block for
ERST persistent store.
The persistent store will be used for Writing/Reading an Error Record by the OS
in case of NMI when fatal error is generated.
In case of fatal error from Windows, it is getting written as well as Read
correctly from the persistent store and error is avialable in Event Viewer.
Can you please help us to narrow down this issue or in what could be reason for
this error in dmesg log.
Regards,
Manish.
next prev parent reply other threads:[~2013-02-27 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 4:40 WHEA Support in Linux Manish
2013-02-27 2:32 ` Chen Gong
2013-02-27 19:00 ` Manish [this message]
2013-03-01 2:16 ` Chen Gong
-- strict thread matches above, loose matches on Subject: below --
2013-02-27 18:57 Manish
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=loom.20130227T195852-926@post.gmane.org \
--to=manishmj1111@gmail.com \
--cc=linux-acpi@vger.kernel.org \
/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