From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Trenta sis <trenta.sis@gmail.com>
Cc: arrfab@centos.org, agya.naila@gmail.com, JBeulich@suse.com,
xen-devel@lists.xen.org
Subject: Is: 0xCF8 on extended config space instead of MCONF? Was:Re: IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash
Date: Mon, 30 Sep 2013 10:13:45 -0400 [thread overview]
Message-ID: <20130930141345.GG3106@phenom.dumpdata.com> (raw)
In-Reply-To: <CANTbh__mET2ZCrkKXt6suti-xES5QXDM3qGSvcz8+L_RyaBY+g@mail.gmail.com>
> Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value= 0020
> 27 I Blade_09 09/08/13 13:25:17 0x806f0013 Chassis, (NMI State) diagnostic
> interrupt
> 28 E Blade_09 09/08/13 13:25:12 0x10000002 SMI Hdlr: 00151743 HI Fatal
> Error, HI_FERR/NERR Value= 0020
Doing a simple Google search on HI_FERR tells me that it is:
http://www.intel.com/content/dam/doc/datasheet/e7525-memory-controller-hub-datasheet.pdf
and that
3.6.14 HI_FERR – Hub Interface First Error Register (D0:F1)
has something in it. The value is 0020 (is that decimal or hex?). If it is
decimal it is then 10100, which is bit 2 and 4:
bit 2:
HI Internal Parity Error Detected. This bit is sticky through reset. System
software clears this bit by writing a ‘1’ to the location.
0 = No Internal Parity error detected.
1 = MCH HI bridge has detected an Internal Parity error. Non-fatal.
and bit 4:
HI Data Parity Error Detected. This bit is sticky through reset. System software
clears this bit by writing a ‘1’ to the location.
0 = No HI data parity error.
1 = MCH has detected a parity error on the data phase of a HI transaction.
But that is unlikely as these are 'non-fatal'. So if this is hex, then it would
be bit 5, which is:
Enhanced Configuration Access Error. This bit is sticky through reset. System
software clears this bit by writing a ‘1’ to the location.
0 = No Enhanced Configuration Access error
1 = A PCI Express* Enhanced Configuration access was mistakenly targeting
the legacy interface. Fatal
That sounds more like it. So we touched a PCIe Enhanced Configuration (MMCONFIG?)
using the legacy interface (cf8?).
Jan, any thoughts? Is there a particular bug-fix we are missing in Xen 4.1 or Xen 4.2
for this? Xen 4.0 seems to work.
Trenta,
When you used Xen 4.0 did you use the same kernel as with Xen 4.1 or Xen 4.2?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-09-30 14:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 14:35 IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash Trenta sis
2013-09-08 14:41 ` Trenta sis
2013-09-09 19:15 ` Konrad Rzeszutek Wilk
2013-09-12 12:47 ` Trenta sis
2013-09-23 14:02 ` Konrad Rzeszutek Wilk
2013-09-29 10:47 ` Trenta sis
2013-09-30 14:13 ` Konrad Rzeszutek Wilk [this message]
2013-09-30 15:40 ` Is: 0xCF8 on extended config space instead of MCONF? Was:Re: " Jan Beulich
2013-10-04 16:31 ` Trenta sis
2013-10-04 16:55 ` Konrad Rzeszutek Wilk
2014-09-05 11:58 ` Trenta sis
2014-09-05 14:30 ` Is: 0xCF8 on extended config space instead of MCONF? Jan Beulich
2014-09-08 12:53 ` Trenta sis
2014-09-08 13:28 ` Jan Beulich
2014-09-09 7:11 ` Trenta sis
2014-09-09 8:53 ` Ian Campbell
2014-09-09 14:00 ` Trenta sis
2014-09-09 14:39 ` Konrad Rzeszutek Wilk
2014-09-09 14:39 ` Ian Campbell
2014-09-09 14:46 ` Trenta sis
2014-09-09 9:15 ` Jan Beulich
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=20130930141345.GG3106@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=agya.naila@gmail.com \
--cc=arrfab@centos.org \
--cc=trenta.sis@gmail.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.