From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Skylake: VT-d and other error messages Date: Wed, 2 Dec 2015 09:54:41 +0000 Message-ID: <565EBFE1.20306@citrix.com> References: <565A275C.108@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3798754777577443546==" Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1a447b-00010L-6O for xen-devel@lists.xenproject.org; Wed, 02 Dec 2015 09:54:47 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Eric Shelton , "Tian, Kevin" Cc: "Zhang, Yang Z" , xen-devel , Keir Fraser , Jan Beulich List-Id: xen-devel@lists.xenproject.org --===============3798754777577443546== Content-Type: multipart/alternative; boundary="------------090103070708090407030504" --------------090103070708090407030504 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 02/12/15 02:51, Eric Shelton wrote: > ASRock Z170 Extreme 4 with BIOS version 2.30 was motherboard #1 > Gigabyte GA-Z170XP-SLI with BIOS version F5 was motherboard #2 > > As I initially reported, both were reporting the error involving f0:1f.0 > > Not surprisingly, there are no f0:xx.y devices. The closest I suppose is: > 00:1f.0 ISA Bridge: Intel Corporation Sunrise Point-H LPC Controller > (rev 31) > > At the moment, I am back on vanilla 4.6.0, and no such error messages > are being reported via 'xl dmesg'. I am guessing reporting of this > error was added post-4.6. > > Eric Nothing obvious comes to mind which would have this effect. Can you provide `lspci -tv` from one of the affected systems? If the platform is generating interrupts from a non-existent device, something is quite broken. ~Andrew --------------090103070708090407030504 Content-Type: text/html; charset="utf-8" Content-Length: 1737 Content-Transfer-Encoding: quoted-printable
On 02/12/15 02:51, Eric Shelton wrote:
ASRock Z170 Extreme 4 with BIOS version 2.30 was motherboard #1
Gigabyte=C2=A0GA-Z170XP-SLI with BIOS version F5 was motherboard #2

As I initially reported, both were reporting the error involving f0:1f.0

Not surprisingly, there are no f0:xx.y devices.=C2=A0 The closest I suppose is:
00:1f.0 ISA Bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)

At the moment, I am back on vanilla 4.6.0, and no such error messages are being reported via 'xl dmesg'.=C2=A0 I am guessing reporting of this error was added post-4.6.

Eric

Nothing obvious comes to mind which would have this effect.

Can you provide `lspci -tv` from one of the affected systems=3F

If the platform is generating interrupts from a non-existent device, something is quite broken.

~Andrew
--------------090103070708090407030504-- --===============3798754777577443546== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3798754777577443546==--