Stefan Bauer
2008-Oct-28 10:09 UTC
[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@lists.xensource.com
http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-28 17:49 UTC
[Xen-devel] Re: ]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000
Sankaran, Rajesh schrieb:> The first step of course would be to make sure you have the latest bios for this platform.It''s the latest bios version from the vendor page. Version: 2RKT54A Release Date: 2008/09/12 Any other ideas? Regards -- stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ross Philipson
2008-Oct-28 19:22 UTC
RE: [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@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Tuesday, October 28, 2008 6:09 AM
To: xen-devel@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-28 19:41 UTC
Re: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000
Ross Philipson schrieb:> 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.Hi Ross, the error after trying to start the hvm guest by xm create win2k is: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroyDomain(5) [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) No device model [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) Releasing devices [2008-10-25 19:59:30 2460] ERROR (__init__:1072) Domain construction failed Traceback (most recent call last): File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 92, in create vm.start() File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 424, in start XendTask.log_progress(0, 30, self._constructDomain) File "//usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 2103, in _constructDomain raise VmError("fail to assign device(%x:%x.%x): maybe it has" VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. I also noticed that lspci did not show the graphiccard anymore after i use the boot option iommu in combination with vtd. Might be caused by that initial error. I have to admit that lspci did not show device 00:2.0. that looks strange to me. please see attached the output of lspci -vv Thanks in advance -- stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-28 20:21 UTC
Re: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg=ffff828bfff57000
Ross Philipson schrieb:> Just out of curiosity, your first email said this: > " Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64." > I am not sure I understand. This is clearly an Intel system as the > output indicates (and esp. since you are using VT-d)?It''s correct, the debian guys just called the 64bit port amd64 no matter if its intel or amd.> Could you easily try a newer version of Xen like 3.4? Lots of VT-d > related issues have been fixed in recent months.Not easily but i will give it a try. the unstable branch then? Regards -- stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-28 22:06 UTC
Re: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg=ffff828bfff57000
Ross Philipson schrieb:> Could you easily try a newer version of Xen like 3.4? Lots of VT-d > related issues have been fixed in recent months.Hi again, with xen3.4 the iommu errors seems to be gone, but a bug comes up right after booting: Oct 28 23:55:17 xen64 kernel: klogd 1.4.1#18, log source = /proc/kmsg started. Oct 28 23:55:17 xen64 kernel: Bootdata ok (command line is root=/dev/sda2 ro pciback.hide=(01:00.0)) Oct 28 23:55:17 xen64 kernel: Linux version 2.6.18.8-xen (root@xen64) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Oct 28 22:00:49 CET 2008 Oct 28 23:55:17 xen64 kernel: BIOS-provided physical RAM map: Oct 28 23:55:17 xen64 kernel: Xen: 0000000000000000 - 0000000020800000 (usable) Oct 28 23:55:17 xen64 kernel: DMI present. Oct 28 23:55:17 xen64 kernel: Intel MultiProcessor Specification v1.4 Oct 28 23:55:17 xen64 kernel: Virtual Wire compatibility mode. Oct 28 23:55:17 xen64 kernel: OEM ID: LENOVO Product ID: THINKCEN APIC at: 0xFEE00000 Oct 28 23:55:17 xen64 kernel: I/O APIC #2 Version 32 at 0xFEC00000. Oct 28 23:55:17 xen64 kernel: Setting APIC routing to xen Oct 28 23:55:17 xen64 kernel: Processors: 2 Oct 28 23:55:17 xen64 kernel: Allocating PCI resources starting at c2000000 (gap: c0000000:20000000) Oct 28 23:55:17 xen64 kernel: Built 1 zonelists. Total pages: 128567 Oct 28 23:55:17 xen64 kernel: Kernel command line: root=/dev/sda2 ro pciback.hide=(01:00.0) Oct 28 23:55:17 xen64 kernel: Initializing CPU#0 Oct 28 23:55:17 xen64 kernel: PID hash table entries: 2048 (order: 11, 16384 bytes) Oct 28 23:55:17 xen64 kernel: Xen reported: 2327.564 MHz processor. Oct 28 23:55:17 xen64 kernel: Console: colour VGA+ 80x25 Oct 28 23:55:17 xen64 kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Oct 28 23:55:17 xen64 kernel: Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Oct 28 23:55:17 xen64 kernel: Software IO TLB enabled: Oct 28 23:55:17 xen64 kernel: Aperture: 64 megabytes Oct 28 23:55:17 xen64 kernel: Kernel range: ffff8800018fd000 - ffff8800058fd000 Oct 28 23:55:17 xen64 kernel: Address size: 27 bits Oct 28 23:55:17 xen64 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Oct 28 23:55:17 xen64 kernel: Memory: 438820k/532480k available (1697k kernel code, 85328k reserved, 732k data, 136k init) Oct 28 23:55:17 xen64 kernel: Calibrating delay using timer specific routine.. 4656.77 BogoMIPS (lpj=23283855) Oct 28 23:55:17 xen64 kernel: Security Framework v1.0.0 initialized Oct 28 23:55:17 xen64 kernel: Capability LSM initialized Oct 28 23:55:17 xen64 kernel: Mount-cache hash table entries: 256 Oct 28 23:55:17 xen64 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Oct 28 23:55:17 xen64 kernel: CPU: L2 cache: 4096K Oct 28 23:55:17 xen64 kernel: CPU: Physical Processor ID: 0 Oct 28 23:55:17 xen64 kernel: CPU: Processor Core ID: 0 Oct 28 23:55:17 xen64 kernel: Freeing SMP alternatives: 24k freed Oct 28 23:55:17 xen64 kernel: GSI 16 sharing vector 0xA8 and IRQ 16 Oct 28 23:55:17 xen64 kernel: GSI 17 sharing vector 0xB0 and IRQ 17 Oct 28 23:55:17 xen64 kernel: GSI 18 sharing vector 0xB8 and IRQ 18 Oct 28 23:55:17 xen64 kernel: GSI 19 sharing vector 0xC0 and IRQ 19 Oct 28 23:55:17 xen64 kernel: GSI 20 sharing vector 0xC8 and IRQ 20 Oct 28 23:55:17 xen64 kernel: Brought up 2 CPUs Oct 28 23:55:17 xen64 kernel: Initializing CPU#1 Oct 28 23:55:17 xen64 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Oct 28 23:55:17 xen64 kernel: CPU: L2 cache: 4096K Oct 28 23:55:17 xen64 kernel: CPU: Physical Processor ID: 0 Oct 28 23:55:17 xen64 kernel: CPU: Processor Core ID: 1 Oct 28 23:55:17 xen64 kernel: migration_cost=12 Oct 28 23:55:17 xen64 kernel: Unpacking initramfs... done Oct 28 23:55:17 xen64 kernel: Freeing initrd memory: 5537k freed Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 16 Oct 28 23:55:17 xen64 kernel: PCI: Using configuration type 1 Oct 28 23:55:17 xen64 kernel: xen_mem: Initialising balloon driver. Oct 28 23:55:17 xen64 kernel: PCI: Probing PCI hardware Oct 28 23:55:17 xen64 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.2 Oct 28 23:55:17 xen64 kernel: PCI: Transparent bridge - 0000:00:1e.0 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:01.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:03.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:03.2[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:03.3[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:19.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.1[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.2[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.7[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1b.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.1[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.2[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.7[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1f.2[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1f.3[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1f.5[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:01:00.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:11:0c.0[A] -> IRQ 20 Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: pciback 0000:01:00.0: seizing device Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: PCI: Bridge: 0000:00:01.0 Oct 28 23:55:17 xen64 kernel: IO window: 2000-2fff Oct 28 23:55:17 xen64 kernel: MEM window: d0000000-d2ffffff Oct 28 23:55:17 xen64 kernel: PREFETCH window: c0000000-cfffffff Oct 28 23:55:17 xen64 kernel: PCI: Bridge: 0000:00:1e.0 Oct 28 23:55:17 xen64 kernel: IO window: disabled. Oct 28 23:55:17 xen64 kernel: MEM window: d3000000-d30fffff Oct 28 23:55:17 xen64 kernel: PREFETCH window: disabled. Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 2 Oct 28 23:55:17 xen64 kernel: IP route cache hash table entries: 16384 (order: 5, 131072 bytes) Oct 28 23:55:17 xen64 kernel: TCP established hash table entries: 65536 (order: 8, 1048576 bytes) Oct 28 23:55:17 xen64 kernel: TCP bind hash table entries: 32768 (order: 7, 524288 bytes) Oct 28 23:55:17 xen64 kernel: TCP: Hash tables configured (established 65536 bind 32768) Oct 28 23:55:17 xen64 kernel: TCP reno registered Oct 28 23:55:17 xen64 kernel: IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com> Oct 28 23:55:17 xen64 kernel: audit: initializing netlink socket (disabled) Oct 28 23:55:17 xen64 kernel: audit(1225234511.359:1): initialized Oct 28 23:55:17 xen64 kernel: Initializing Cryptographic API Oct 28 23:55:17 xen64 kernel: io scheduler noop registered Oct 28 23:55:17 xen64 kernel: io scheduler anticipatory registered Oct 28 23:55:17 xen64 kernel: io scheduler deadline registered Oct 28 23:55:17 xen64 kernel: io scheduler cfq registered (default) Oct 28 23:55:17 xen64 kernel: loop: loaded (max 8 devices) Oct 28 23:55:17 xen64 kernel: Xen virtual console successfully installed as xvc0 Oct 28 23:55:17 xen64 kernel: Event-channel device installed. Oct 28 23:55:17 xen64 kernel: netfront: Initialising virtual ethernet driver. Oct 28 23:55:17 xen64 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Oct 28 23:55:17 xen64 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Oct 28 23:55:17 xen64 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Oct 28 23:55:17 xen64 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Oct 28 23:55:17 xen64 kernel: mice: PS/2 mouse device common for all mice Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 1 Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 17 Oct 28 23:55:17 xen64 kernel: BIOS EDD facility v0.16 2004-Jun-25, 2 devices found Oct 28 23:55:17 xen64 kernel: Freeing unused kernel memory: 136k freed Oct 28 23:55:17 xen64 kernel: usbcore: registered new driver usbfs Oct 28 23:55:17 xen64 kernel: usbcore: registered new driver hub Oct 28 23:55:17 xen64 kernel: USB Universal Host Controller Interface driver v3.0 Oct 28 23:55:17 xen64 kernel: SCSI subsystem initialized Oct 28 23:55:17 xen64 kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] Oct 28 23:55:17 xen64 kernel: ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1C40 irq 14 Oct 28 23:55:17 xen64 kernel: scsi0 : ata_piix Oct 28 23:55:17 xen64 kernel: ata1.00: ATA-7, max UDMA/133, 156312576 sectors: LBA48 NCQ (depth 0/32) Oct 28 23:55:17 xen64 kernel: ata1.00: ata1: dev 0 multi count 16 Oct 28 23:55:17 xen64 kernel: ata1.00: configured for UDMA/133 Oct 28 23:55:17 xen64 kernel: Vendor: ATA Model: WDC WD800JD-08MS Rev: 10.0 Oct 28 23:55:17 xen64 kernel: Type: Direct-Access ANSI SCSI revision: 05 Oct 28 23:55:17 xen64 kernel: ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1C48 irq 15 Oct 28 23:55:17 xen64 kernel: scsi1 : ata_piix Oct 28 23:55:17 xen64 kernel: ata2.00: ATAPI, max UDMA/33 Oct 28 23:55:17 xen64 kernel: ata2.00: configured for UDMA/33 Oct 28 23:55:17 xen64 kernel: Vendor: TSSTcorp Model: DVD-ROM TS-H353B Rev: LE06 Oct 28 23:55:17 xen64 kernel: Type: CD-ROM ANSI SCSI revision: 05 Oct 28 23:55:17 xen64 kernel: ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] Oct 28 23:55:17 xen64 kernel: ata3: SATA max UDMA/133 cmd 0x1CB8 ctl 0x1CAE bmdma 0x1C60 irq 18 Oct 28 23:55:17 xen64 kernel: ata4: SATA max UDMA/133 cmd 0x1CB0 ctl 0x1CAA bmdma 0x1C68 irq 18 Oct 28 23:55:17 xen64 kernel: scsi2 : ata_piix Oct 28 23:55:17 xen64 kernel: ATA: abnormal status 0x7F on port 0x1CBF Oct 28 23:55:17 xen64 kernel: scsi3 : ata_piix Oct 28 23:55:17 xen64 kernel: ATA: abnormal status 0x7F on port 0x1CB7 Oct 28 23:55:17 xen64 kernel: SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB) Oct 28 23:55:17 xen64 kernel: sda: Write Protect is off Oct 28 23:55:17 xen64 kernel: SCSI device sda: drive cache: write back Oct 28 23:55:17 xen64 kernel: SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB) Oct 28 23:55:17 xen64 kernel: sda: Write Protect is off Oct 28 23:55:17 xen64 kernel: SCSI device sda: drive cache: write back Oct 28 23:55:17 xen64 kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 > Oct 28 23:55:17 xen64 kernel: sd 0:0:0:0: Attached scsi disk sda Oct 28 23:55:17 xen64 kernel: kjournald starting. Commit interval 5 seconds Oct 28 23:55:17 xen64 kernel: EXT3-fs: mounted filesystem with ordered data mode. Oct 28 23:55:17 xen64 kernel: sr0: scsi3-mmc drive: 125x/125x cd/rw xa/form2 cdda tray Oct 28 23:55:17 xen64 kernel: Uniform CD-ROM driver Revision: 3.20 Oct 28 23:55:17 xen64 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Oct 28 23:55:17 xen64 kernel: sr 1:0:0:0: Attached scsi generic sg1 type 5 Oct 28 23:55:17 xen64 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.4.1.12-NAPI Oct 28 23:55:17 xen64 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Oct 28 23:55:17 xen64 kernel: Adding 289160k swap on /dev/sda3. Priority:-1 extents:1 across:289160k Oct 28 23:55:17 xen64 kernel: EXT3 FS on sda2, internal journal Oct 28 23:55:17 xen64 kernel: kjournald starting. Commit interval 5 seconds Oct 28 23:55:17 xen64 kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended Oct 28 23:55:17 xen64 kernel: EXT3 FS on sda5, internal journal Oct 28 23:55:17 xen64 kernel: EXT3-fs: mounted filesystem with ordered data mode. Oct 28 23:55:20 xen64 kernel: Bridge firewalling registered Oct 28 23:55:20 xen64 kernel: suspend: event channel 14 Please see also the output of xm info and xm attached. Regards -- stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ross Philipson
2008-Oct-29 13:26 UTC
RE: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000
Yeah, I am not really sure about that. I assume you did a pull of a recent xen-unstable? Did the system successfully boot in spite of the bug reported (it seems to have)? Ross -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer Sent: Tuesday, October 28, 2008 6:07 PM To: xen-devel@lists.xensource.com Subject: Re: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000 Ross Philipson schrieb:> Could you easily try a newer version of Xen like 3.4? Lots of VT-d > related issues have been fixed in recent months.Hi again, with xen3.4 the iommu errors seems to be gone, but a bug comes up right after booting: Oct 28 23:55:17 xen64 kernel: klogd 1.4.1#18, log source = /proc/kmsg started. Oct 28 23:55:17 xen64 kernel: Bootdata ok (command line is root=/dev/sda2 ro pciback.hide=(01:00.0)) Oct 28 23:55:17 xen64 kernel: Linux version 2.6.18.8-xen (root@xen64) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Oct 28 22:00:49 CET 2008 Oct 28 23:55:17 xen64 kernel: BIOS-provided physical RAM map: Oct 28 23:55:17 xen64 kernel: Xen: 0000000000000000 - 0000000020800000 (usable) Oct 28 23:55:17 xen64 kernel: DMI present. Oct 28 23:55:17 xen64 kernel: Intel MultiProcessor Specification v1.4 Oct 28 23:55:17 xen64 kernel: Virtual Wire compatibility mode. Oct 28 23:55:17 xen64 kernel: OEM ID: LENOVO Product ID: THINKCEN APIC at: 0xFEE00000 Oct 28 23:55:17 xen64 kernel: I/O APIC #2 Version 32 at 0xFEC00000. Oct 28 23:55:17 xen64 kernel: Setting APIC routing to xen Oct 28 23:55:17 xen64 kernel: Processors: 2 Oct 28 23:55:17 xen64 kernel: Allocating PCI resources starting at c2000000 (gap: c0000000:20000000) Oct 28 23:55:17 xen64 kernel: Built 1 zonelists. Total pages: 128567 Oct 28 23:55:17 xen64 kernel: Kernel command line: root=/dev/sda2 ro pciback.hide=(01:00.0) Oct 28 23:55:17 xen64 kernel: Initializing CPU#0 Oct 28 23:55:17 xen64 kernel: PID hash table entries: 2048 (order: 11, 16384 bytes) Oct 28 23:55:17 xen64 kernel: Xen reported: 2327.564 MHz processor. Oct 28 23:55:17 xen64 kernel: Console: colour VGA+ 80x25 Oct 28 23:55:17 xen64 kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Oct 28 23:55:17 xen64 kernel: Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Oct 28 23:55:17 xen64 kernel: Software IO TLB enabled: Oct 28 23:55:17 xen64 kernel: Aperture: 64 megabytes Oct 28 23:55:17 xen64 kernel: Kernel range: ffff8800018fd000 - ffff8800058fd000 Oct 28 23:55:17 xen64 kernel: Address size: 27 bits Oct 28 23:55:17 xen64 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Oct 28 23:55:17 xen64 kernel: Memory: 438820k/532480k available (1697k kernel code, 85328k reserved, 732k data, 136k init) Oct 28 23:55:17 xen64 kernel: Calibrating delay using timer specific routine.. 4656.77 BogoMIPS (lpj=23283855) Oct 28 23:55:17 xen64 kernel: Security Framework v1.0.0 initialized Oct 28 23:55:17 xen64 kernel: Capability LSM initialized Oct 28 23:55:17 xen64 kernel: Mount-cache hash table entries: 256 Oct 28 23:55:17 xen64 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Oct 28 23:55:17 xen64 kernel: CPU: L2 cache: 4096K Oct 28 23:55:17 xen64 kernel: CPU: Physical Processor ID: 0 Oct 28 23:55:17 xen64 kernel: CPU: Processor Core ID: 0 Oct 28 23:55:17 xen64 kernel: Freeing SMP alternatives: 24k freed Oct 28 23:55:17 xen64 kernel: GSI 16 sharing vector 0xA8 and IRQ 16 Oct 28 23:55:17 xen64 kernel: GSI 17 sharing vector 0xB0 and IRQ 17 Oct 28 23:55:17 xen64 kernel: GSI 18 sharing vector 0xB8 and IRQ 18 Oct 28 23:55:17 xen64 kernel: GSI 19 sharing vector 0xC0 and IRQ 19 Oct 28 23:55:17 xen64 kernel: GSI 20 sharing vector 0xC8 and IRQ 20 Oct 28 23:55:17 xen64 kernel: Brought up 2 CPUs Oct 28 23:55:17 xen64 kernel: Initializing CPU#1 Oct 28 23:55:17 xen64 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Oct 28 23:55:17 xen64 kernel: CPU: L2 cache: 4096K Oct 28 23:55:17 xen64 kernel: CPU: Physical Processor ID: 0 Oct 28 23:55:17 xen64 kernel: CPU: Processor Core ID: 1 Oct 28 23:55:17 xen64 kernel: migration_cost=12 Oct 28 23:55:17 xen64 kernel: Unpacking initramfs... done Oct 28 23:55:17 xen64 kernel: Freeing initrd memory: 5537k freed Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 16 Oct 28 23:55:17 xen64 kernel: PCI: Using configuration type 1 Oct 28 23:55:17 xen64 kernel: xen_mem: Initialising balloon driver. Oct 28 23:55:17 xen64 kernel: PCI: Probing PCI hardware Oct 28 23:55:17 xen64 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.2 Oct 28 23:55:17 xen64 kernel: PCI: Transparent bridge - 0000:00:1e.0 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:01.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:03.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:03.2[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:03.3[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:19.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.1[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.2[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1a.7[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1b.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.1[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.2[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1d.7[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1f.2[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1f.3[B] -> IRQ 17 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:00:1f.5[C] -> IRQ 18 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:01:00.0[A] -> IRQ 16 Oct 28 23:55:17 xen64 kernel: PCI->APIC IRQ transform: 0000:11:0c.0[A] -> IRQ 20 Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: pciback 0000:01:00.0: seizing device Oct 28 23:55:17 xen64 kernel: BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wra pper() Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: Call Trace: Oct 28 23:55:17 xen64 kernel: [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a Oct 28 23:55:17 xen64 kernel: [<ffffffff803049e8>] driver_probe_device+0x52/0xa8 Oct 28 23:55:17 xen64 kernel: [<ffffffff80304b17>] __driver_attach+0x6d/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff80304aaa>] __driver_attach+0x0/0xaa Oct 28 23:55:17 xen64 kernel: [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e Oct 28 23:55:17 xen64 kernel: [<ffffffff80304047>] bus_add_driver+0x7e/0x130 Oct 28 23:55:17 xen64 kernel: [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d Oct 28 23:55:17 xen64 kernel: [<ffffffff80491d04>] pcistub_init+0xfb/0x1c9 Oct 28 23:55:17 xen64 kernel: [<ffffffff80207158>] init+0x13e/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae8c>] child_rip+0xa/0x12 Oct 28 23:55:17 xen64 kernel: [<ffffffff8020701a>] init+0x0/0x34c Oct 28 23:55:17 xen64 kernel: [<ffffffff8020ae82>] child_rip+0x0/0x12 Oct 28 23:55:17 xen64 kernel: Oct 28 23:55:17 xen64 kernel: PCI: Bridge: 0000:00:01.0 Oct 28 23:55:17 xen64 kernel: IO window: 2000-2fff Oct 28 23:55:17 xen64 kernel: MEM window: d0000000-d2ffffff Oct 28 23:55:17 xen64 kernel: PREFETCH window: c0000000-cfffffff Oct 28 23:55:17 xen64 kernel: PCI: Bridge: 0000:00:1e.0 Oct 28 23:55:17 xen64 kernel: IO window: disabled. Oct 28 23:55:17 xen64 kernel: MEM window: d3000000-d30fffff Oct 28 23:55:17 xen64 kernel: PREFETCH window: disabled. Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 2 Oct 28 23:55:17 xen64 kernel: IP route cache hash table entries: 16384 (order: 5, 131072 bytes) Oct 28 23:55:17 xen64 kernel: TCP established hash table entries: 65536 (order: 8, 1048576 bytes) Oct 28 23:55:17 xen64 kernel: TCP bind hash table entries: 32768 (order: 7, 524288 bytes) Oct 28 23:55:17 xen64 kernel: TCP: Hash tables configured (established 65536 bind 32768) Oct 28 23:55:17 xen64 kernel: TCP reno registered Oct 28 23:55:17 xen64 kernel: IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com> Oct 28 23:55:17 xen64 kernel: audit: initializing netlink socket (disabled) Oct 28 23:55:17 xen64 kernel: audit(1225234511.359:1): initialized Oct 28 23:55:17 xen64 kernel: Initializing Cryptographic API Oct 28 23:55:17 xen64 kernel: io scheduler noop registered Oct 28 23:55:17 xen64 kernel: io scheduler anticipatory registered Oct 28 23:55:17 xen64 kernel: io scheduler deadline registered Oct 28 23:55:17 xen64 kernel: io scheduler cfq registered (default) Oct 28 23:55:17 xen64 kernel: loop: loaded (max 8 devices) Oct 28 23:55:17 xen64 kernel: Xen virtual console successfully installed as xvc0 Oct 28 23:55:17 xen64 kernel: Event-channel device installed. Oct 28 23:55:17 xen64 kernel: netfront: Initialising virtual ethernet driver. Oct 28 23:55:17 xen64 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Oct 28 23:55:17 xen64 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Oct 28 23:55:17 xen64 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Oct 28 23:55:17 xen64 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Oct 28 23:55:17 xen64 kernel: mice: PS/2 mouse device common for all mice Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 1 Oct 28 23:55:17 xen64 kernel: NET: Registered protocol family 17 Oct 28 23:55:17 xen64 kernel: BIOS EDD facility v0.16 2004-Jun-25, 2 devices found Oct 28 23:55:17 xen64 kernel: Freeing unused kernel memory: 136k freed Oct 28 23:55:17 xen64 kernel: usbcore: registered new driver usbfs Oct 28 23:55:17 xen64 kernel: usbcore: registered new driver hub Oct 28 23:55:17 xen64 kernel: USB Universal Host Controller Interface driver v3.0 Oct 28 23:55:17 xen64 kernel: SCSI subsystem initialized Oct 28 23:55:17 xen64 kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] Oct 28 23:55:17 xen64 kernel: ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1C40 irq 14 Oct 28 23:55:17 xen64 kernel: scsi0 : ata_piix Oct 28 23:55:17 xen64 kernel: ata1.00: ATA-7, max UDMA/133, 156312576 sectors: LBA48 NCQ (depth 0/32) Oct 28 23:55:17 xen64 kernel: ata1.00: ata1: dev 0 multi count 16 Oct 28 23:55:17 xen64 kernel: ata1.00: configured for UDMA/133 Oct 28 23:55:17 xen64 kernel: Vendor: ATA Model: WDC WD800JD-08MS Rev: 10.0 Oct 28 23:55:17 xen64 kernel: Type: Direct-Access ANSI SCSI revision: 05 Oct 28 23:55:17 xen64 kernel: ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1C48 irq 15 Oct 28 23:55:17 xen64 kernel: scsi1 : ata_piix Oct 28 23:55:17 xen64 kernel: ata2.00: ATAPI, max UDMA/33 Oct 28 23:55:17 xen64 kernel: ata2.00: configured for UDMA/33 Oct 28 23:55:17 xen64 kernel: Vendor: TSSTcorp Model: DVD-ROM TS-H353B Rev: LE06 Oct 28 23:55:17 xen64 kernel: Type: CD-ROM ANSI SCSI revision: 05 Oct 28 23:55:17 xen64 kernel: ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] Oct 28 23:55:17 xen64 kernel: ata3: SATA max UDMA/133 cmd 0x1CB8 ctl 0x1CAE bmdma 0x1C60 irq 18 Oct 28 23:55:17 xen64 kernel: ata4: SATA max UDMA/133 cmd 0x1CB0 ctl 0x1CAA bmdma 0x1C68 irq 18 Oct 28 23:55:17 xen64 kernel: scsi2 : ata_piix Oct 28 23:55:17 xen64 kernel: ATA: abnormal status 0x7F on port 0x1CBF Oct 28 23:55:17 xen64 kernel: scsi3 : ata_piix Oct 28 23:55:17 xen64 kernel: ATA: abnormal status 0x7F on port 0x1CB7 Oct 28 23:55:17 xen64 kernel: SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB) Oct 28 23:55:17 xen64 kernel: sda: Write Protect is off Oct 28 23:55:17 xen64 kernel: SCSI device sda: drive cache: write back Oct 28 23:55:17 xen64 kernel: SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB) Oct 28 23:55:17 xen64 kernel: sda: Write Protect is off Oct 28 23:55:17 xen64 kernel: SCSI device sda: drive cache: write back Oct 28 23:55:17 xen64 kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6> Oct 28 23:55:17 xen64 kernel: sd 0:0:0:0: Attached scsi disk sda Oct28 23:55:17 xen64 kernel: kjournald starting. Commit interval 5 seconds Oct 28 23:55:17 xen64 kernel: EXT3-fs: mounted filesystem with ordered data mode. Oct 28 23:55:17 xen64 kernel: sr0: scsi3-mmc drive: 125x/125x cd/rw xa/form2 cdda tray Oct 28 23:55:17 xen64 kernel: Uniform CD-ROM driver Revision: 3.20 Oct 28 23:55:17 xen64 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Oct 28 23:55:17 xen64 kernel: sr 1:0:0:0: Attached scsi generic sg1 type 5 Oct 28 23:55:17 xen64 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.4.1.12-NAPI Oct 28 23:55:17 xen64 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Oct 28 23:55:17 xen64 kernel: Adding 289160k swap on /dev/sda3. Priority:-1 extents:1 across:289160k Oct 28 23:55:17 xen64 kernel: EXT3 FS on sda2, internal journal Oct 28 23:55:17 xen64 kernel: kjournald starting. Commit interval 5 seconds Oct 28 23:55:17 xen64 kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended Oct 28 23:55:17 xen64 kernel: EXT3 FS on sda5, internal journal Oct 28 23:55:17 xen64 kernel: EXT3-fs: mounted filesystem with ordered data mode. Oct 28 23:55:20 xen64 kernel: Bridge firewalling registered Oct 28 23:55:20 xen64 kernel: suspend: event channel 14 Please see also the output of xm info and xm attached. Regards -- stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-29 13:37 UTC
Re: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000
Ross Philipson schrieb:> Yeah, I am not really sure about that. I assume you did a pull of a > recent xen-unstable? Did the system successfully boot in spite of the > bug reported (it seems to have)?I took xen 3.4 thats xen-unstable.hg from yesterday evening. The system boots and the iommu error messages are gone. Network did not come up properly. It works fine without pci passthrough options. In the bios i have to select whether the onboard graphic is used as primary vga output or the pci-e one. If i define the onboard one then the pci-e card gets unavailable in xen, furthermore lspci did not show it anymore. if i set the pci-e card as primary, it comes up fine in xen, but if i hide that card which is required for passthrough, vga output becomes unavailable. vga output stops right after that line: Event-channel device installed. netfront: Initialising virtual ethernet driver. Regards -- Stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-29 14:07 UTC
Re: [Xen-devel] [VT-D]iommu.c:775:iommu_page_fault:iommu->reg=ffff828bfff57000
Ross Philipson schrieb:> I am afraid I may not have too many answers on this. I mainly responded > because I saw that you were having VT-d issues comparable to ones I had > seen in the recent past. A lot of those issues (but not all) were > actually bugs that got fixed over time in xen-unstable. That is why I > suggested trying the latest. Hopefully a xen guru on the dev list will > have some better ideas. Sorry I couldn''t be more helpful.Thanks anyway for your response. -- Stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-29 16:58 UTC
Re: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED]
Stefan Bauer schrieb:> 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: >Here is a short update on this problem: I found out, that the internal graphiccard and the PEG card can''t work beside each other. i add a pci card too and the bug message is gone. It seems that xen was trying during the boot process to hide a non existing device, which caused that problem. Thanks -- stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Kay, Allen M
2008-Oct-29 19:24 UTC
RE: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED]
> >I found out, that the internal graphiccard and the PEG card can''t work >beside each other. i add a pci card too and the bug message is gone. > >It seems that xen was trying during the boot process to hide a non >existing device, which caused that problem. >If possible, stick with PCIe devices. Conventional PCI device passthrough is more complicated as it requires pass through all PCI devices behind the same PCIe-to-PCI bridge. Allen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefan Bauer
2008-Oct-29 19:35 UTC
Re: [Xen-devel] [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED]
Kay, Allen M schrieb:> If possible, stick with PCIe devices. Conventional PCI device passthrough is more complicated as it requires pass through all PCI devices behind the same PCIe-to-PCI bridge.I do. That PCI device is just used for graphic output by dom0 and not passthroughed to any domU''s. Stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel