* Skylake: VT-d and other error messages
@ 2015-11-28 20:46 Eric Shelton
2015-11-28 22:14 ` Andrew Cooper
` (2 more replies)
0 siblings, 3 replies; 13+ messages in thread
From: Eric Shelton @ 2015-11-28 20:46 UTC (permalink / raw)
To: xen-devel, Yang Zhang, Kevin Tian, Keir Fraser, Jan Beulich,
Andrew Cooper
[-- Attachment #1.1: Type: text/plain, Size: 1030 bytes --]
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:
Not enabling x2APIC (upon firmware request)
...
mwait-idle: does not run on family 6 model 94
...
[VT-D] iommu.c:875: iommu_fault_status: Primary Pending Fault
[VT-D] INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg =
ffff82c000201000
(on motherboard 1) [VT-D] INTR-REMAP: reason 22 - Present field in the IRTE
entry is clear
(on motherboard 2) [VT-D] INTR-REMAP: reason 25 - Blocked a compatibility
format interrupt request
This leads to a few questions:
1) Is there some reason x2APIC should not be enabled on Skylake? What
consequence, if any, is there not having x2APIC enabled?
2) Should mwait-idle be available on Skylake?
3) What about the IOMMU errors on Skylake - are they a concern?
Thank you,
Eric
[-- Attachment #1.2: Type: text/html, Size: 1249 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Skylake: VT-d and other error messages 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 8:47 ` Shuai Ruan [not found] ` <20151202084717.GA18791@shuai.ruan@linux.intel.com> 2 siblings, 1 reply; 13+ messages in thread From: Andrew Cooper @ 2015-11-28 22:14 UTC (permalink / raw) To: Eric Shelton, xen-devel, Yang Zhang, Kevin Tian, Keir Fraser, Jan Beulich [-- Attachment #1.1: Type: text/plain, Size: 2295 bytes --] 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 results. Below are > some of the unexpected messages: > > Not enabling x2APIC (upon firmware request) > ... > mwait-idle: does not run on family 6 model 94 > ... > [VT-D] iommu.c:875: iommu_fault_status: Primary Pending Fault > [VT-D] INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu > reg = ffff82c000201000 > (on motherboard 1) [VT-D] INTR-REMAP: reason 22 - Present field in the > IRTE entry is clear > (on motherboard 2) [VT-D] INTR-REMAP: reason 25 - Blocked a > compatibility format interrupt request > > This leads to a few questions: > 1) Is there some reason x2APIC should not be enabled on Skylake? What > consequence, if any, is there not having x2APIC enabled? In this case, the firmware has set the x2apic opt-out bit in the DMAR table, indicating that Xen should not use x2apic. You might find an option in your BIOS to undo this; there have been enough errata in the past in this area that I would expect it to be a tweakable. x2apic is the extension to xapic, which permits more than 255 cpus. So long as you don't have that many, there isn't a specific problem with missing x2apic mode. > 2) Should mwait-idle be available on Skylake? We probably need to resync the mwait driver with Linux. It is whitelisted on known cpu model numbers. > 3) What about the IOMMU errors on Skylake - are they a concern? Yes. In both cases, PCI device f0:1f.0 is misconfigured or misbehaving. On motherboard 1, it is delivering an interrupt for which no remapping entry has been set up. On motherboard 2, it is delivering an compatibility-format interrupt, as opposed to a remapable-format interrupt. For motherboard 2, Xen should disallow such a configuration. Either interrupt remapping is enabled and all devices should be configured to issue remmapable interrupts, or interrupt remapping is disabled and everything should be configured to issue compatibility-format interrupts. Either way, diagnosing the problem here starts with identifying what f0:1f.0 is. ~Andrew [-- Attachment #1.2: Type: text/html, Size: 3778 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-11-28 22:14 ` Andrew Cooper @ 2015-12-02 2:34 ` Tian, Kevin 2015-12-02 2:51 ` Eric Shelton 0 siblings, 1 reply; 13+ messages in thread From: Tian, Kevin @ 2015-12-02 2:34 UTC (permalink / raw) To: Andrew Cooper, Eric Shelton, xen-devel, Zhang, Yang Z, Keir Fraser, Jan Beulich [-- Attachment #1.1: Type: text/plain, Size: 2630 bytes --] Eric, could you provide your motherboard information and as Andrew pointed out what’s f0:1f.0? From: Andrew Cooper [mailto:andrew.cooper3@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-d and other error messages 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 results. Below are some of the unexpected messages: Not enabling x2APIC (upon firmware request) ... mwait-idle: does not run on family 6 model 94 ... [VT-D] iommu.c:875: iommu_fault_status: Primary Pending Fault [VT-D] INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg = ffff82c000201000 (on motherboard 1) [VT-D] INTR-REMAP: reason 22 - Present field in the IRTE entry is clear (on motherboard 2) [VT-D] INTR-REMAP: reason 25 - Blocked a compatibility format interrupt request This leads to a few questions: 1) Is there some reason x2APIC should not be enabled on Skylake? What consequence, if any, is there not having x2APIC enabled? In this case, the firmware has set the x2apic opt-out bit in the DMAR table, indicating that Xen should not use x2apic. You might find an option in your BIOS to undo this; there have been enough errata in the past in this area that I would expect it to be a tweakable. x2apic is the extension to xapic, which permits more than 255 cpus. So long as you don't have that many, there isn't a specific problem with missing x2apic mode. 2) Should mwait-idle be available on Skylake? We probably need to resync the mwait driver with Linux. It is whitelisted on known cpu model numbers. 3) What about the IOMMU errors on Skylake - are they a concern? Yes. In both cases, PCI device f0:1f.0 is misconfigured or misbehaving. On motherboard 1, it is delivering an interrupt for which no remapping entry has been set up. On motherboard 2, it is delivering an compatibility-format interrupt, as opposed to a remapable-format interrupt. For motherboard 2, Xen should disallow such a configuration. Either interrupt remapping is enabled and all devices should be configured to issue remmapable interrupts, or interrupt remapping is disabled and everything should be configured to issue compatibility-format interrupts. Either way, diagnosing the problem here starts with identifying what f0:1f.0 is. ~Andrew [-- Attachment #1.2: Type: text/html, Size: 7049 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 2:34 ` Tian, Kevin @ 2015-12-02 2:51 ` Eric Shelton 2015-12-02 9:54 ` Andrew Cooper 2015-12-02 10:45 ` Jan Beulich 0 siblings, 2 replies; 13+ messages in thread From: Eric Shelton @ 2015-12-02 2:51 UTC (permalink / raw) To: Tian, Kevin Cc: Zhang, Yang Z, Andrew Cooper, Keir Fraser, Jan Beulich, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 3461 bytes --] 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 On Tue, Dec 1, 2015 at 9:34 PM, Tian, Kevin <kevin.tian@intel.com> wrote: > Eric, could you provide your motherboard information and as Andrew pointed > out what’s f0:1f.0? > > > > *From:* Andrew Cooper [mailto:andrew.cooper3@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-d and other error messages > > > > 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 results. Below are some of the unexpected messages: > > > > Not enabling x2APIC (upon firmware request) > > ... > > mwait-idle: does not run on family 6 model 94 > > ... > > [VT-D] iommu.c:875: iommu_fault_status: Primary Pending Fault > > [VT-D] INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg > = ffff82c000201000 > > (on motherboard 1) [VT-D] INTR-REMAP: reason 22 - Present field in the > IRTE entry is clear > > (on motherboard 2) [VT-D] INTR-REMAP: reason 25 - Blocked a compatibility > format interrupt request > > > > This leads to a few questions: > > 1) Is there some reason x2APIC should not be enabled on Skylake? What > consequence, if any, is there not having x2APIC enabled? > > > In this case, the firmware has set the x2apic opt-out bit in the DMAR > table, indicating that Xen should not use x2apic. > > You might find an option in your BIOS to undo this; there have been enough > errata in the past in this area that I would expect it to be a tweakable. > > x2apic is the extension to xapic, which permits more than 255 cpus. So > long as you don't have that many, there isn't a specific problem with > missing x2apic mode. > > > 2) Should mwait-idle be available on Skylake? > > > We probably need to resync the mwait driver with Linux. It is whitelisted > on known cpu model numbers. > > > 3) What about the IOMMU errors on Skylake - are they a concern? > > > Yes. > > In both cases, PCI device f0:1f.0 is misconfigured or misbehaving. > > On motherboard 1, it is delivering an interrupt for which no remapping > entry has been set up. > > On motherboard 2, it is delivering an compatibility-format interrupt, as > opposed to a remapable-format interrupt. > > For motherboard 2, Xen should disallow such a configuration. Either > interrupt remapping is enabled and all devices should be configured to > issue remmapable interrupts, or interrupt remapping is disabled and > everything should be configured to issue compatibility-format interrupts. > > Either way, diagnosing the problem here starts with identifying what > f0:1f.0 is. > > ~Andrew > [-- Attachment #1.2: Type: text/html, Size: 6541 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 2:51 ` Eric Shelton @ 2015-12-02 9:54 ` Andrew Cooper 2015-12-02 10:45 ` Jan Beulich 1 sibling, 0 replies; 13+ messages in thread From: Andrew Cooper @ 2015-12-02 9:54 UTC (permalink / raw) To: Eric Shelton, Tian, Kevin Cc: Zhang, Yang Z, xen-devel, Keir Fraser, Jan Beulich [-- 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 ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 2:51 ` Eric Shelton 2015-12-02 9:54 ` Andrew Cooper @ 2015-12-02 10:45 ` Jan Beulich 2015-12-02 15:04 ` Eric Shelton 1 sibling, 1 reply; 13+ messages in thread From: Jan Beulich @ 2015-12-02 10:45 UTC (permalink / raw) To: Eric Shelton Cc: Yang Z Zhang, Andrew Cooper, Kevin Tian, Keir Fraser, xen-devel >>> On 02.12.15 at 03:51, <eshelton@pobox.com> 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) Did you also check "iommu=verbose" output for occurrences of this ID (e.g. representing an IO-APIC or HPET)? Jan ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 10:45 ` Jan Beulich @ 2015-12-02 15:04 ` Eric Shelton 2015-12-02 15:28 ` Jan Beulich 0 siblings, 1 reply; 13+ messages in thread From: Eric Shelton @ 2015-12-02 15:04 UTC (permalink / raw) To: Jan Beulich Cc: Yang Z Zhang, Andrew Cooper, Kevin Tian, Keir Fraser, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 947 bytes --] 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. Eric On Wed, Dec 2, 2015 at 5:45 AM, Jan Beulich <JBeulich@suse.com> wrote: > >>> On 02.12.15 at 03:51, <eshelton@pobox.com> 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) > > Did you also check "iommu=verbose" output for occurrences of this > ID (e.g. representing an IO-APIC or HPET)? > > Jan > > [-- Attachment #1.2: Type: text/html, Size: 1514 bytes --] [-- Attachment #2: xl-dmesg-asrock.txt --] [-- Type: text/plain, Size: 18936 bytes --] Xen 4.6.0-9.fc20 (XEN) Xen version 4.6.0 (user@) (gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7)) debug=n Mon Nov 30 22:31:58 UTC 2015 (XEN) Latest ChangeSet: (XEN) Bootloader: GRUB 2.00 (XEN) Command line: placeholder iommu=debug apic_verbosity=debug loglvl=all console=none dom0_mem=min:1024M dom0_mem=max:4096M (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009c800 (usable) (XEN) 000000000009c800 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 0000000069c3a000 (usable) (XEN) 0000000069c3a000 - 0000000069c3b000 (ACPI NVS) (XEN) 0000000069c3b000 - 0000000069c65000 (reserved) (XEN) 0000000069c65000 - 0000000069cb8000 (usable) (XEN) 0000000069cb8000 - 000000006a3bd000 (reserved) (XEN) 000000006a3bd000 - 0000000076b99000 (usable) (XEN) 0000000076b99000 - 00000000777b0000 (reserved) (XEN) 00000000777b0000 - 0000000077f9a000 (ACPI NVS) (XEN) 0000000077f9a000 - 0000000077fff000 (ACPI data) (XEN) 0000000077fff000 - 0000000078000000 (usable) (XEN) 0000000078000000 - 0000000078100000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fe000000 - 00000000fe011000 (reserved) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000876000000 (usable) (XEN) ACPI: RSDP 000F05B0, 0024 (r2 ALASKA) (XEN) ACPI: XSDT 77A1F098, 00B4 (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FACP 77A41B30, 010C (r5 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: DSDT 77A1F1E8, 22943 (r2 ALASKA A M I 1072009 INTL 20120913) (XEN) ACPI: FACS 77F99F80, 0040 (XEN) ACPI: APIC 77A41C40, 0084 (r3 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FPDT 77A41CC8, 0044 (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FIDT 77A41D10, 009C (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: MCFG 77A41DB0, 003C (r1 ALASKA A M I 1072009 MSFT 97) (XEN) ACPI: HPET 77A41DF0, 0038 (r1 ALASKA A M I 1072009 AMI. 5000B) (XEN) ACPI: SSDT 77A41E28, 036D (r1 SataRe SataTabl 1000 INTL 20120913) (XEN) ACPI: LPIT 77A42198, 0094 (r1 INTEL SKL 0 MSFT 5F) (XEN) ACPI: SSDT 77A42230, 002B (r2 INTEL UsbCTabl 1000 INTL 20120913) (XEN) ACPI: DBGP 77A42260, 0034 (r1 INTEL 0 MSFT 5F) (XEN) ACPI: DBG2 77A42298, 0054 (r0 INTEL 0 MSFT 5F) (XEN) ACPI: SSDT 77A422F0, 0618 (r2 INTEL xh_rvp08 0 INTL 20120913) (XEN) ACPI: AAFT 77A42908, 051A (r1 ALASKA OEMAAFT 1072009 MSFT 97) (XEN) ACPI: SSDT 77A42E28, 5212 (r2 SaSsdt SaSsdt 3000 INTL 20120913) (XEN) ACPI: UEFI 77A48040, 0042 (r1 0 0) (XEN) ACPI: SSDT 77A48088, 0E58 (r2 CpuRef CpuSsdt 3000 INTL 20120913) (XEN) ACPI: DMAR 77A48EE0, 00A8 (r1 INTEL SKL 1 INTL 1) (XEN) ACPI: ASF! 77A48F88, 00A5 (r32 INTEL HCG 1 TFSM F4240) (XEN) System RAM: 32452MB (33230872kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-0000000876000000 (XEN) Domain heap initialised (XEN) found SMP MP-table at 000fc6a0 (XEN) DMI 2.8 present. (XEN) APIC boot state is 'xapic' (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x1808 (XEN) ACPI: v5 SLEEP INFO: control[1:1804], status[1:1800] (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:1804,1:0], pm1x_evt[1:1800,1:0] (XEN) ACPI: 32/64X FACS address mismatch in FADT - 77f99f80/0000000000000000, using 32 (XEN) ACPI: wakeup_vec[77f99f8c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) Processor #2 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) (XEN) Processor #4 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) (XEN) Processor #6 7:14 APIC version 21 (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) ERST table was not found (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) mapped APIC to ffff82cfffdfb000 (fee00000) (XEN) mapped IOAPIC to ffff82cfffdfa000 (fec00000) (XEN) IRQ limits: 120 GSI, 840 MSI/MSI-X (XEN) Failed to enable Interrupt Remapping: Will not enable x2APIC. (XEN) xstate_init: using cntxt_size: 0x440 and states: 0x1f (XEN) Intel machine check reporting enabled (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3514.746 MHz processor. (XEN) Initing memory sharing. (XEN) alt table ffff82d0802b8b50 -> ffff82d0802b9ef4 (XEN) spurious 8259A interrupt: IRQ7. (XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff (XEN) PCI: MCFG area at e0000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-ff (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control not enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) Getting VERSION: 1060015 (XEN) Getting VERSION: 1060015 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Getting ID: 0 (XEN) Getting LVT0: 700 (XEN) Getting LVT1: 400 (XEN) Suppress EOI broadcast on CPU#0 (XEN) enabled ExtINT on CPU#0 (XEN) ESR value before enabling vector: 0x40 after: 0 (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) init IO_APIC IRQs (XEN) IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23, 2-24, 2-25, 2-26, 2-27, 2-28, 2-29, 2-30, 2-31, 2-32, 2-33, 2-34, 2-35, 2-36, 2-37, 2-38, 2-39, 2-40, 2-41, 2-42, 2-43, 2-44, 2-45, 2-46, 2-47, 2-48, 2-49, 2-50, 2-51, 2-52, 2-53, 2-54, 2-55, 2-56, 2-57, 2-58, 2-59, 2-60, 2-61, 2-62, 2-63, 2-64, 2-65, 2-66, 2-67, 2-68, 2-69, 2-70, 2-71, 2-72, 2-73, 2-74, 2-75, 2-76, 2-77, 2-78, 2-79, 2-80, 2-81, 2-82, 2-83, 2-84, 2-85, 2-86, 2-87, 2-88, 2-89, 2-90, 2-91, 2-92, 2-93, 2-94, 2-95, 2-96, 2-97, 2-98, 2-99, 2-100, 2-101, 2-102, 2-103, 2-104, 2-105, 2-106, 2-107, 2-108, 2-109, 2-110, 2-111, 2-112, 2-113, 2-114, 2-115, 2-116, 2-117, 2-118, 2-119 not connected. (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0 (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #2 registers: 120. (XEN) testing the IO APIC....................... (XEN) IO APIC #2...... (XEN) .... register #00: 02000000 (XEN) ....... : physical APIC id: 02 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 00770020 (XEN) ....... : max redirection entries: 0077 (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0020 (XEN) .... register #02: 00000000 (XEN) ....... : arbitration: 00 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 7 00 (XEN) 01 001 01 0 0 0 0 0 1 1 38 (XEN) 02 001 01 0 0 0 0 0 1 1 F0 (XEN) 03 001 01 0 0 0 0 0 1 1 40 (XEN) 04 001 01 0 0 0 0 0 1 1 48 (XEN) 05 001 01 0 0 0 0 0 1 1 50 (XEN) 06 001 01 0 0 0 0 0 1 1 58 (XEN) 07 001 01 0 0 0 0 0 1 1 60 (XEN) 08 001 01 0 0 0 0 0 1 1 68 (XEN) 09 001 01 1 1 0 0 0 1 1 70 (XEN) 0a 001 01 0 0 0 0 0 1 1 78 (XEN) 0b 001 01 0 0 0 0 0 1 1 88 (XEN) 0c 001 01 0 0 0 0 0 1 1 90 (XEN) 0d 001 01 0 0 0 0 0 1 1 98 (XEN) 0e 001 01 0 0 0 0 0 1 1 A0 (XEN) 0f 001 01 0 0 0 0 0 1 1 A8 (XEN) 10 000 00 1 0 0 0 0 0 0 00 (XEN) 11 000 00 1 0 0 0 0 0 0 00 (XEN) 12 000 00 1 0 0 0 0 0 0 00 (XEN) 13 000 00 1 0 0 0 0 0 0 00 (XEN) 14 000 00 1 0 0 0 0 0 0 00 (XEN) 15 000 00 1 0 0 0 0 0 0 00 (XEN) 16 000 00 1 0 0 0 0 0 0 00 (XEN) 17 000 00 1 0 0 0 0 0 0 00 (XEN) 18 094 04 1 0 0 0 0 1 2 86 (XEN) 19 010 00 1 0 0 0 0 1 2 85 (XEN) 1a 059 09 1 0 0 0 0 0 2 08 (XEN) 1b 00A 0A 1 0 0 0 0 0 2 22 (XEN) 1c 003 03 1 0 0 0 0 1 2 20 (XEN) 1d 000 00 1 0 0 0 0 0 0 00 (XEN) 1e 000 00 1 0 0 0 0 0 0 00 (XEN) 1f 000 00 1 0 0 0 0 0 0 00 (XEN) 20 081 01 1 0 0 0 0 1 2 0C (XEN) 21 000 00 1 0 0 0 0 0 0 00 (XEN) 22 000 00 1 0 0 0 0 0 0 00 (XEN) 23 000 00 1 0 0 0 0 0 0 00 (XEN) 24 000 00 1 0 0 0 0 0 0 00 (XEN) 25 000 00 1 0 0 0 0 0 0 00 (XEN) 26 000 00 1 0 0 0 0 0 0 00 (XEN) 27 000 00 1 0 0 0 0 0 0 00 (XEN) 28 000 00 1 0 0 0 0 0 0 00 (XEN) 29 000 00 1 0 0 0 0 0 0 00 (XEN) 2a 000 00 1 0 0 0 0 0 0 00 (XEN) 2b 000 00 1 0 0 0 0 0 0 00 (XEN) 2c 041 01 1 0 0 0 0 0 2 44 (XEN) 2d 000 00 1 0 0 0 0 0 0 00 (XEN) 2e 003 03 1 0 0 0 0 0 2 A0 (XEN) 2f 000 00 1 0 0 0 0 0 0 00 (XEN) 30 000 00 1 0 0 0 0 0 0 00 (XEN) 31 000 00 1 0 0 0 0 0 0 00 (XEN) 32 000 00 1 0 0 0 0 0 0 00 (XEN) 33 000 00 1 0 0 0 0 0 0 00 (XEN) 34 08D 0D 1 0 0 0 0 0 2 18 (XEN) 35 000 00 1 0 0 0 0 0 0 00 (XEN) 36 000 00 1 0 0 0 0 0 0 00 (XEN) 37 000 00 1 0 0 0 0 0 0 00 (XEN) 38 000 00 1 0 0 0 0 0 0 00 (XEN) 39 000 00 1 0 0 0 0 0 0 00 (XEN) 3a 080 00 1 0 0 0 0 0 2 08 (XEN) 3b 010 00 1 0 0 0 0 0 2 10 (XEN) 3c 000 00 1 0 0 0 0 0 0 00 (XEN) 3d 040 00 1 0 0 0 0 0 2 C0 (XEN) 3e 000 00 1 0 0 0 0 0 0 00 (XEN) 3f 020 00 1 0 0 0 0 0 2 0C (XEN) 40 000 00 1 0 0 0 0 0 0 00 (XEN) 41 098 08 1 0 0 0 0 1 2 02 (XEN) 42 004 04 1 0 0 0 0 0 2 08 (XEN) 43 000 00 1 0 0 0 0 0 0 00 (XEN) 44 000 00 1 0 0 0 0 0 0 00 (XEN) 45 000 00 1 0 0 0 0 0 0 00 (XEN) 46 000 00 1 0 0 0 0 0 0 00 (XEN) 47 000 00 1 0 0 0 0 0 0 00 (XEN) 48 000 00 1 0 0 0 0 0 0 00 (XEN) 49 000 00 1 0 0 0 0 0 0 00 (XEN) 4a 000 00 1 0 0 0 0 0 0 00 (XEN) 4b 000 00 1 0 0 0 0 0 0 00 (XEN) 4c 000 00 1 0 0 0 0 0 0 00 (XEN) 4d 000 00 1 0 0 0 0 0 0 00 (XEN) 4e 001 01 1 0 0 0 0 1 2 80 (XEN) 4f 0D0 00 1 0 0 0 0 0 2 10 (XEN) 50 000 00 1 0 0 0 0 0 0 00 (XEN) 51 000 00 1 0 0 0 0 0 0 00 (XEN) 52 000 00 1 0 0 0 0 0 0 00 (XEN) 53 001 01 1 0 0 0 0 1 2 05 (XEN) 54 000 00 1 0 0 0 0 0 0 00 (XEN) 55 000 00 1 0 0 0 0 0 0 00 (XEN) 56 000 00 1 0 0 0 0 0 0 00 (XEN) 57 000 00 1 0 0 0 0 0 0 00 (XEN) 58 000 00 1 0 0 0 0 0 0 00 (XEN) 59 000 00 1 0 0 0 0 0 0 00 (XEN) 5a 080 00 1 0 0 0 0 0 2 A4 (XEN) 5b 000 00 1 0 0 0 0 0 0 00 (XEN) 5c 000 00 1 0 0 0 0 0 0 00 (XEN) 5d 000 00 1 0 0 0 0 0 0 00 (XEN) 5e 000 00 1 0 0 0 0 0 0 00 (XEN) 5f 000 00 1 0 0 0 0 0 0 00 (XEN) 60 000 00 1 0 0 0 0 0 0 00 (XEN) 61 023 03 1 0 0 0 0 0 2 07 (XEN) 62 000 00 1 0 0 0 0 0 0 00 (XEN) 63 000 00 1 0 0 0 0 0 0 00 (XEN) 64 000 00 1 0 0 0 0 1 2 40 (XEN) 65 000 00 1 0 0 0 0 0 0 00 (XEN) 66 018 08 1 0 0 0 0 0 2 20 (XEN) 67 000 00 1 0 0 0 0 0 0 00 (XEN) 68 000 00 1 0 0 0 0 0 0 00 (XEN) 69 000 00 1 0 0 0 0 0 0 00 (XEN) 6a 000 00 1 0 0 0 0 0 0 00 (XEN) 6b 000 00 1 0 0 0 0 0 0 00 (XEN) 6c 000 00 1 0 0 0 0 0 0 00 (XEN) 6d 000 00 1 0 0 0 0 0 0 00 (XEN) 6e 000 00 1 0 0 0 0 0 0 00 (XEN) 6f 000 00 1 0 0 0 0 0 0 00 (XEN) 70 000 00 1 0 0 0 0 0 0 00 (XEN) 71 000 00 1 0 0 0 0 0 0 00 (XEN) 72 000 00 1 0 0 0 0 0 0 00 (XEN) 73 000 00 1 0 0 0 0 0 0 00 (XEN) 74 000 00 1 0 0 0 0 0 0 00 (XEN) 75 000 00 1 0 0 0 0 0 0 00 (XEN) 76 000 00 1 0 0 0 0 0 0 00 (XEN) 77 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ56 -> 0:1 (XEN) IRQ64 -> 0:3 (XEN) IRQ72 -> 0:4 (XEN) IRQ80 -> 0:5 (XEN) IRQ88 -> 0:6 (XEN) IRQ96 -> 0:7 (XEN) IRQ104 -> 0:8 (XEN) IRQ112 -> 0:9 (XEN) IRQ120 -> 0:10 (XEN) IRQ136 -> 0:11 (XEN) IRQ144 -> 0:12 (XEN) IRQ152 -> 0:13 (XEN) IRQ160 -> 0:14 (XEN) IRQ168 -> 0:15 (XEN) .................................... done. (XEN) Using local APIC timer interrupts. (XEN) calibrating APIC timer ... (XEN) ..... CPU clock speed is 3503.5526 MHz. (XEN) ..... host bus clock speed is 23.9969 MHz. (XEN) ..... bus_scale = 0x1892 (XEN) TSC deadline timer enabled (XEN) Platform timer is 23.999MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) mwait-idle: MWAIT substates: 0x142120 (XEN) mwait-idle: v0.4 model 0x5e (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) - VMCS shadowing (XEN) - VM Functions (XEN) - Virtualisation Exceptions (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) Suppress EOI broadcast on CPU#1 (XEN) masked ExtINT on CPU#1 (XEN) Suppress EOI broadcast on CPU#2 (XEN) masked ExtINT on CPU#2 (XEN) Suppress EOI broadcast on CPU#3 (XEN) masked ExtINT on CPU#3 (XEN) Brought up 4 CPUs (XEN) ACPI sleep modes: S3 (XEN) VPMU: disabled (XEN) mcheck_poll: Machine check polling timer started. (XEN) Dom0 has maximum 696 PIRQs (XEN) NX (Execute Disable) protection active (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x204a000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000854000000->0000000858000000 (1021426 pages to be allocated) (XEN) Init. ramdisk: 00000008735f2000->0000000875fffe00 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff8204a000 (XEN) Init. ramdisk: 0000000000000000->0000000000000000 (XEN) Phys-Mach map: ffffffff8204a000->ffffffff8284a000 (XEN) Start info: ffffffff8284a000->ffffffff8284a4b4 (XEN) Page tables: ffffffff8284b000->ffffffff82864000 (XEN) Boot stack: ffffffff82864000->ffffffff82865000 (XEN) TOTAL: ffffffff80000000->ffffffff82c00000 (XEN) ENTRY ADDRESS: ffffffff81d4d1f0 (XEN) Dom0 has maximum 4 VCPUs (XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) ....................................................................done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: All (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 304kB init memory. (XEN) IOAPIC[0]: Set PCI routing entry (2-9 -> 0x70 -> IRQ 9 Mode:1 Active:0) (XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) PCI add device 0000:00:00.0 (XEN) PCI add device 0000:00:02.0 (XEN) PCI add device 0000:00:14.0 (XEN) PCI add device 0000:00:14.2 (XEN) PCI add device 0000:00:16.0 (XEN) PCI add device 0000:00:17.0 (XEN) PCI add device 0000:00:1b.0 (XEN) PCI add device 0000:00:1c.0 (XEN) PCI add device 0000:00:1c.2 (XEN) PCI add device 0000:00:1d.0 (XEN) PCI add device 0000:00:1d.7 (XEN) PCI add device 0000:00:1f.0 (XEN) PCI add device 0000:00:1f.2 (XEN) PCI add device 0000:00:1f.3 (XEN) PCI add device 0000:00:1f.4 (XEN) PCI add device 0000:00:1f.6 (XEN) PCI add device 0000:03:00.0 (XEN) PCI add device 0000:05:00.0 (XEN) IOAPIC[0]: Set PCI routing entry (2-13 -> 0x98 -> IRQ 13 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-1 -> 0x38 -> IRQ 1 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-4 -> 0x48 -> IRQ 4 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-8 -> 0x68 -> IRQ 8 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-14 -> 0xa0 -> IRQ 14 Mode:1 Active:1) (XEN) IOAPIC[0]: Set PCI routing entry (2-16 -> 0xb0 -> IRQ 16 Mode:1 Active:1) (XEN) IOAPIC[0]: Set PCI routing entry (2-18 -> 0xb8 -> IRQ 18 Mode:1 Active:1) (XEN) IOAPIC[0]: Set PCI routing entry (2-19 -> 0x21 -> IRQ 19 Mode:1 Active:1) [-- Attachment #3: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 15:04 ` Eric Shelton @ 2015-12-02 15:28 ` Jan Beulich 2015-12-02 15:37 ` Eric Shelton 0 siblings, 1 reply; 13+ messages in thread From: Jan Beulich @ 2015-12-02 15:28 UTC (permalink / raw) To: Eric Shelton Cc: Yang Z Zhang, Andrew Cooper, Kevin Tian, Keir Fraser, xen-devel >>> On 02.12.15 at 16:04, <eshelton@pobox.com> 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 error returns). Jan ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 15:28 ` Jan Beulich @ 2015-12-02 15:37 ` Eric Shelton 2015-12-02 15:41 ` Jan Beulich 0 siblings, 1 reply; 13+ messages in thread From: Eric Shelton @ 2015-12-02 15:37 UTC (permalink / raw) To: Jan Beulich Cc: Kevin Tian, Keir Fraser, Andrew Cooper, Yang Z Zhang, xen-devel, Eric Shelton On Dec 2, 2015, at 10:28 AM, Jan Beulich <JBeulich@suse.com> wrote: >>>> On 02.12.15 at 16:04, <eshelton@pobox.com> 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 error returns). So when I rebuild the hypervisor, it sounds like I should be doing a debug build? Eric ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 15:37 ` Eric Shelton @ 2015-12-02 15:41 ` Jan Beulich 2015-12-04 21:23 ` Eric Shelton 0 siblings, 1 reply; 13+ messages in thread From: Jan Beulich @ 2015-12-02 15:41 UTC (permalink / raw) To: Eric Shelton Cc: Kevin Tian, Keir Fraser, Andrew Cooper, Yang Z Zhang, xen-devel, Eric Shelton >>> On 02.12.15 at 16:37, <knockknock@gmail.com> wrote: > On Dec 2, 2015, at 10:28 AM, Jan Beulich <JBeulich@suse.com> wrote: > >>>>> On 02.12.15 at 16:04, <eshelton@pobox.com> 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 error returns). > > So when I rebuild the hypervisor, it sounds like I should be doing a debug > build? Yes please. Jan ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-12-02 15:41 ` Jan Beulich @ 2015-12-04 21:23 ` Eric Shelton 0 siblings, 0 replies; 13+ messages in thread From: Eric Shelton @ 2015-12-04 21:23 UTC (permalink / raw) To: Jan Beulich Cc: Yang Z Zhang, Andrew Cooper, Kevin Tian, Keir Fraser, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 837 bytes --] On Wed, Dec 2, 2015 at 10:41 AM, Jan Beulich <JBeulich@suse.com> wrote: > >>> On 02.12.15 at 16:37, <knockknock@gmail.com> wrote: > > On Dec 2, 2015, at 10:28 AM, Jan Beulich <JBeulich@suse.com> wrote: > > > >>>>> On 02.12.15 at 16:04, <eshelton@pobox.com> 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 error returns). > > > > So when I rebuild the hypervisor, it sounds like I should be doing a > debug > > build? > > Yes please. > > With my current setup, it was easier for me to go back to 4.4.3. Apparently the IOAPIC is at 0000:f0.1f.0. Output from 'xl dmesg'' is attached. Eric [-- Attachment #1.2: Type: text/html, Size: 1553 bytes --] [-- Attachment #2: xl-dmesg-4.4.3.txt --] [-- Type: text/plain, Size: 26834 bytes --] .3-7)) debug=n Fri Dec 4 18:12:56 UTC 2015 (XEN) Latest ChangeSet: (XEN) Bootloader: GRUB 2.00 (XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M iommu=debug loglvl=all apic_verbosity=debug (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009c800 (usable) (XEN) 000000000009c800 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 0000000070ec5000 (usable) (XEN) 0000000070ec5000 - 0000000070ec6000 (ACPI NVS) (XEN) 0000000070ec6000 - 0000000070ef0000 (reserved) (XEN) 0000000070ef0000 - 0000000070f43000 (usable) (XEN) 0000000070f43000 - 0000000071648000 (reserved) (XEN) 0000000071648000 - 0000000076b9d000 (usable) (XEN) 0000000076b9d000 - 00000000777b0000 (reserved) (XEN) 00000000777b0000 - 0000000077f9a000 (ACPI NVS) (XEN) 0000000077f9a000 - 0000000077fff000 (ACPI data) (XEN) 0000000077fff000 - 0000000078000000 (usable) (XEN) 0000000078000000 - 0000000078100000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fe000000 - 00000000fe011000 (reserved) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000876000000 (usable) (XEN) ACPI: RSDP 000F05B0, 0024 (r2 ALASKA) (XEN) ACPI: XSDT 77A1F098, 00B4 (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FACP 77A41B30, 010C (r5 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: DSDT 77A1F1E8, 22943 (r2 ALASKA A M I 1072009 INTL 20120913) (XEN) ACPI: FACS 77F99F80, 0040 (XEN) ACPI: APIC 77A41C40, 0084 (r3 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FPDT 77A41CC8, 0044 (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FIDT 77A41D10, 009C (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: MCFG 77A41DB0, 003C (r1 ALASKA A M I 1072009 MSFT 97) (XEN) ACPI: HPET 77A41DF0, 0038 (r1 ALASKA A M I 1072009 AMI. 5000B) (XEN) ACPI: SSDT 77A41E28, 036D (r1 SataRe SataTabl 1000 INTL 20120913) (XEN) ACPI: LPIT 77A42198, 0094 (r1 INTEL SKL 0 MSFT 5F) (XEN) ACPI: SSDT 77A42230, 002B (r2 INTEL UsbCTabl 1000 INTL 20120913) (XEN) ACPI: DBGP 77A42260, 0034 (r1 INTEL 0 MSFT 5F) (XEN) ACPI: DBG2 77A42298, 0054 (r0 INTEL 0 MSFT 5F) (XEN) ACPI: SSDT 77A422F0, 0618 (r2 INTEL xh_rvp08 0 INTL 20120913) (XEN) ACPI: AAFT 77A42908, 051A (r1 ALASKA OEMAAFT 1072009 MSFT 97) (XEN) ACPI: SSDT 77A42E28, 5212 (r2 SaSsdt SaSsdt 3000 INTL 20120913) (XEN) ACPI: UEFI 77A48040, 0042 (r1 0 0) (XEN) ACPI: SSDT 77A48088, 0E58 (r2 CpuRef CpuSsdt 3000 INTL 20120913) (XEN) ACPI: DMAR 77A48EE0, 00A8 (r1 INTEL SKL 1 INTL 1) (XEN) ACPI: ASF! 77A48F88, 00A5 (r32 INTEL HCG 1 TFSM F4240) (XEN) System RAM: 32452MB (33230888kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-0000000876000000 (XEN) Domain heap initialised (XEN) found SMP MP-table at 000fc670 (XEN) DMI 2.8 present. (XEN) APIC boot state is 'xapic' (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x1808 (XEN) ACPI: v5 SLEEP INFO: control[1:1804], status[1:1800] (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1804,0], pm1x_evt[1800,0] (XEN) ACPI: 32/64X FACS address mismatch in FADT - 77f99f80/0000000000000000, using 32 (XEN) ACPI: wakeup_vec[77f99f8c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) Processor #2 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) (XEN) Processor #4 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) (XEN) Processor #6 7:14 APIC version 21 (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) [VT-D]dmar.c:809: Host address width 39 (XEN) [VT-D]dmar.c:823: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:485: dmaru->address = fed90000 (XEN) [VT-D]iommu.c:1151: drhd->address = fed90000 iommu->reg = ffff82c000201000 (XEN) [VT-D]iommu.c:1153: cap = 1c0000c40660462 ecap = 7e3ff0505e (XEN) [VT-D]dmar.c:396: endpoint: 0000:00:02.0 (XEN) [VT-D]dmar.c:823: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:485: dmaru->address = fed91000 (XEN) [VT-D]iommu.c:1151: drhd->address = fed91000 iommu->reg = ffff82c000203000 (XEN) [VT-D]iommu.c:1153: cap = d2008c40660462 ecap = f050da (XEN) [VT-D]dmar.c:410: IOAPIC: 0000:f0:1f.0 (XEN) [VT-D]dmar.c:374: MSI HPET: 0000:00:1f.0 (XEN) [VT-D]dmar.c:499: flags: INCLUDE_ALL (XEN) [VT-D]dmar.c:828: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:396: endpoint: 0000:00:14.0 (XEN) [VT-D]dmar.c:694: RMRR region: base_addr 77552000 end_address 77571fff (XEN) [VT-D]dmar.c:828: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:620: RMRR address range not in reserved memory base = 78800000 end = 88ffffff; iommu_inclusive_mapping=1 parameter may be needed. (XEN) [VT-D]dmar.c:396: endpoint: 0000:00:02.0 (XEN) [VT-D]dmar.c:694: RMRR region: base_addr 78800000 end_address 88ffffff (XEN) ERST table was not found (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) mapped APIC to ffff82cfffdfb000 (fee00000) (XEN) mapped IOAPIC to ffff82cfffdfa000 (fec00000) (XEN) IRQ limits: 120 GSI, 840 MSI/MSI-X (XEN) Failed to enable Interrupt Remapping: Will not enable x2APIC. (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3511.848 MHz processor. (XEN) Initing memory sharing. (XEN) xstate_init: using cntxt_size: 0x440 and states: 0x1f (XEN) mce_intel.c:725: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0 (XEN) Intel machine check reporting enabled (XEN) spurious 8259A interrupt: IRQ7. (XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff (XEN) PCI: MCFG area at e0000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-ff (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control not enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) Getting VERSION: 1060015 (XEN) Getting VERSION: 1060015 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Getting ID: 0 (XEN) Getting LVT0: 700 (XEN) Getting LVT1: 400 (XEN) Suppress EOI broadcast on CPU#0 (XEN) enabled ExtINT on CPU#0 (XEN) ESR value before enabling vector: 0x40 after: 0 (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) init IO_APIC IRQs (XEN) IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23, 2-24, 2-25, 2-26, 2-27, 2-28, 2-29, 2-30, 2-31, 2-32, 2-33, 2-34, 2-35, 2-36, 2-37, 2-38, 2-39, 2-40, 2-41, 2-42, 2-43, 2-44, 2-45, 2-46, 2-47, 2-48, 2-49, 2-50, 2-51, 2-52, 2-53, 2-54, 2-55, 2-56, 2-57, 2-58, 2-59, 2-60, 2-61, 2-62, 2-63, 2-64, 2-65, 2-66, 2-67, 2-68, 2-69, 2-70, 2-71, 2-72, 2-73, 2-74, 2-75, 2-76, 2-77, 2-78, 2-79, 2-80, 2-81, 2-82, 2-83, 2-84, 2-85, 2-86, 2-87, 2-88, 2-89, 2-90, 2-91, 2-92, 2-93, 2-94, 2-95, 2-96, 2-97, 2-98, 2-99, 2-100, 2-101, 2-102, 2-103, 2-104, 2-105, 2-106, 2-107, 2-108, 2-109, 2-110, 2-111, 2-112, 2-113, 2-114, 2-115, 2-116, 2-117, 2-118, 2-119 not connected. (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0 (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #2 registers: 120. (XEN) testing the IO APIC....................... (XEN) IO APIC #2...... (XEN) .... register #00: 02000000 (XEN) ....... : physical APIC id: 02 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 00770020 (XEN) ....... : max redirection entries: 0077 (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0020 (XEN) .... register #02: 00000000 (XEN) ....... : arbitration: 00 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 7 00 (XEN) 01 001 01 0 0 0 0 0 1 1 38 (XEN) 02 001 01 0 0 0 0 0 1 1 F0 (XEN) 03 001 01 0 0 0 0 0 1 1 40 (XEN) 04 001 01 0 0 0 0 0 1 1 48 (XEN) 05 001 01 0 0 0 0 0 1 1 50 (XEN) 06 001 01 0 0 0 0 0 1 1 58 (XEN) 07 001 01 0 0 0 0 0 1 1 60 (XEN) 08 001 01 0 0 0 0 0 1 1 68 (XEN) 09 001 01 1 1 0 0 0 1 1 70 (XEN) 0a 001 01 0 0 0 0 0 1 1 78 (XEN) 0b 001 01 0 0 0 0 0 1 1 88 (XEN) 0c 001 01 0 0 0 0 0 1 1 90 (XEN) 0d 001 01 0 0 0 0 0 1 1 98 (XEN) 0e 001 01 0 0 0 0 0 1 1 A0 (XEN) 0f 001 01 0 0 0 0 0 1 1 A8 (XEN) 10 000 00 1 0 0 0 0 0 0 00 (XEN) 11 000 00 1 0 0 0 0 0 0 00 (XEN) 12 000 00 1 0 0 0 0 0 0 00 (XEN) 13 000 00 1 0 0 0 0 0 0 00 (XEN) 14 000 00 1 0 0 0 0 0 0 00 (XEN) 15 000 00 1 0 0 0 0 0 0 00 (XEN) 16 000 00 1 0 0 0 0 0 0 00 (XEN) 17 000 00 1 0 0 0 0 0 0 00 (XEN) 18 000 00 1 0 0 0 0 0 0 00 (XEN) 19 014 04 1 0 0 0 0 1 2 85 (XEN) 1a 070 00 1 0 0 0 0 0 2 08 (XEN) 1b 019 09 1 0 0 0 0 0 2 A2 (XEN) 1c 000 00 1 0 0 0 0 0 0 00 (XEN) 1d 000 00 1 0 0 0 0 0 0 00 (XEN) 1e 000 00 1 0 0 0 0 0 0 00 (XEN) 1f 000 00 1 0 0 0 0 0 0 00 (XEN) 20 0C5 05 1 0 0 0 0 1 2 0C (XEN) 21 000 00 1 0 0 0 0 0 0 00 (XEN) 22 000 00 1 0 0 0 0 0 0 00 (XEN) 23 000 00 1 0 0 0 0 0 0 00 (XEN) 24 000 00 1 0 0 0 0 0 0 00 (XEN) 25 046 06 1 0 0 0 0 1 2 86 (XEN) 26 000 00 1 0 0 0 0 0 0 00 (XEN) 27 051 01 1 0 0 0 0 0 2 01 (XEN) 28 000 00 1 0 0 0 0 0 0 00 (XEN) 29 000 00 1 0 0 0 0 0 0 00 (XEN) 2a 000 00 1 0 0 0 0 0 0 00 (XEN) 2b 000 00 1 0 0 0 0 0 0 00 (XEN) 2c 021 01 1 0 0 0 0 0 2 04 (XEN) 2d 000 00 1 0 0 0 0 0 0 00 (XEN) 2e 083 03 1 0 0 0 0 1 2 84 (XEN) 2f 000 00 1 0 0 0 0 0 0 00 (XEN) 30 000 00 1 0 0 0 0 0 0 00 (XEN) 31 000 00 1 0 0 0 0 0 0 00 (XEN) 32 000 00 1 0 0 0 0 0 0 00 (XEN) 33 000 00 1 0 0 0 0 0 0 00 (XEN) 34 000 00 1 0 0 0 0 0 0 00 (XEN) 35 000 00 1 0 0 0 0 0 0 00 (XEN) 36 000 00 1 0 0 0 0 0 0 00 (XEN) 37 000 00 1 0 0 0 0 0 0 00 (XEN) 38 000 00 1 0 0 0 0 0 0 00 (XEN) 39 000 00 1 0 0 0 0 0 0 00 (XEN) 3a 0C2 02 1 0 0 0 0 0 2 10 (XEN) 3b 0D0 00 1 0 0 0 0 0 2 10 (XEN) 3c 000 00 1 0 0 0 0 0 0 00 (XEN) 3d 000 00 1 0 0 0 0 0 0 00 (XEN) 3e 082 02 1 0 0 0 0 0 2 6A (XEN) 3f 000 00 1 0 0 0 0 0 0 00 (XEN) 40 000 00 1 0 0 0 0 0 0 00 (XEN) 41 0B8 08 1 0 0 0 0 1 2 01 (XEN) 42 004 04 1 0 0 0 0 0 2 28 (XEN) 43 000 00 1 0 0 0 0 0 0 00 (XEN) 44 000 00 1 0 0 0 0 0 0 00 (XEN) 45 000 00 1 0 0 0 0 0 0 00 (XEN) 46 000 00 1 0 0 0 0 0 0 00 (XEN) 47 000 00 1 0 0 0 0 0 0 00 (XEN) 48 000 00 1 0 0 0 0 0 0 00 (XEN) 49 000 00 1 0 0 0 0 0 0 00 (XEN) 4a 000 00 1 0 0 0 0 0 0 00 (XEN) 4b 000 00 1 0 0 0 0 0 0 00 (XEN) 4c 000 00 1 0 0 0 0 0 0 00 (XEN) 4d 000 00 1 0 0 0 0 0 0 00 (XEN) 4e 000 00 1 0 0 0 0 0 0 00 (XEN) 4f 0D0 00 1 0 0 0 0 1 2 52 (XEN) 50 000 00 1 0 0 0 0 0 0 00 (XEN) 51 000 00 1 0 0 0 0 0 0 00 (XEN) 52 09C 0C 1 0 0 0 0 0 2 29 (XEN) 53 000 00 1 0 0 0 0 0 0 00 (XEN) 54 000 00 1 0 0 0 0 0 0 00 (XEN) 55 000 00 1 0 0 0 0 0 0 00 (XEN) 56 000 00 1 0 0 0 0 0 0 00 (XEN) 57 000 00 1 0 0 0 0 0 0 00 (XEN) 58 000 00 1 0 0 0 0 0 0 00 (XEN) 59 000 00 1 0 0 0 0 0 0 00 (XEN) 5a 080 00 1 0 0 0 0 0 2 84 (XEN) 5b 000 00 1 0 0 0 0 0 0 00 (XEN) 5c 000 00 1 0 0 0 0 0 0 00 (XEN) 5d 000 00 1 0 0 0 0 0 0 00 (XEN) 5e 0C9 09 1 0 0 0 0 1 2 08 (XEN) 5f 000 00 1 0 0 0 0 0 0 00 (XEN) 60 000 00 1 0 0 0 0 0 0 00 (XEN) 61 032 02 1 0 0 0 0 0 2 07 (XEN) 62 000 00 1 0 0 0 0 0 0 00 (XEN) 63 000 00 1 0 0 0 0 0 0 00 (XEN) 64 098 08 1 0 0 0 0 1 2 00 (XEN) 65 000 00 1 0 0 0 0 0 0 00 (XEN) 66 008 08 1 0 0 0 0 0 2 20 (XEN) 67 000 00 1 0 0 0 0 0 0 00 (XEN) 68 000 00 1 0 0 0 0 0 0 00 (XEN) 69 000 00 1 0 0 0 0 0 0 00 (XEN) 6a 000 00 1 0 0 0 0 0 0 00 (XEN) 6b 000 00 1 0 0 0 0 0 0 00 (XEN) 6c 000 00 1 0 0 0 0 0 0 00 (XEN) 6d 000 00 1 0 0 0 0 0 0 00 (XEN) 6e 000 00 1 0 0 0 0 0 0 00 (XEN) 6f 000 00 1 0 0 0 0 0 0 00 (XEN) 70 000 00 1 0 0 0 0 0 0 00 (XEN) 71 000 00 1 0 0 0 0 0 0 00 (XEN) 72 000 00 1 0 0 0 0 0 0 00 (XEN) 73 000 00 1 0 0 0 0 0 0 00 (XEN) 74 000 00 1 0 0 0 0 0 0 00 (XEN) 75 000 00 1 0 0 0 0 0 0 00 (XEN) 76 000 00 1 0 0 0 0 0 0 00 (XEN) 77 030 00 1 0 0 0 0 0 2 85 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ56 -> 0:1 (XEN) IRQ64 -> 0:3 (XEN) IRQ72 -> 0:4 (XEN) IRQ80 -> 0:5 (XEN) IRQ88 -> 0:6 (XEN) IRQ96 -> 0:7 (XEN) IRQ104 -> 0:8 (XEN) IRQ112 -> 0:9 (XEN) IRQ120 -> 0:10 (XEN) IRQ136 -> 0:11 (XEN) IRQ144 -> 0:12 (XEN) IRQ152 -> 0:13 (XEN) IRQ160 -> 0:14 (XEN) IRQ168 -> 0:15 (XEN) .................................... done. (XEN) Using local APIC timer interrupts. (XEN) calibrating APIC timer ... (XEN) ..... CPU clock speed is 3504.5216 MHz. (XEN) ..... host bus clock speed is 24.0035 MHz. (XEN) ..... bus_scale = 0x1894 (XEN) TSC deadline timer enabled (XEN) Platform timer is 23.999MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) mwait-idle: MWAIT substates: 0x142120 (XEN) mwait-idle: v0.4 model 0x5e (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) - VMCS shadowing (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) Suppress EOI broadcast on CPU#1 (XEN) masked ExtINT on CPU#1 (XEN) Suppress EOI broadcast on CPU#2 (XEN) masked ExtINT on CPU#2 (XEN) Suppress EOI broadcast on CPU#3 (XEN) masked ExtINT on CPU#3 (XEN) Brought up 4 CPUs (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x204a000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000854000000->0000000858000000 (1022204 pages to be allocated) (XEN) Init. ramdisk: 00000008738fc000->0000000876000000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff8204a000 (XEN) Init. ramdisk: 0000000000000000->0000000000000000 (XEN) Phys-Mach map: ffffffff8204a000->ffffffff8284a000 (XEN) Start info: ffffffff8284a000->ffffffff8284a4b4 (XEN) Page tables: ffffffff8284b000->ffffffff82864000 (XEN) Boot stack: ffffffff82864000->ffffffff82865000 (XEN) TOTAL: ffffffff80000000->ffffffff82c00000 (XEN) ENTRY ADDRESS: ffffffff81d4d1f0 (XEN) Dom0 has maximum 4 VCPUs (XEN) [VT-D]iommu.c:1435: d0:Hostbridge: skip 0000:00:00.0 map (XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) [VT-D]iommu.c:1449: d0:PCIe: map 0000:00:02.0 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:14.0 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:14.2 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:16.0 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:17.0 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:1f.0 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:1f.2 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:1f.3 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:1f.4 (XEN) [VT-D]iommu.c:1461: d0:PCI: map 0000:00:1f.6 (XEN) [VT-D]iommu.c:1449: d0:PCIe: map 0000:03:00.0 (XEN) [VT-D]iommu.c:730: iommu_enable_translation: iommu->reg = ffff82c000201000 (XEN) [VT-D]iommu.c:730: iommu_enable_translation: iommu->reg = ffff82c000203000 (XEN) Scrubbing Free RAM: ......................................................................................................................................................................................................................................................................................done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: All (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 264kB init memory. (XEN) traps.c:2524:d0 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d0 Domain attempted WRMSR 00000000c0000082 from 0xffff82d0802b3000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d0 Domain attempted WRMSR 00000000c0000083 from 0xffff82d0802b3080 to 0xffffffff81776470. (XEN) traps.c:2524:d0 Domain attempted WRMSR 0000000000000174 from 0x000000000000e008 to 0x0000000000000010. (XEN) traps.c:2524:d0 Domain attempted WRMSR 0000000000000175 from 0xffff82d0802b7fc0 to 0x0000000000000000. (XEN) traps.c:2524:d0 Domain attempted WRMSR 0000000000000176 from 0xffff82d08021d090 to 0xffffffff81776240. (XEN) traps.c:2524:d0 Domain attempted WRMSR 00000000c0000084 from 0x0000000000034700 to 0x0000000000047700. (XEN) traps.c:2524:d0 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d0 Domain attempted WRMSR 00000000c0000082 from 0xffff830862163000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d0 Domain attempted WRMSR 00000000c0000083 from 0xffff830862163080 to 0xffffffff81776470. (XEN) IOAPIC[0]: Set PCI routing entry (2-9 -> 0x70 -> IRQ 9 Mode:1 Active:0) (XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) PCI add device 0000:00:00.0 (XEN) PCI add device 0000:00:02.0 (XEN) PCI add device 0000:00:14.0 (XEN) PCI add device 0000:00:14.2 (XEN) PCI add device 0000:00:16.0 (XEN) PCI add device 0000:00:17.0 (XEN) PCI add device 0000:00:1b.0 (XEN) PCI add device 0000:00:1c.0 (XEN) PCI add device 0000:00:1c.2 (XEN) PCI add device 0000:00:1d.0 (XEN) PCI add device 0000:00:1d.7 (XEN) PCI add device 0000:00:1f.0 (XEN) PCI add device 0000:00:1f.2 (XEN) PCI add device 0000:00:1f.3 (XEN) PCI add device 0000:00:1f.4 (XEN) PCI add device 0000:00:1f.6 (XEN) PCI add device 0000:03:00.0 (XEN) IOAPIC[0]: Set PCI routing entry (2-13 -> 0x98 -> IRQ 13 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-1 -> 0x38 -> IRQ 1 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-4 -> 0x48 -> IRQ 4 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-8 -> 0x68 -> IRQ 8 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (2-14 -> 0xa0 -> IRQ 14 Mode:1 Active:1) (XEN) IOAPIC[0]: Set PCI routing entry (2-16 -> 0xb0 -> IRQ 16 Mode:1 Active:1) (XEN) IOAPIC[0]: Set PCI routing entry (2-18 -> 0xb8 -> IRQ 18 Mode:1 Active:1) (XEN) IOAPIC[0]: Set PCI routing entry (2-19 -> 0x21 -> IRQ 19 Mode:1 Active:1) (XEN) [VT-D]iommu.c:1598: d0:PCI: unmap 0000:00:1f.6 (XEN) [VT-D]iommu.c:1461: d1:PCI: map 0000:00:1f.6 (XEN) printk: 18 messages suppressed. (XEN) traps.c:2524:d1 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d1 Domain attempted WRMSR 00000000c0000082 from 0xffff830862143000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d1 Domain attempted WRMSR 00000000c0000083 from 0xffff830862143080 to 0xffffffff81776470. (XEN) traps.c:2524:d1 Domain attempted WRMSR 0000000000000174 from 0x000000000000e008 to 0x0000000000000010. (XEN) traps.c:2524:d1 Domain attempted WRMSR 0000000000000175 from 0xffff830862147fc0 to 0x0000000000000000. (XEN) traps.c:2524:d1 Domain attempted WRMSR 0000000000000176 from 0xffff82d08021d090 to 0xffffffff81776240. (XEN) traps.c:2524:d1 Domain attempted WRMSR 00000000c0000084 from 0x0000000000034700 to 0x0000000000047700. (XEN) traps.c:2524:d1 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d1 Domain attempted WRMSR 00000000c0000082 from 0xffff82d0802b3000 to 0xffffffff81773ad0. (XEN) printk: 19 messages suppressed. (XEN) traps.c:2524:d2 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d2 Domain attempted WRMSR 00000000c0000082 from 0xffff830862163000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d2 Domain attempted WRMSR 00000000c0000083 from 0xffff830862163080 to 0xffffffff81776470. (XEN) printk: 25 messages suppressed. (XEN) traps.c:2524:d3 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d3 Domain attempted WRMSR 00000000c0000082 from 0xffff830862143000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d3 Domain attempted WRMSR 00000000c0000083 from 0xffff830862143080 to 0xffffffff81776470. (XEN) traps.c:2524:d3 Domain attempted WRMSR 0000000000000174 from 0x000000000000e008 to 0x0000000000000010. (XEN) traps.c:2524:d3 Domain attempted WRMSR 0000000000000175 from 0xffff830862147fc0 to 0x0000000000000000. (XEN) traps.c:2524:d3 Domain attempted WRMSR 0000000000000176 from 0xffff82d08021d090 to 0xffffffff81776240. (XEN) traps.c:2524:d3 Domain attempted WRMSR 00000000c0000084 from 0x0000000000034700 to 0x0000000000047700. (XEN) traps.c:2524:d3 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d3 Domain attempted WRMSR 00000000c0000082 from 0xffff830862163000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d3 Domain attempted WRMSR 00000000c0000083 from 0xffff830862163080 to 0xffffffff81776470. (XEN) printk: 18 messages suppressed. (XEN) traps.c:2524:d6 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d6 Domain attempted WRMSR 00000000c0000082 from 0xffff830862163000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d6 Domain attempted WRMSR 00000000c0000083 from 0xffff830862163080 to 0xffffffff81776470. (XEN) traps.c:2524:d6 Domain attempted WRMSR 0000000000000174 from 0x000000000000e008 to 0x0000000000000010. (XEN) traps.c:2524:d6 Domain attempted WRMSR 0000000000000175 from 0xffff830862167fc0 to 0x0000000000000000. (XEN) traps.c:2524:d6 Domain attempted WRMSR 0000000000000176 from 0xffff82d08021d090 to 0xffffffff81776240. (XEN) traps.c:2524:d6 Domain attempted WRMSR 00000000c0000084 from 0x0000000000034700 to 0x0000000000047700. (XEN) traps.c:2524:d6 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d6 Domain attempted WRMSR 00000000c0000082 from 0xffff830862153000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d6 Domain attempted WRMSR 00000000c0000083 from 0xffff830862153080 to 0xffffffff81776470. (XEN) printk: 18 messages suppressed. (XEN) traps.c:2524:d7 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d7 Domain attempted WRMSR 00000000c0000082 from 0xffff830862163000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d7 Domain attempted WRMSR 00000000c0000083 from 0xffff830862163080 to 0xffffffff81776470. (XEN) traps.c:2524:d7 Domain attempted WRMSR 0000000000000174 from 0x000000000000e008 to 0x0000000000000010. (XEN) traps.c:2524:d7 Domain attempted WRMSR 0000000000000175 from 0xffff830862167fc0 to 0x0000000000000000. (XEN) traps.c:2524:d7 Domain attempted WRMSR 0000000000000176 from 0xffff82d08021d090 to 0xffffffff81776240. (XEN) traps.c:2524:d7 Domain attempted WRMSR 00000000c0000084 from 0x0000000000034700 to 0x0000000000047700. (XEN) traps.c:2524:d7 Domain attempted WRMSR 00000000c0000081 from 0xe023e00800000000 to 0x0023001000000000. (XEN) traps.c:2524:d7 Domain attempted WRMSR 00000000c0000082 from 0xffff830862163000 to 0xffffffff81773ad0. (XEN) traps.c:2524:d7 Domain attempted WRMSR 00000000c0000083 from 0xffff830862163080 to 0xffffffff81776470. [-- Attachment #3: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Skylake: VT-d and other error messages 2015-11-28 20:46 Skylake: VT-d and other error messages Eric Shelton 2015-11-28 22:14 ` Andrew Cooper @ 2015-12-02 8:47 ` Shuai Ruan [not found] ` <20151202084717.GA18791@shuai.ruan@linux.intel.com> 2 siblings, 0 replies; 13+ messages in thread From: Shuai Ruan @ 2015-12-02 8:47 UTC (permalink / raw) To: Eric Shelton Cc: Kevin Tian, Keir Fraser, Andrew Cooper, Jan Beulich, Yang Zhang, xen-devel 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: iommu_fault_status: Primary Pending Fault > [VT-D] INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg = > ffff82c000201000 > (on motherboard 1) [VT-D] INTR-REMAP: reason 22 - Present field in the IRTE > entry is clear > (on motherboard 2) [VT-D] INTR-REMAP: reason 25 - Blocked a compatibility > format interrupt request > The error above do not happen on my skylake machine. Thanks Shuai > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
[parent not found: <20151202084717.GA18791@shuai.ruan@linux.intel.com>]
* Re: Skylake: VT-d and other error messages [not found] ` <20151202084717.GA18791@shuai.ruan@linux.intel.com> @ 2015-12-02 9:07 ` Shuai Ruan 0 siblings, 0 replies; 13+ messages in thread From: Shuai Ruan @ 2015-12-02 9:07 UTC (permalink / raw) To: Eric Shelton Cc: Kevin Tian, Keir Fraser, Andrew Cooper, Jan Beulich, Yang Zhang, xen-devel 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. When disable an option called "X2APIC Opt Out" in bios , the message will disappear. > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2015-12-04 21:23 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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.