From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Eric Shelton <eshelton@pobox.com>, "Tian, Kevin" <kevin.tian@intel.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: Skylake: VT-d and other error messages
Date: Wed, 2 Dec 2015 09:54:41 +0000 [thread overview]
Message-ID: <565EBFE1.20306@citrix.com> (raw)
In-Reply-To: <CAPQw5rm5vPR3S5iJf1PPouB-6aM4-pG6WpDC41bAFCu9PtSQKA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 819 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 1697 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-02 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 20:46 Skylake: VT-d and other error messages Eric Shelton
2015-11-28 22:14 ` Andrew Cooper
2015-12-02 2:34 ` Tian, Kevin
2015-12-02 2:51 ` Eric Shelton
2015-12-02 9:54 ` Andrew Cooper [this message]
2015-12-02 10:45 ` Jan Beulich
2015-12-02 15:04 ` Eric Shelton
2015-12-02 15:28 ` Jan Beulich
2015-12-02 15:37 ` Eric Shelton
2015-12-02 15:41 ` Jan Beulich
2015-12-04 21:23 ` Eric Shelton
2015-12-02 8:47 ` Shuai Ruan
[not found] ` <20151202084717.GA18791@shuai.ruan@linux.intel.com>
2015-12-02 9:07 ` Shuai Ruan
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=565EBFE1.20306@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=eshelton@pobox.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@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 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.