[VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000

All of lore.kernel.org
 help / color / mirror / Atom feed

* [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000
@ 2008-10-28 10:09 Stefan Bauer
       [not found] ` <80769D7B14936844A23C0C43D9FBCF0F21182262@orsmsx501.amr.corp.intel.com>
                   ` (2 more replies)
  0 siblings, 3 replies; 12+ messages in thread
From: Stefan Bauer @ 2008-10-28 10:09 UTC (permalink / raw)
  To: xen-devel

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

[parent not found: <80769D7B14936844A23C0C43D9FBCF0F21182262@orsmsx501.amr.corp.intel.com>]

* Re: ]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000
       [not found] ` <80769D7B14936844A23C0C43D9FBCF0F21182262@orsmsx501.amr.corp.intel.com>
@ 2008-10-28 17:49   ` Stefan Bauer
  0 siblings, 0 replies; 12+ messages in thread
From: Stefan Bauer @ 2008-10-28 17:49 UTC (permalink / raw)
  To: xen-devel

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* RE: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000
  2008-10-28 10:09 [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 Stefan Bauer
       [not found] ` <80769D7B14936844A23C0C43D9FBCF0F21182262@orsmsx501.amr.corp.intel.com>
@ 2008-10-28 19:22 ` Ross Philipson
  2008-10-28 19:41   ` Stefan Bauer
  2008-10-29 16:58 ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED] Stefan Bauer
  2 siblings, 1 reply; 12+ messages in thread
From: Ross Philipson @ 2008-10-28 19:22 UTC (permalink / raw)
  To: Stefan Bauer, xen-devel

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000
  2008-10-28 19:22 ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000 Ross Philipson
@ 2008-10-28 19:41   ` Stefan Bauer
       [not found]     ` <409D32C55C48D34DB5E31C8AB29EB15B071C6B27@FTLPEXCH05.citrite.net>
  0 siblings, 1 reply; 12+ messages in thread
From: Stefan Bauer @ 2008-10-28 19:41 UTC (permalink / raw)
  Cc: xen-devel

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

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


[-- Attachment #2: lspci --]
[-- Type: text/plain, Size: 15835 bytes --]

00:00.0 Host bridge: Intel Corporation Unknown device 29b0 (rev 02)
	Subsystem: Lenovo Unknown device 3037
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information

00:01.0 PCI bridge: Intel Corporation Unknown device 29b1 (rev 02) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 32 bytes
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: d0000000-d2ffffff
	Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
	Capabilities: [88] Subsystem: Lenovo Unknown device 3037
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Capabilities: [a0] Express Root Port (Slot+) IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 2
		Link: Latency L0s <256ns, L1 <4us
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x16
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise-
		Slot: Number 4096, PowerLimit 75.000000
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Off, PwrInd On, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-

00:03.0 Communication controller: Intel Corporation Unknown device 29b4 (rev 02)
	Subsystem: Lenovo Unknown device 3037
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at d3326000 (64-bit, non-prefetchable) [size=16]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [8c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000

00:03.2 IDE interface: Intel Corporation Unknown device 29b6 (rev 02) (prog-if 85 [Master SecO PriO])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 18
	Region 0: I/O ports at 1c80 [disabled] [size=8]
	Region 1: I/O ports at 1c74 [disabled] [size=4]
	Region 2: I/O ports at 1c78 [disabled] [size=8]
	Region 3: I/O ports at 1c70 [disabled] [size=4]
	Region 4: I/O ports at 1c20 [disabled] [size=16]
	Capabilities: [c8] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000

00:03.3 Serial controller: Intel Corporation Unknown device 29b7 (rev 02) (prog-if 02 [16550])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 0: I/O ports at 1c88 [size=8]
	Region 1: Memory at d3324000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [c8] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000

00:19.0 Ethernet controller: Intel Corporation Unknown device 10bd (rev 02)
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at d3300000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at d3325000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at 1820 [size=32]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [e0] #13 [0306]

00:1a.0 USB Controller: Intel Corporation Unknown device 2937 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 4: I/O ports at 1840 [size=32]
	Capabilities: [50] #13 [0306]

00:1a.1 USB Controller: Intel Corporation Unknown device 2938 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 4: I/O ports at 1860 [size=32]
	Capabilities: [50] #13 [0306]

00:1a.2 USB Controller: Intel Corporation Unknown device 2939 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 18
	Region 4: I/O ports at 1880 [size=32]
	Capabilities: [50] #13 [0306]

00:1a.7 USB Controller: Intel Corporation Unknown device 293c (rev 02) (prog-if 20 [EHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 18
	Region 0: Memory at d3326800 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port
	Capabilities: [98] #13 [0306]

00:1b.0 Audio device: Intel Corporation Unknown device 293e (rev 02)
	Subsystem: Lenovo Unknown device 3037
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at d3320000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express Unknown type IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
		Link: Latency L0s <64ns, L1 <1us
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed unknown, Width x0

00:1d.0 USB Controller: Intel Corporation Unknown device 2934 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 4: I/O ports at 18a0 [size=32]
	Capabilities: [50] #13 [0306]

00:1d.1 USB Controller: Intel Corporation Unknown device 2935 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 4: I/O ports at 18c0 [size=32]
	Capabilities: [50] #13 [0306]

00:1d.2 USB Controller: Intel Corporation Unknown device 2936 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 18
	Region 4: I/O ports at 18e0 [size=32]
	Capabilities: [50] #13 [0306]

00:1d.7 USB Controller: Intel Corporation Unknown device 293a (rev 02) (prog-if 20 [EHCI])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at d3326c00 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port
	Capabilities: [98] #13 [0306]

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=11, subordinate=11, sec-latency=32
	Memory behind bridge: d3000000-d30fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [50] Subsystem: Lenovo Unknown device 3037

00:1f.0 ISA bridge: Intel Corporation Unknown device 2914 (rev 02)
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information

00:1f.2 IDE interface: Intel Corporation Unknown device 2920 (rev 02) (prog-if 8a [Master SecP PriP])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 0: I/O ports at <unassigned>
	Region 1: I/O ports at <unassigned>
	Region 2: I/O ports at <unassigned>
	Region 3: I/O ports at <unassigned>
	Region 4: I/O ports at 1c40 [size=16]
	Region 5: I/O ports at 1c30 [size=16]
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [b0] #13 [0306]

00:1f.3 SMBus: Intel Corporation Unknown device 2930 (rev 02)
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin B routed to IRQ 17
	Region 0: Memory at d3327000 (64-bit, non-prefetchable) [disabled] [size=256]
	Region 4: I/O ports at 1c00 [size=32]

00:1f.5 IDE interface: Intel Corporation Unknown device 2926 (rev 02) (prog-if 85 [Master SecO PriO])
	Subsystem: Lenovo Unknown device 3037
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 18
	Region 0: I/O ports at 1cb8 [size=8]
	Region 1: I/O ports at 1cac [size=4]
	Region 2: I/O ports at 1cb0 [size=8]
	Region 3: I/O ports at 1ca8 [size=4]
	Region 4: I/O ports at 1c60 [size=16]
	Region 5: I/O ports at 1c50 [size=16]
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [b0] #13 [0306]

01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0402 (rev a1) (prog-if 00 [VGA])
	Subsystem: ASUSTeK Computer Inc. Unknown device 8243
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at d2000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at d0000000 (64-bit, non-prefetchable) [size=32M]
	Region 5: I/O ports at 2000 [size=128]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express Endpoint IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
		Device: Latency L0s <512ns, L1 <4us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
		Link: Latency L0s <512ns, L1 <4us
		Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x16

11:0c.0 Ethernet controller: Atheros Communications, Inc. AR5005G 802.11abg NIC (rev 01)
	Subsystem: Atheros Communications, Inc. Unknown device 2052
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 20
	Region 0: Memory at d3000000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-


[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

[parent not found: <409D32C55C48D34DB5E31C8AB29EB15B071C6B27@FTLPEXCH05.citrite.net>]

* Re: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg=ffff828bfff57000
       [not found]     ` <409D32C55C48D34DB5E31C8AB29EB15B071C6B27@FTLPEXCH05.citrite.net>
@ 2008-10-28 20:21       ` Stefan Bauer
  2008-10-28 22:06       ` Stefan Bauer
  1 sibling, 0 replies; 12+ messages in thread
From: Stefan Bauer @ 2008-10-28 20:21 UTC (permalink / raw)
  To: xen-devel

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg=ffff828bfff57000
       [not found]     ` <409D32C55C48D34DB5E31C8AB29EB15B071C6B27@FTLPEXCH05.citrite.net>
  2008-10-28 20:21       ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg=ffff828bfff57000 Stefan Bauer
@ 2008-10-28 22:06       ` Stefan Bauer
  2008-10-29 13:26         ` [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000 Ross Philipson
  1 sibling, 1 reply; 12+ messages in thread
From: Stefan Bauer @ 2008-10-28 22:06 UTC (permalink / raw)
  To: xen-devel

[-- Attachment #1: Type: text/plain, Size: 22252 bytes --]

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

[-- Attachment #2: xm-info --]
[-- Type: text/plain, Size: 1174 bytes --]

host                   : xen64
release                : 2.6.18.8-xen
version                : #1 SMP Tue Oct 28 22:00:49 CET 2008
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2327
hw_caps                : bfebfbff:20100800:00000000:00000140:0000e3fd:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 3044
free_memory            : 2469
node_to_cpu            : node0:0-1
node_to_memory         : node0:2469
xen_major              : 3
xen_minor              : 4
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb
cc_compiler            : gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
cc_compile_by          : root
cc_compile_domain      : 
cc_compile_date        : Tue Oct 28 23:12:59 CET 2008
xend_config_format     : 4

[-- Attachment #3: xm-dmesg --]
[-- Type: text/plain, Size: 5318 bytes --]

 __  __            _____ _  _                      _        _     _      
 \ \/ /___ _ __   |___ /| || |     _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \    |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) |__   _|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_) |_|     \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.4-unstable (root@) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) Tue Oct 28 23:12:59 CET 2008
(XEN) Latest ChangeSet: Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb
(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 2 MBR signatures
(XEN)  Found 2 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 (14704kB)
(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.582 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) *** 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->ffffffff80a98600
(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.

[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* RE: [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000
  2008-10-28 22:06       ` Stefan Bauer
@ 2008-10-29 13:26         ` Ross Philipson
  2008-10-29 13:37           ` Stefan Bauer
  0 siblings, 1 reply; 12+ messages in thread
From: Ross Philipson @ 2008-10-29 13:26 UTC (permalink / raw)
  To: Stefan Bauer, xen-devel

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 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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000
  2008-10-29 13:26         ` [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000 Ross Philipson
@ 2008-10-29 13:37           ` Stefan Bauer
       [not found]             ` <409D32C55C48D34DB5E31C8AB29EB15B071C6C9C@FTLPEXCH05.citrite.net>
  0 siblings, 1 reply; 12+ messages in thread
From: Stefan Bauer @ 2008-10-29 13:37 UTC (permalink / raw)
  Cc: xen-devel

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

[parent not found: <409D32C55C48D34DB5E31C8AB29EB15B071C6C9C@FTLPEXCH05.citrite.net>]

* Re: [VT-D]iommu.c:775:iommu_page_fault:iommu->reg=ffff828bfff57000
       [not found]             ` <409D32C55C48D34DB5E31C8AB29EB15B071C6C9C@FTLPEXCH05.citrite.net>
@ 2008-10-29 14:07               ` Stefan Bauer
  0 siblings, 0 replies; 12+ messages in thread
From: Stefan Bauer @ 2008-10-29 14:07 UTC (permalink / raw)
  To: xen-devel

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED]
  2008-10-28 10:09 [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 Stefan Bauer
       [not found] ` <80769D7B14936844A23C0C43D9FBCF0F21182262@orsmsx501.amr.corp.intel.com>
  2008-10-28 19:22 ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000 Ross Philipson
@ 2008-10-29 16:58 ` Stefan Bauer
  2008-10-29 19:24   ` Kay, Allen M
  2 siblings, 1 reply; 12+ messages in thread
From: Stefan Bauer @ 2008-10-29 16:58 UTC (permalink / raw)
  To: xen-devel

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* RE: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED]
  2008-10-29 16:58 ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED] Stefan Bauer
@ 2008-10-29 19:24   ` Kay, Allen M
  2008-10-29 19:35     ` Stefan Bauer
  0 siblings, 1 reply; 12+ messages in thread
From: Kay, Allen M @ 2008-10-29 19:24 UTC (permalink / raw)
  To: Stefan Bauer, xen-devel@lists.xensource.com

>
>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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED]
  2008-10-29 19:24   ` Kay, Allen M
@ 2008-10-29 19:35     ` Stefan Bauer
  0 siblings, 0 replies; 12+ messages in thread
From: Stefan Bauer @ 2008-10-29 19:35 UTC (permalink / raw)
  Cc: xen-devel@lists.xensource.com

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2008-10-29 19:35 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-28 10:09 [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 Stefan Bauer
     [not found] ` <80769D7B14936844A23C0C43D9FBCF0F21182262@orsmsx501.amr.corp.intel.com>
2008-10-28 17:49   ` ]iommu.c:775: " Stefan Bauer
2008-10-28 19:22 ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000 Ross Philipson
2008-10-28 19:41   ` Stefan Bauer
     [not found]     ` <409D32C55C48D34DB5E31C8AB29EB15B071C6B27@FTLPEXCH05.citrite.net>
2008-10-28 20:21       ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg=ffff828bfff57000 Stefan Bauer
2008-10-28 22:06       ` Stefan Bauer
2008-10-29 13:26         ` [VT-D]iommu.c:775: iommu_page_fault:iommu->reg=ffff828bfff57000 Ross Philipson
2008-10-29 13:37           ` Stefan Bauer
     [not found]             ` <409D32C55C48D34DB5E31C8AB29EB15B071C6C9C@FTLPEXCH05.citrite.net>
2008-10-29 14:07               ` [VT-D]iommu.c:775:iommu_page_fault:iommu->reg=ffff828bfff57000 Stefan Bauer
2008-10-29 16:58 ` [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 [SOLVED] Stefan Bauer
2008-10-29 19:24   ` Kay, Allen M
2008-10-29 19:35     ` Stefan Bauer

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.