On Wed, Dec 2, 2015 at 10:41 AM, Jan Beulich wrote:
> >>> On 02.12.15 at 16:37, wrote:
> > On Dec 2, 2015, at 10:28 AM, Jan Beulich wrote:
> >
> > On 02.12.15 at 16:04, wrote:
> >>> I have attached the output from 'xl dmesg' with iommu=debug
> >>> apic_verbosity=debug loglvl=all
> >>
> >>
On Dec 2, 2015, at 10:28 AM, Jan Beulich wrote:
On 02.12.15 at 16:04, wrote:
>> I have attached the output from 'xl dmesg' with iommu=debug
>> apic_verbosity=debug loglvl=all
>
> As of 4.6.0 it actually takes a debug hypervisor to get those
> messages logged (which arguably is wrong, and w
>>> On 02.12.15 at 16:37, wrote:
> On Dec 2, 2015, at 10:28 AM, Jan Beulich wrote:
>
> On 02.12.15 at 16:04, wrote:
>>> I have attached the output from 'xl dmesg' with iommu=debug
>>> apic_verbosity=debug loglvl=all
>>
>> As of 4.6.0 it actually takes a debug hypervisor to get those
>> mes
>>> On 02.12.15 at 16:04, wrote:
> I have attached the output from 'xl dmesg' with iommu=debug
> apic_verbosity=debug loglvl=all
As of 4.6.0 it actually takes a debug hypervisor to get those
messages logged (which arguably is wrong, and which quite
certainly is wrong for messages accompanying err
I have attached the output from 'xl dmesg' with iommu=debug
apic_verbosity=debug loglvl=all
This is with 4.6.0, with the recent patch enabling mwait-idle on Skylake
applied. My initial post was running the latest out of xen.git master. I
may be able to try to newer code again later this week.
E
>>> On 02.12.15 at 03:51, 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. Th
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.
On Wed, Dec 02, 2015 at 04:47:17PM +0800, Shuai Ruan wrote:
> On Sat, Nov 28, 2015 at 03:46:05PM -0500, Eric Shelton wrote:
>
> hi eric:
>
> I test this on my skylake machine. Result is follow
> > Not enabling x2APIC (upon firmware request)
> I got the message too.
According to Andrew's comments.
On Sat, Nov 28, 2015 at 03:46:05PM -0500, Eric Shelton wrote:
hi eric:
I test this on my skylake machine. Result is follow
> Not enabling x2APIC (upon firmware request)
I got the message too.
> ...
> mwait-idle: does not run on family 6 model 94
I got the message too.
> ...
> [VT-D] iommu.c:875:
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: In
Eric, could you provide your motherboard information and as Andrew pointed out
what’s f0:1f.0?
From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
Sent: Sunday, November 29, 2015 6:15 AM
To: Eric Shelton; xen-devel; Zhang, Yang Z; Tian, Kevin; Keir Fraser; Jan
Beulich
Subject: Re: Skylake: VT
On 28/11/15 20:46, Eric Shelton wrote:
> Looking through the output of 'xl dmesg' on a Skylake system
> (i5-6600K), I found a number of error messages that I do not encounter
> on a Haswell-based system. I have tried two motherboards from
> different manufacturers, with pretty much the same result
Looking through the output of 'xl dmesg' on a Skylake system (i5-6600K), I
found a number of error messages that I do not encounter on a Haswell-based
system. I have tried two motherboards from different manufacturers, with
pretty much the same results. Below are some of the unexpected messages:
13 matches
Mail list logo
