[Xen-devel] 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

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 30.09.13 at 16:13, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
> 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.

Possibly MMCONF just didn't get used on 4.0?

And no, I don't think I recall any possibly relevant change. Even more,
the description above sounds more like an error resulting from device
misbehavior than from software incorrectly doing some access.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel