From: Don Zickus <dzickus@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
ying.huang@intel.com, kernel-team@fedoraproject.org,
Matt_Domsch@dell.com, linux-acpi@vger.kernel.org
Subject: Re: GHES: Failed to read error status
Date: Thu, 17 Nov 2011 11:31:12 -0500 [thread overview]
Message-ID: <20111117163112.GO8685@redhat.com> (raw)
In-Reply-To: <CAErSpo4X1-0D1iOm=SuoxaqwWh2sVYFR_1qsZMRB00tBFnSu+Q@mail.gmail.com>
On Tue, Nov 15, 2011 at 08:29:56AM -0700, Bjorn Helgaas wrote:
> [+linux-acpi]
>
> On Mon, Nov 14, 2011 at 11:36 AM, Dave Jones <davej@redhat.com> wrote:
> > It appears that there's a problem with Dell poweredge servers
> > and GHES judging by the bug reports at
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=746755
> > https://bugs.launchpad.net/ubuntu/+bug/881164
> >
> > Is this likely to be something that Dell need to fix in a firmware update,
> > or something that the code needs to accomodate ?
I think one problem was that in 2.6.38 the kernel saw HEST/GHES was
supported and just tried to communicate with it. Unfortunately the kernel
forgot to tell the BIOS that it supports firmware first mode, so in this
case the firmware is probably blocking the GHES access and the kernel is
confused why.
The following commits resolved that issue (which may not entirely fix the
problem, but might move it along).
9fb0bfe ACPI, APEI, Add WHEA _OSC support
b3b46d7 APEI: Fix WHEA _OSC call
The second one in particular was noticed by Dell. Though I recall that we
needed to update the firmware to get Dell boxes working, but that was
probably for EINJ.
Cheers,
Don
prev parent reply other threads:[~2011-11-17 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 18:36 GHES: Failed to read error status Dave Jones
2011-11-15 15:29 ` Bjorn Helgaas
2011-11-17 16:31 ` Don Zickus [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=20111117163112.GO8685@redhat.com \
--to=dzickus@redhat.com \
--cc=Matt_Domsch@dell.com \
--cc=bhelgaas@google.com \
--cc=davej@redhat.com \
--cc=kernel-team@fedoraproject.org \
--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