WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828

To: "Stefan Bauer" <stefan.bauer@xxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000
From: "Ross Philipson" <Ross.Philipson@xxxxxxxxxx>
Date: Tue, 28 Oct 2008 15:22:48 -0400
Cc:
Delivery-date: Tue, 28 Oct 2008 12:23:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4906E4BE.7040102@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4906E4BE.7040102@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack45UL3qS5Vd41+RmabqN7oh0Zo4wATLGrg
Thread-topic: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000
So the trace below is showing a failure during Xen boot and later you
have trouble passing through a graphics card to an HVM? Do you get
subsequent errors when starting the HVM? What is device 00:2.0 that is
causing the fault below? Reason 5 indicates a DMA write to a page where
the IOMMU PTE W bit is clear to disallow DMA writes.

Thanks
Ross

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefan Bauer
Sent: Tuesday, October 28, 2008 6:09 AM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg
=ffff828bfff57000

Dear Users,

Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64.

I cant use VT-d to passthrough pci-e graphiccard to my win2000 hvm
guest:

Probably the problem is caused by that iommu errors, please see beleow:

xm dmesg

 __  __            _____  _____  ___
 \ \/ /___ _ __   |___ / |___ / / _ \
  \  // _ \ '_ \    |_ \   |_ \| | | |
  /  \  __/ | | |  ___) | ___) | |_| |
 /_/\_\___|_| |_| |____(_)____(_)___/

(XEN) Xen version 3.3.0 (root@) (gcc version 4.1.2 20061115
(prerelease) (Debian 4.1.1-21)) Sat Oct 25 12:58:03 CEST 2008
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: console=vga max_loop=128 dom0_mem=512M iommu=1 vtd=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e000 (usable)
(XEN)  000000000009e000 - 00000000000a0000 (reserved)
(XEN)  00000000000ce000 - 00000000000d0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000be4b0000 (usable)
(XEN)  00000000be4b0000 - 00000000be4c9000 (ACPI data)
(XEN)  00000000be4c9000 - 00000000be4cc000 (ACPI NVS)
(XEN)  00000000be4cc000 - 00000000c0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN) System RAM: 3044MB (3117368kB)
(XEN) ACPI: RSDP 000F5E00, 0024 (r2 PTLTD )
(XEN) ACPI: XSDT BE4BD887, 00B4 (r1 LENOVO TC-2R     60400D0  LTP
   0)
(XEN) ACPI: TCPA BE4C8AD9, 0032 (r2 LENOVO TC-2R     60400D0 PTL
   0)
(XEN) ACPI: FACP BE4C8B0B, 00F4 (r3 INTEL            60400D0 PTL
   3)
(XEN) ACPI: DSDT BE4C0F80, 7AE5 (r1  INTEL BEARLAKE  60400D0 MSFT
100000E)
(XEN) ACPI: FACS BE4CBFC0, 0040
(XEN) ACPI: DMAR BE4C8BFF, 0110 (r1 Intel  OEMDMAR   60400D0 LOHR
   1)
(XEN) ACPI: SLIC BE4C8D0F, 0176 (r1 LENOVO TC-2R     60400D0  LTP
   0)
(XEN) ACPI: MCFG BE4C8E85, 003C (r1 PTLTD    MCFG    60400D0  LTP
   0)
(XEN) ACPI: HPET BE4C8EC1, 0038 (r1 PTLTD  HPETTBL   60400D0  LTP
   1)
(XEN) ACPI: APIC BE4C8EF9, 0068 (r1 PTLTD        APIC    60400D0  LTP
   0)
(XEN) ACPI: BOOT BE4C8F61, 0028 (r1 PTLTD  $SBFTBL$  60400D0  LTP
   1)
(XEN) ACPI: ASF! BE4C8F89, 0077 (r16   CETP     CETP  60400D0 PTL
    1)
(XEN) ACPI: SSDT BE4BF1CA, 025F (r1  PmRef  Cpu0Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BF124, 00A6 (r1  PmRef  Cpu7Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BF07E, 00A6 (r1  PmRef  Cpu6Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEFD8, 00A6 (r1  PmRef  Cpu5Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEF32, 00A6 (r1  PmRef  Cpu4Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEE8C, 00A6 (r1  PmRef  Cpu3Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEDE6, 00A6 (r1  PmRef  Cpu2Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BED40, 00A6 (r1  PmRef  Cpu1Tst     3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BD93B, 1405 (r1  PmRef    CpuPm     3000 INTL
20050228)
(XEN) Xen heap: 14MB (14688kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Intel VT-d has been enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2327.540 MHz processor.
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz stepping 0b
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz stepping 0b
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000
(XEN) [VT-D]iommu.c:744: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:729: iommu_fault:DMA Write: 0:2.0 addr 200200000
REASON 5 iommu->reg = ffff828bfff57000
(XEN) print_vtd_entries: iommu = ffff8300bd6ad180 bdf = 0:2:0 gmfn =
200200
(XEN)     root_entry = ffff8300bc9e0000
(XEN)     root_entry[0] = b9cd6001
(XEN)     context = ffff8300b9cd6000
(XEN)     context[10] = 101_be4a6001
(XEN)     l3 = ffff8300be4a6000
(XEN)     l3_index = 8
(XEN)     l3[8] = 0
(XEN)     l3[8] not present
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x52fecc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   00000000b8000000->00000000b9000000 (126976 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff8052fecc
(XEN)  Init. ramdisk: ffffffff80530000->ffffffff80a98c00
(XEN)  Phys-Mach map: ffffffff80a99000->ffffffff80b99000
(XEN)  Start info:    ffffffff80b99000->ffffffff80b994a4
(XEN)  Page tables:   ffffffff80b9a000->ffffffff80ba5000
(XEN)  Boot stack:    ffffffff80ba5000->ffffffff80ba6000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: ........................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen)
(XEN) Freed 108kB init memory.
(XEN) domctl.c:635:d0 XEN_DOMCTL_test_assign_device: 1:0:0 already
assigned, or non-existent
(XEN) domctl.c:635:d0 XEN_DOMCTL_test_assign_device: 1:0:0 already
assigned, or non-existent


Help is greatly appreciated.


-- 
stefan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel