|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000
Cheers Daniel, Good to hear you've got it going. I am using PCI however. I am about to tear the whole build done and run 3.2.1. again to see if that resolves some issues. grtz Han Daniel Kao-2 wrote: > > > > > > > > I use vtd=1 instead of iommu=1 but I'm not sure what the difference > is. Also, I'm running Xen 3.2.1 that I compiled myself under a > CentOS > 5.2 x86_64 system. I've stayed away from 3.3 until I see more > stability with VT-d. > > (XEN) Xen version 3.2.1 ( root@xxxxxxxxxxxxxxx ) (gcc version 4.1.2 > 20071124 (Red Hat 4.1.2-42)) Fri Jul 18 04:47:33 PDT 2008 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: vtd=1 > > ... > > (XEN) [VT-D]intel-iommu.c:769: iommu_page_fault: iommu->reg = > ffff828bfff57000 > (XEN) [VT-D]intel-iommu.c:752: iommu_page_fault:DMA Write: DEVICE 0:2.0 > addr 14404000 REASON 5 > > I have a similar fault error in my xm dmesg also but it doesn't affect > the ability of using VT-d on a DVB-S PCIe card I use in an HVM. > Other > than that, there's not much else I can offer in help. > -- > Daniel Kao > Übermind, Inc. > Seattle, WA, U.S.A. > > > daballiemo wrote: > > Guys, > > i really hope somebody can help me, i am getting quit desperate.. > > rgds > > > daballiemo wrote: > > > Hello, > > I have been working sometime now on getting a HVM accepting a PCI card > from the host. As was said in the VT-D wiki I bought an ASUS P5E VM DO > motherboard (rel 0803) which has the VT-D option in the bios. I want to > pass a Hauppauge PVR 500 card to a virtual machine running LinuxMCE. After > first trying XEN 3.2.1 which did not enable the "VT-D virtualisation" bit > in xm dmesg, i upgraded the system to run XEN 3.3 which ended up having > errors regarding "(XEN) [VT-D]iommu.c:775: iommu_page_fault: iommu->reg > = > ffff828bfff57000" in xm dmesg > > This happens both with and without pciback.hide in grub commandline. If I > use "pci [xx.xx.xx] in my HVM conf and boot the HVM the host crashes and I > have to hard reset the system. It will happen both for a PCI network card > as well as the capture card. > > Is it possible to overcome the iommu_page_fault error in 3.3.0? > If not and I have to go to xen-unstable can someone provide me with a link > how to build xen-unstable. I am keen to learn but only have about 2 yrs of > experience. > > Many thankx > > Han > > > > xm dmesg: > > \ \/ /___ _ __ |___ / |___ / / _ \ > \ // _ \ '_ \ |_ \ |_ \| | | | > / \ __/ | | | ___) | ___) | |_| | > /_/\_\___|_| |_| |____(_)____(_)___/ > > (XEN) Xen version 3.3.0 (buildd@buildd) (gcc version 4.3.2 (Ubuntu > 4.3.2-1ubuntu9) ) Mon Oct 6 18:11:58 UTC 2008 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: iommu=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 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009dc00 (usable) > (XEN) 000000000009dc00 - 00000000000a0000 (reserved) > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000cf250000 (usable) > (XEN) 00000000cf250000 - 00000000cf25e000 (ACPI data) > (XEN) 00000000cf25e000 - 00000000cf2e0000 (ACPI NVS) > (XEN) 00000000cf2e0000 - 00000000cf300000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000ffc00000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 000000012c000000 (usable) > (XEN) System RAM: 4017MB (4114356kB) > (XEN) ACPI: RSDP 000F9A80, 0024 (r2 ACPIAM) > (XEN) ACPI: XSDT CF250100, 006C (r1 A_M_I_ OEMXSDT 7000823 MSFT > 97) > (XEN) ACPI: FACP CF250290, 00F4 (r3 A_M_I_ OEMFACP 7000823 MSFT > 97) > (XEN) ACPI: DSDT CF2505C0, 843B (r1 A0869 A0869001 1 INTL > 20060113) > (XEN) ACPI: FACS CF25E000, 0040 > (XEN) ACPI: APIC CF250390, 006C (r1 A_M_I_ OEMAPIC 7000823 MSFT > 97) > (XEN) ACPI: MCFG CF250400, 003C (r1 A_M_I_ OEMMCFG 7000823 MSFT > 97) > (XEN) ACPI: OEMB CF25E040, 0081 (r1 A_M_I_ AMI_OEM 7000823 MSFT > 97) > (XEN) ACPI: HPET CF258A00, 0038 (r1 A_M_I_ OEMHPET 7000823 MSFT > 97) > (XEN) ACPI: GSCI CF25E0D0, 2024 (r1 A_M_I_ GMCHSCI 7000823 MSFT > 97) > (XEN) ACPI: iEIT CF260100, 00B0 (r1 A_M_I_ EITTABLE 7000823 MSFT > 97) > (XEN) ACPI: DMAR CF2601B0, 0168 (r1 AMI OEMDMAR 1 MSFT > 97) > (XEN) ACPI: TCPA CF258AE0, 0032 (r1 A_M_I_ TBLOEMID 1 MSFT > 97) > (XEN) Xen heap: 14MB (14600kB) > (XEN) Domain heap initialised > (XEN) Processor #0 6:15 APIC version 20 > (XEN) Processor #1 6:15 APIC version 20 > (XEN) Processor #2 6:15 APIC version 20 > (XEN) Processor #3 6:15 APIC version 20 > (XEN) IOAPIC[0]: apic_id 4, 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 2400.104 MHz processor. > (XEN) HVM: VMX enabled > (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz stepping 0b > (XEN) Booting processor 1/1 eip 8c000 > (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz stepping 0b > (XEN) Booting processor 2/2 eip 8c000 > (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz stepping 0b > (XEN) Booting processor 3/3 eip 8c000 > (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz stepping 0b > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) checking TSC synchronization across 4 CPUs: passed. > (XEN) Platform timer is 14.318MHz HPET > (XEN) Brought up 4 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 594fd7000 > REASON 5 iommu->reg = ffff828bfff57000 > (XEN) print_vtd_entries: iommu = ffff8300ce2fb980 bdf = 0:2:0 gmfn = > 594fd7 > (XEN) root_entry = ffff83012bdf1000 > (XEN) root_entry[0] = 1277ac001 > (XEN) context = ffff8301277ac000 > (XEN) context[10] = 101_12bdeb001 > (XEN) l3 = ffff83012bdeb000 > (XEN) l3_index = 16 > (XEN) l3[16] = 0 > (XEN) l3[16] not present > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> > 0xffffffff806d6948 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000120000000->0000000124000000 (956662 pages > to > be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80200000->ffffffff806d6948 > (XEN) Init. ramdisk: ffffffff806d7000->ffffffff81c42000 > (XEN) Phys-Mach map: ffffffff81c42000->ffffffff823ae7b0 > (XEN) Start info: ffffffff823af000->ffffffff823af4a4 > (XEN) Page tables: ffffffff823b0000->ffffffff823c7000 > (XEN) Boot stack: ffffffff823c7000->ffffffff823c8000 > (XEN) TOTAL: ffffffff80000000->ffffffff82800000 > (XEN) ENTRY ADDRESS: ffffffff80200000 > (XEN) Dom0 has maximum 4 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 112kB init memory. > (XEN) ioapic_guest_write: apic=0, pin=17, old_irq=-1, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=00010299, new_entry=0001a9c0 > (XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector 99 > (XEN) ioapic_guest_write: apic=0, pin=21, old_irq=-1, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=000102d9, new_entry=0001a9d0 > (XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector d9 > (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=-1, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=00010a38, new_entry=0001a9d8 > (XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector 38 > (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=-1, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=00010299, new_entry=0001a921 > (XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector 99 > (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=-1, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=00010ab9, new_entry=0001a929 > (XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector b9 > (XEN) ioapic_guest_write: apic=0, pin=20, old_irq=-1, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=00010299, new_entry=0001a931 > (XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector 99 > > lspci: > > 00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev > 02) > 00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express > Integrated Graphics Controller (rev 02) > 00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI > Controller (rev 02) > 00:03.2 IDE interface: Intel Corporation 82Q35 Express PT IDER Controller > (rev 02) > 00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT > Controller (rev 02) > 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network > Connection (rev 02) > 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #4 (rev 02) > 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #5 (rev 02) > 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #6 (rev 02) > 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI > Controller #2 (rev 02) > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio > Controller (rev 02) > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express > Port 1 (rev 02) > 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express > Port 5 (rev 02) > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #1 (rev 02) > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #2 (rev 02) > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #3 (rev 02) > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI > Controller #1 (rev 02) > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) > 00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface > Controller (rev 02) > 00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 > port SATA IDE Controller (rev 02) > 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller > (rev 02) > 00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA > IDE Controller (rev 02) > 00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 > Family) Thermal Subsystem (rev 02) > 01:00.0 IDE interface: JMicron Technologies, Inc. JMB368 IDE controller > 03:00.0 Multimedia video controller: Internext Compression Inc iTVC16 > (CX23416) MPEG-2 Encoder (rev 01) > 03:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 > Gigabit Ethernet (rev 10) > 03:02.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) > > > > > > > > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users > -- View this message in context: http://www.nabble.com/-VT-D-iommu.c%3A775%3A-iommu_page_fault%3A-iommu-%3Ereg-%3D-ffff828bfff57000-tp20902110p20942796.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |