No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

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

* No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
@ 2009-04-26 14:29 Tim Kaufmann
  2009-04-26 14:51 ` Tim Kaufmann
  2009-04-27 10:41 ` Christian Tramnitz
  0 siblings, 2 replies; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-26 14:29 UTC (permalink / raw)
  To: xen-devel

Hello,

my system: Intel DQ45CB with latest BIOS (0079 as of April 6th 2009)  
and VT-d enabled, Core 2 Quad Q9550 (E0), 8 GB RAM.

Tested with OpenSuse 11.1, packaged Kernel/Xen 3.3 and kernel opts  
"iommu=1", "iommu=1 msi=1", "dom0_mem=1024M iommu=1", "dom0_mem=1024M  
iommu=1 msi=1". System freezes on boot, last messages displayed are

(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled

Installed Debian Lenny and compiled 2.6.18.8 / Xen 3.4rc3 - same  
result as above.

I'd like to help debugging this, but I'd need someone to help me  
setting up Serial-over-LAN with one of my other computers (Ubuntu 8.04  
LTS, XP, Mac OS X 10.5).

Tim

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-26 14:29 No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB Tim Kaufmann
@ 2009-04-26 14:51 ` Tim Kaufmann
  2009-04-26 21:04   ` Ross Philipson
  2009-04-27 10:41 ` Christian Tramnitz
  1 sibling, 1 reply; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-26 14:51 UTC (permalink / raw)
  To: xen-devel

Am 26.04.2009 um 16:29 schrieb Tim Kaufmann:

> Installed Debian Lenny and compiled 2.6.18.8 / Xen 3.4rc3 - same  
> result as above.

May be it's interesting to know the last messages before this setup  
hangs:

(XEN) Brought up 4 CPUs
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation not supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) CPUIDLE: disabled due to no HPET. Force enable with "cpuidle".

The latter one disappears when I turn on HPET in BIOS.

Tim

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-26 14:51 ` Tim Kaufmann
@ 2009-04-26 21:04   ` Ross Philipson
  2009-04-26 23:35     ` Tim Kaufmann
  0 siblings, 1 reply; 28+ messages in thread
From: Ross Philipson @ 2009-04-26 21:04 UTC (permalink / raw)
  To: Tim Kaufmann, xen-devel

> my system: Intel DQ45CB with latest BIOS (0079 as of April 6th 2009) and VT-d enabled, Core 2 Quad Q9550 (E0), 8 GB RAM.

You said it is an Intel system; is the over all system an OEM system or a custom assembly? Whose BIOS is ver 0079?

The trace below is much like the tail end of the trace we saw when we encountered a problem like this. Can you try using "iommu_inclusive_mapping=1" on the xen boot command line? This works around a VT-d related BIOS issue.

Thanks
Ross

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tim Kaufmann
Sent: Sunday, April 26, 2009 10:51 AM
To: xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

Am 26.04.2009 um 16:29 schrieb Tim Kaufmann:

> Installed Debian Lenny and compiled 2.6.18.8 / Xen 3.4rc3 - same  
> result as above.

May be it's interesting to know the last messages before this setup  
hangs:

(XEN) Brought up 4 CPUs
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation not supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) CPUIDLE: disabled due to no HPET. Force enable with "cpuidle".

The latter one disappears when I turn on HPET in BIOS.

Tim

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

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-26 21:04   ` Ross Philipson
@ 2009-04-26 23:35     ` Tim Kaufmann
  2009-04-27 13:39       ` Ross Philipson
  0 siblings, 1 reply; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-26 23:35 UTC (permalink / raw)
  To: Ross Philipson; +Cc: xen-devel

> You said it is an Intel system; is the over all system an OEM system  
> or a custom assembly?

It's a custom assembly and the BIOS ver 0079 belongs to the mainboard.  
To be precise, here it is:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2933&DwnldID=17562&strOSs=All&OSFullName=Alle%20Betriebssysteme&lang=deu

> Can you try using "iommu_inclusive_mapping=1" on the xen boot  
> command line? This works around a VT-d related BIOS issue.

That didn't help. Now that I compiled Xen with debug options, the last  
lines before the boot process hangs look like this:

(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 1:1.0

This output is the same, no matter if I boot with iommu=1 only or with  
both iommu and iommu_inclusive_mapping enabled.

Attached, there's a full xm dmesg of the machine after booting it with  
IOMMU disabled.

Tim


  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ \047_ \    |_ \| || |_| | | |__| \047__/ __| |_ \ __|  
\047_ \| \047__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@xxxxxxxxxxxx) (gcc version 4.3.2  
(Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: iommu_inclusive_mapping=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 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd3c1000 (usable)
(XEN)  00000000bd3c1000 - 00000000bd403000 (ACPI NVS)
(XEN)  00000000bd403000 - 00000000bd526000 (reserved)
(XEN)  00000000bd526000 - 00000000bd53a000 (ACPI NVS)
(XEN)  00000000bd53a000 - 00000000bd63c000 (reserved)
(XEN)  00000000bd63c000 - 00000000bd63d000 (ACPI NVS)
(XEN)  00000000bd63d000 - 00000000bd642000 (reserved)
(XEN)  00000000bd642000 - 00000000bd64c000 (ACPI data)
(XEN)  00000000bd64c000 - 00000000bd667000 (ACPI NVS)
(XEN)  00000000bd667000 - 00000000bd686000 (reserved)
(XEN)  00000000bd686000 - 00000000bd68c000 (ACPI NVS)
(XEN)  00000000bd68c000 - 00000000bd800000 (usable)
(XEN)  00000000bd800000 - 00000000bdb00000 (reserved)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8084MB (8278860kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD64AE18, 0064 (r1 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: FACP BD649D98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD642018, 6818 (r1 INTEL  DQ45CB         4F INTL  
20051117)
(XEN) ACPI: FACS BD652F40, 0040
(XEN) ACPI: APIC BD649F18, 006C (r2 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: MCFG BD654E18, 003C (r1 INTEL  DQ45CB         4F  
MSFT       97)
(XEN) ACPI: ASF! BD653D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM     
F4240)
(XEN) ACPI: HPET BD654D98, 0038 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: SPCR BD654C98, 0050 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: TCPA BD654C18, 0032 (r2 INTEL  DQ45CB         4F MSFT   
1000013)
(XEN) ACPI: DMAR BD63CC18, 0120 (r1 INTEL  DQ45CB         4F  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd652f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.098 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) HPET: 8 timers in total, 4 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x287a00
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80488000 memsz=0x8a8e8
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80513000 memsz=0xc08
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80514000 memsz=0xcd81c
(XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff805e181c
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80206000
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: FEATURES = "writable_page_tables| 
writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb| 
supervisor_mode_kernel"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0xffffffff80000000
(XEN)     virt_offset      = 0x0
(XEN)     virt_kstart      = 0xffffffff80200000
(XEN)     virt_kend        = 0xffffffff805e181c
(XEN)     virt_entry       = 0xffffffff80200000
(XEN)     p2m_base         = 0xffffffffffffffff
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 ->  
0xffffffff805e181c
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000230000000->0000000234000000 (1994281  
pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff805e181c
(XEN)  Init. ramdisk: ffffffff805e2000->ffffffff817a4800
(XEN)  Phys-Mach map: ffffffff817a5000->ffffffff826fc148
(XEN)  Start info:    ffffffff826fd000->ffffffff826fd4b4
(XEN)  Page tables:   ffffffff826fe000->ffffffff82715000
(XEN)  Boot stack:    ffffffff82715000->ffffffff82716000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82800000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 ->  
0xffffffff80487a00
(XEN) elf_load_binary: phdr 1 at 0xffffffff80488000 ->  
0xffffffff805128e8
(XEN) elf_load_binary: phdr 2 at 0xffffffff80513000 ->  
0xffffffff80513c08
(XEN) elf_load_binary: phdr 3 at 0xffffffff80514000 ->  
0xffffffff8054eff8
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to  
switch input to Xen)
(XEN) Freed 128kB init memory.
(XEN) PCI add device 00:19.0
(XEN) PCI add device 00:03.2
(XEN) PCI add device 00:1f.5
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN) 	_PPC: 0
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=64,  
bit_offset=0, reserved=0, address=409
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=16,  
bit_offset=0, reserved=0, address=408
(XEN) 	_PSS: state_count=2
(XEN) 	State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN) 	State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN) 	_PSD: num_entries=5 rev=0 domain=1 coord_type=252  
num_processors=1
(XEN) 	_PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 0 initialization completed
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN) 	_PPC: 0
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=64,  
bit_offset=0, reserved=0, address=409
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=16,  
bit_offset=0, reserved=0, address=408
(XEN) 	_PSS: state_count=2
(XEN) 	State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN) 	State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN) 	_PSD: num_entries=5 rev=0 domain=2 coord_type=252  
num_processors=1
(XEN) 	_PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 1 initialization completed
(XEN) Set CPU acpi_id(3) cpuid(2) Px State info:
(XEN) 	_PPC: 0
(XEN) Set CPU acpi_id(3) cpuid(2) Px State info:
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=64,  
bit_offset=0, reserved=0, address=409
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=16,  
bit_offset=0, reserved=0, address=408
(XEN) 	_PSS: state_count=2
(XEN) 	State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN) 	State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN) 	_PSD: num_entries=5 rev=0 domain=3 coord_type=252  
num_processors=1
(XEN) 	_PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 2 initialization completed
(XEN) Set CPU acpi_id(4) cpuid(3) Px State info:
(XEN) 	_PPC: 0
(XEN) Set CPU acpi_id(4) cpuid(3) Px State info:
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=64,  
bit_offset=0, reserved=0, address=409
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=16,  
bit_offset=0, reserved=0, address=408
(XEN) 	_PSS: state_count=2
(XEN) 	State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN) 	State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN) 	_PSD: num_entries=5 rev=0 domain=4 coord_type=252  
num_processors=1
(XEN) 	_PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 3 initialization completed
(XEN) no cpu_id for acpi_id 5
(XEN) no cpu_id for acpi_id 6
(XEN) no cpu_id for acpi_id 7
(XEN) no cpu_id for acpi_id 8
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 01:01.0
(XEN) PCI add device 01:00.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1f.5
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 00:1b.0
(XEN) irq.c:640:d0 Cannot bind IRQ 2 to guest. In use by \047cascade 
\047.
(XEN) irq.c:640:d0 Cannot bind IRQ 2 to guest. In use by \047cascade 
\047.
(XEN) mtrr: type mismatch for c1fe0000,10000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c1fc0000,20000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c1f80000,40000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c1f00000,80000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c1e00000,100000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c1c00000,200000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c1800000,400000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c1000000,800000 old: write-back new:  
write-combining
(XEN) mtrr: type mismatch for c0000000,1000000 old: write-back new:  
write-combining

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-26 23:35     ` Tim Kaufmann
@ 2009-04-27 13:39       ` Ross Philipson
       [not found]         ` <F126C20F-9063-4FCC-BF8F-FE4CCDBCF1E5@taquiri.de>
  0 siblings, 1 reply; 28+ messages in thread
From: Ross Philipson @ 2009-04-27 13:39 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

Tim,

Could you send along a few things that might be helpful?

1. The rest of the xen output from your debug build leading up to the hang.
2. A listing of your PCI devices using lspci.
3. A dump of the ACPI DMAR using pmtools/acpidump - using something like this
    $ acpidump -t DMAR -b > dmar.bin

Thanks
Ross

-----Original Message-----
From: Tim Kaufmann [mailto:tk@taquiri.de]
Sent: Sunday, April 26, 2009 7:36 PM
To: Ross Philipson
Cc: xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

> You said it is an Intel system; is the over all system an OEM system
> or a custom assembly?

It's a custom assembly and the BIOS ver 0079 belongs to the mainboard.
To be precise, here it is:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2933&DwnldID=17562&strOSs=All&OSFullName=Alle%20Betriebssysteme&lang=deu

> Can you try using "iommu_inclusive_mapping=1" on the xen boot
> command line? This works around a VT-d related BIOS issue.

That didn't help. Now that I compiled Xen with debug options, the last
lines before the boot process hangs look like this:

(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 1:1.0

This output is the same, no matter if I boot with iommu=1 only or with
both iommu and iommu_inclusive_mapping enabled.

Attached, there's a full xm dmesg of the machine after booting it with
IOMMU disabled.

Tim


  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __
___
   \  // _ \ \047_ \    |_ \| || |_| | | |__| \047__/ __| |_ \ __|
\047_ \| \047__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@xxxxxxxxxxxx) (gcc version 4.3.2
(Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100
19575:dc5bd14a4675
(XEN) Command line: iommu_inclusive_mapping=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 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd3c1000 (usable)
(XEN)  00000000bd3c1000 - 00000000bd403000 (ACPI NVS)
(XEN)  00000000bd403000 - 00000000bd526000 (reserved)
(XEN)  00000000bd526000 - 00000000bd53a000 (ACPI NVS)
(XEN)  00000000bd53a000 - 00000000bd63c000 (reserved)
(XEN)  00000000bd63c000 - 00000000bd63d000 (ACPI NVS)
(XEN)  00000000bd63d000 - 00000000bd642000 (reserved)
(XEN)  00000000bd642000 - 00000000bd64c000 (ACPI data)
(XEN)  00000000bd64c000 - 00000000bd667000 (ACPI NVS)
(XEN)  00000000bd667000 - 00000000bd686000 (reserved)
(XEN)  00000000bd686000 - 00000000bd68c000 (ACPI NVS)
(XEN)  00000000bd68c000 - 00000000bd800000 (usable)
(XEN)  00000000bd800000 - 00000000bdb00000 (reserved)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8084MB (8278860kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD64AE18, 0064 (r1 INTEL  DQ45CB         4F MSFT
10013)
(XEN) ACPI: FACP BD649D98, 00F4 (r4  INTEL    A M I  6222004 MSFT
10013)
(XEN) ACPI: DSDT BD642018, 6818 (r1 INTEL  DQ45CB         4F INTL
20051117)
(XEN) ACPI: FACS BD652F40, 0040
(XEN) ACPI: APIC BD649F18, 006C (r2 INTEL  DQ45CB         4F MSFT
10013)
(XEN) ACPI: MCFG BD654E18, 003C (r1 INTEL  DQ45CB         4F
MSFT       97)
(XEN) ACPI: ASF! BD653D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM
F4240)
(XEN) ACPI: HPET BD654D98, 0038 (r1 INTEL  DQ45CB         4F
AMI.        3)
(XEN) ACPI: SPCR BD654C98, 0050 (r1 INTEL  DQ45CB         4F
AMI.        3)
(XEN) ACPI: TCPA BD654C18, 0032 (r2 INTEL  DQ45CB         4F MSFT
1000013)
(XEN) ACPI: DMAR BD63CC18, 0120 (r1 INTEL  DQ45CB         4F
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd652f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.098 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) HPET: 8 timers in total, 4 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x287a00
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80488000 memsz=0x8a8e8
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80513000 memsz=0xc08
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80514000 memsz=0xcd81c
(XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff805e181c
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80206000
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: FEATURES = "writable_page_tables|
writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|
supervisor_mode_kernel"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0xffffffff80000000
(XEN)     virt_offset      = 0x0
(XEN)     virt_kstart      = 0xffffffff80200000
(XEN)     virt_kend        = 0xffffffff805e181c
(XEN)     virt_entry       = 0xffffffff80200000
(XEN)     p2m_base         = 0xffffffffffffffff
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 ->
0xffffffff805e181c
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000230000000->0000000234000000 (1994281
pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff805e181c
(XEN)  Init. ramdisk: ffffffff805e2000->ffffffff817a4800
(XEN)  Phys-Mach map: ffffffff817a5000->ffffffff826fc148
(XEN)  Start info:    ffffffff826fd000->ffffffff826fd4b4
(XEN)  Page tables:   ffffffff826fe000->ffffffff82715000
(XEN)  Boot stack:    ffffffff82715000->ffffffff82716000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82800000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 ->
0xffffffff80487a00
(XEN) elf_load_binary: phdr 1 at 0xffffffff80488000 ->
0xffffffff805128e8
(XEN) elf_load_binary: phdr 2 at 0xffffffff80513000 ->
0xffffffff80513c08
(XEN) elf_load_binary: phdr 3 at 0xffffffff80514000 ->
0xffffffff8054eff8
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to
switch input to Xen)
(XEN) Freed 128kB init memory.
(XEN) PCI add device 00:19.0
(XEN) PCI add device 00:03.2
(XEN) PCI add device 00:1f.5
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN)   _PPC: 0
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=64,
bit_offset=0, reserved=0, address=409
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=16,
bit_offset=0, reserved=0, address=408
(XEN)   _PSS: state_count=2
(XEN)   State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN)   State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN)   _PSD: num_entries=5 rev=0 domain=1 coord_type=252
num_processors=1
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 0 initialization completed
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN)   _PPC: 0
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=64,
bit_offset=0, reserved=0, address=409
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=16,
bit_offset=0, reserved=0, address=408
(XEN)   _PSS: state_count=2
(XEN)   State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN)   State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN)   _PSD: num_entries=5 rev=0 domain=2 coord_type=252
num_processors=1
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 1 initialization completed
(XEN) Set CPU acpi_id(3) cpuid(2) Px State info:
(XEN)   _PPC: 0
(XEN) Set CPU acpi_id(3) cpuid(2) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=64,
bit_offset=0, reserved=0, address=409
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=16,
bit_offset=0, reserved=0, address=408
(XEN)   _PSS: state_count=2
(XEN)   State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN)   State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN)   _PSD: num_entries=5 rev=0 domain=3 coord_type=252
num_processors=1
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 2 initialization completed
(XEN) Set CPU acpi_id(4) cpuid(3) Px State info:
(XEN)   _PPC: 0
(XEN) Set CPU acpi_id(4) cpuid(3) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=64,
bit_offset=0, reserved=0, address=409
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=16,
bit_offset=0, reserved=0, address=408
(XEN)   _PSS: state_count=2
(XEN)   State0: 2830MHz 27000mW 10us 10us 0x4822 0x4822
(XEN)   State1: 1998MHz 13800mW 10us 10us 0x616 0x616
(XEN)   _PSD: num_entries=5 rev=0 domain=4 coord_type=252
num_processors=1
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 3 initialization completed
(XEN) no cpu_id for acpi_id 5
(XEN) no cpu_id for acpi_id 6
(XEN) no cpu_id for acpi_id 7
(XEN) no cpu_id for acpi_id 8
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 01:01.0
(XEN) PCI add device 01:00.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1f.5
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 00:1b.0
(XEN) irq.c:640:d0 Cannot bind IRQ 2 to guest. In use by \047cascade
\047.
(XEN) irq.c:640:d0 Cannot bind IRQ 2 to guest. In use by \047cascade
\047.
(XEN) mtrr: type mismatch for c1fe0000,10000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c1fc0000,20000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c1f80000,40000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c1f00000,80000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c1e00000,100000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c1c00000,200000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c1800000,400000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c1000000,800000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for c0000000,1000000 old: write-back new:
write-combining

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

[parent not found: <F126C20F-9063-4FCC-BF8F-FE4CCDBCF1E5@taquiri.de>]

[parent not found: <831D55AF5A11D64C9B4B43F59EEBF72035FCB540E5@FTLPMAILBOX02.citrite.net>]

[parent not found: <21F81074-ADE6-4913-A77E-4615F84E5CB9@taquiri.de>]

[parent not found: <831D55AF5A11D64C9B4B43F59EEBF72035FCB540F1@FTLPMAILBOX02.citrite.net>]

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
       [not found]               ` <831D55AF5A11D64C9B4B43F59EEBF72035FCB540F1@FTLPMAILBOX02.citrite.net>
@ 2009-04-27 16:48                 ` Tim Kaufmann
  2009-04-27 18:00                   ` Ross Philipson
  0 siblings, 1 reply; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-27 16:48 UTC (permalink / raw)
  To: Ross Philipson; +Cc: xen-devel

I sent the requested files to Ross, now we're working on getting the  
Serial-over-LAN (SOL) to work so I can capture the boot messages.

The board has two COM ports. One does not have a standard connector.  
It's only a couple of pins directly on the board, so we can't use this  
without getting a connector for it. I turned that one off in the BIOS.  
lspci still shows the "serial KT controller", so this must be the COM- 
Port created by AMT/SOL. The board's manual states, that the SOL-Port  
is Com4 by the way.

As the data is sent via Ethernet, the USB-to-Serial-Converter and the  
Nullmodem-Cable probably won't be useful. I downloaded the AMT-SDK  
from intel.com and successfully connected to the AMT-Stack on the Xen- 
PC. I can start a SOL-Console - now what? :-)

Tim

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 16:48                 ` Tim Kaufmann
@ 2009-04-27 18:00                   ` Ross Philipson
  2009-04-27 18:31                     ` Tim Kaufmann
  0 siblings, 1 reply; 28+ messages in thread
From: Ross Philipson @ 2009-04-27 18:00 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

So I haven't tried the AMT SOL stuff before but you may be able to setup the AMT commander/director tools (AMT Developer Toolkit) to get the SOL output. You will probably have to do some AMT provisioning to be able to connect the tools. Then you can setup the xen command line to do serial tracing - try it first with COM4. Also can you send a more verbose lspci trace (lspci -vv e.g.)?

Thanks
Ross

-----Original Message-----
From: Tim Kaufmann [mailto:tk@taquiri.de] 
Sent: Monday, April 27, 2009 12:48 PM
To: Ross Philipson
Cc: xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

I sent the requested files to Ross, now we're working on getting the  
Serial-over-LAN (SOL) to work so I can capture the boot messages.

The board has two COM ports. One does not have a standard connector.  
It's only a couple of pins directly on the board, so we can't use this  
without getting a connector for it. I turned that one off in the BIOS.  
lspci still shows the "serial KT controller", so this must be the COM- 
Port created by AMT/SOL. The board's manual states, that the SOL-Port  
is Com4 by the way.

As the data is sent via Ethernet, the USB-to-Serial-Converter and the  
Nullmodem-Cable probably won't be useful. I downloaded the AMT-SDK  
from intel.com and successfully connected to the AMT-Stack on the Xen- 
PC. I can start a SOL-Console - now what? :-)

Tim

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 18:00                   ` Ross Philipson
@ 2009-04-27 18:31                     ` Tim Kaufmann
  2009-04-27 18:39                       ` Ross Philipson
  0 siblings, 1 reply; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-27 18:31 UTC (permalink / raw)
  To: Ross Philipson; +Cc: xen-devel


> connect the tools.

Done.

> Then you can setup the xen command line to do serial tracing - try  
> it first with COM4.

A hint on how to *properly* set this up would be very welcome.

> Also can you send a more verbose lspci trace (lspci -vv e.g.)?

Attached.

Tim



automatix:~# lspci -vv
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM  
Controller (rev 03)
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information <?>

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset  
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at e220 [size=8]
	Capabilities: [90] Message Signalled Interrupts: Mask- 64bit-  
Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Capabilities: [d0] 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-

00:02.1 Display controller: Intel Corporation 4 Series Chipset  
Integrated Graphics Controller (rev 03)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Region 0: Memory at d0400000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [d0] 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-

00:03.0 Communication controller: Intel Corporation 4 Series Chipset  
HECI Controller (rev 03)
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx+
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d0627100 (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 4 Series Chipset PT IDER  
Controller (rev 03) (prog-if 85 [Master SecO PriO])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 10
	Region 0: I/O ports at e210 [size=8]
	Region 1: I/O ports at e200 [size=4]
	Region 2: I/O ports at e1f0 [size=8]
	Region 3: I/O ports at e1e0 [size=4]
	Region 4: I/O ports at e1d0 [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 4 Series Chipset Serial  
KT Controller (rev 03) (prog-if 02 [16550])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 3
	Region 0: I/O ports at e1c0 [size=8]
	Region 1: Memory at d0625000 (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 82567LM-3 Gigabit  
Network Connection (rev 02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 255
	Region 0: Memory at d0600000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at d0624000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at e100 [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: 00000000fee0100c  Data: 41c0
	Capabilities: [e0] Vendor Specific Information <?>
	Kernel driver in use: e1000e

00:1a.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #4  
(rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 17
	Region 4: I/O ports at e0e0 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1a.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #5  
(rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 18
	Region 4: I/O ports at e0c0 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1a.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #6  
(rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 4: I/O ports at e0a0 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1a.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller  
#2 (rev 02) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 0: Memory at d0626c00 (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: BAR=1 offset=00a0
	Capabilities: [98] Vendor Specific Information <?>
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd

00:1b.0 Audio device: Intel Corporation ICH10 HD Audio Controller (rev  
02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at d0620000 (64-bit, non-prefetchable) [disabled]  
[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 (v1) Root Complex Integrated Endpoint, MSI  
00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- RBE- FLReset+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0  
<64ns, L1 <1us
			ClockPM- Suprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive-  
BWMgmt- ABWMgmt-
	Kernel modules: snd-hda-intel

00:1d.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #1  
(rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 20
	Region 4: I/O ports at e080 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1d.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #2  
(rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 21
	Region 4: I/O ports at e060 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1d.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #3  
(rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 4: I/O ports at e040 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1d.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller  
#1 (rev 02) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 20
	Region 0: Memory at d0626800 (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: BAR=1 offset=00a0
	Capabilities: [98] Vendor Specific Information <?>
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2) (prog- 
if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: d0500000-d05fffff
	Prefetchable memory behind bridge: 00000000d0700000-00000000d07fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [50] Subsystem: Gammagraphx, Inc. Device 0000

00:1f.0 ISA bridge: Intel Corporation ICH10 LPC Interface Controller  
(rev 02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information <?>

00:1f.2 SATA controller: Intel Corporation ICH10 6 port SATA AHCI  
Controller (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 254
	Region 0: I/O ports at e1b0 [size=8]
	Region 1: I/O ports at e1a0 [size=4]
	Region 2: I/O ports at e190 [size=8]
	Region 3: I/O ports at e180 [size=4]
	Region 4: I/O ports at e020 [size=32]
	Region 5: Memory at d0626000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-  
Queue=0/3 Enable+
		Address: fee0100c  Data: 4139
	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: [a8] SATA HBA <?>
	Capabilities: [b0] Vendor Specific Information <?>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation ICH10 SMBus Controller (rev 02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 19
	Region 0: Memory at d0627000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at e000 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c-i801

00:1f.5 IDE interface: Intel Corporation ICH10 2 port SATA IDE  
Controller (rev 02) (prog-if 85 [Master SecO PriO])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 21
	Region 0: I/O ports at e170 [size=8]
	Region 1: I/O ports at e160 [size=4]
	Region 2: I/O ports at e150 [size=8]
	Region 3: I/O ports at e140 [size=4]
	Region 4: I/O ports at e130 [size=16]
	Region 5: I/O ports at e120 [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] Vendor Specific Information <?>
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix

01:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]  
(rev 78)
	Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC  
Management NIC
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (2500ns min, 2500ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: I/O ports at d000 [size=128]
	Region 1: Memory at d0521100 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at d0700000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot 
+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-
	Kernel driver in use: 3c59x
	Kernel modules: 3c59x

01:01.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) (prog-if 10  
[OHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (3000ns min, 6000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at d0520000 (32-bit, non-prefetchable) [size=4K]
	Region 1: Memory at d0521000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [44] 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+
	Kernel driver in use: ohci1394
	Kernel modules: ohci1394

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 18:31                     ` Tim Kaufmann
@ 2009-04-27 18:39                       ` Ross Philipson
  2009-04-27 19:01                         ` Pasi Kärkkäinen
  0 siblings, 1 reply; 28+ messages in thread
From: Ross Philipson @ 2009-04-27 18:39 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

So using com4, you will need something like this:

        xen.gz console=com4 com4=115200,8n1,0xe1c0,0

Note that 0xe1c0 is the IO port for the KT Controller below. Give that a shot. I am interested to see if this works since this would be a useful method of debugging.

Thanks
Ross

-----Original Message-----
From: Tim Kaufmann [mailto:tk@taquiri.de]
Sent: Monday, April 27, 2009 2:31 PM
To: Ross Philipson
Cc: xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB


> connect the tools.

Done.

> Then you can setup the xen command line to do serial tracing - try
> it first with COM4.

A hint on how to *properly* set this up would be very welcome.

> Also can you send a more verbose lspci trace (lspci -vv e.g.)?

Attached.

Tim



automatix:~# lspci -vv
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM
Controller (rev 03)
        Subsystem: Intel Corporation Device 1003
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort+ >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: [e0] Vendor Specific Information <?>

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at e220 [size=8]
        Capabilities: [90] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [d0] 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-

00:02.1 Display controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at d0400000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: [d0] 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-

00:03.0 Communication controller: Intel Corporation 4 Series Chipset
HECI Controller (rev 03)
        Subsystem: Intel Corporation Device 1003
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx+
        Latency: 0
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at d0627100 (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 4 Series Chipset PT IDER
Controller (rev 03) (prog-if 85 [Master SecO PriO])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin C routed to IRQ 10
        Region 0: I/O ports at e210 [size=8]
        Region 1: I/O ports at e200 [size=4]
        Region 2: I/O ports at e1f0 [size=8]
        Region 3: I/O ports at e1e0 [size=4]
        Region 4: I/O ports at e1d0 [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 4 Series Chipset Serial
KT Controller (rev 03) (prog-if 02 [16550])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 3
        Region 0: I/O ports at e1c0 [size=8]
        Region 1: Memory at d0625000 (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 82567LM-3 Gigabit
Network Connection (rev 02)
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 255
        Region 0: Memory at d0600000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at d0624000 (32-bit, non-prefetchable) [size=4K]
        Region 2: I/O ports at e100 [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: 00000000fee0100c  Data: 41c0
        Capabilities: [e0] Vendor Specific Information <?>
        Kernel driver in use: e1000e

00:1a.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #4
(rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 17
        Region 4: I/O ports at e0e0 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci-hcd

00:1a.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #5
(rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 18
        Region 4: I/O ports at e0c0 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci-hcd

00:1a.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #6
(rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin C routed to IRQ 19
        Region 4: I/O ports at e0a0 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci-hcd

00:1a.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller
#2 (rev 02) (prog-if 20 [EHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin C routed to IRQ 19
        Region 0: Memory at d0626c00 (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: BAR=1 offset=00a0
        Capabilities: [98] Vendor Specific Information <?>
        Kernel driver in use: ehci_hcd
        Kernel modules: ehci-hcd

00:1b.0 Audio device: Intel Corporation ICH10 HD Audio Controller (rev
02)
        Subsystem: Intel Corporation Device 1003
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at d0620000 (64-bit, non-prefetchable) [disabled]
[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 (v1) Root Complex Integrated Endpoint, MSI
00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
                        ExtTag- RBE- FLReset+
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
                LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0
<64ns, L1 <1us
                        ClockPM- Suprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive-
BWMgmt- ABWMgmt-
        Kernel modules: snd-hda-intel

00:1d.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #1
(rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 20
        Region 4: I/O ports at e080 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci-hcd

00:1d.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #2
(rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 21
        Region 4: I/O ports at e060 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci-hcd

00:1d.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #3
(rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin C routed to IRQ 19
        Region 4: I/O ports at e040 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci-hcd

00:1d.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller
#1 (rev 02) (prog-if 20 [EHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at d0626800 (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: BAR=1 offset=00a0
        Capabilities: [98] Vendor Specific Information <?>
        Kernel driver in use: ehci_hcd
        Kernel modules: ehci-hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2) (prog-
if 01 [Subtractive decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: d0500000-d05fffff
        Prefetchable memory behind bridge: 00000000d0700000-00000000d07fffff
        Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: [50] Subsystem: Gammagraphx, Inc. Device 0000

00:1f.0 ISA bridge: Intel Corporation ICH10 LPC Interface Controller
(rev 02)
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: [e0] Vendor Specific Information <?>

00:1f.2 SATA controller: Intel Corporation ICH10 6 port SATA AHCI
Controller (rev 02) (prog-if 01 [AHCI 1.0])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 254
        Region 0: I/O ports at e1b0 [size=8]
        Region 1: I/O ports at e1a0 [size=4]
        Region 2: I/O ports at e190 [size=8]
        Region 3: I/O ports at e180 [size=4]
        Region 4: I/O ports at e020 [size=32]
        Region 5: Memory at d0626000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/3 Enable+
                Address: fee0100c  Data: 4139
        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: [a8] SATA HBA <?>
        Capabilities: [b0] Vendor Specific Information <?>
        Kernel driver in use: ahci
        Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation ICH10 SMBus Controller (rev 02)
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin C routed to IRQ 19
        Region 0: Memory at d0627000 (64-bit, non-prefetchable) [size=256]
        Region 4: I/O ports at e000 [size=32]
        Kernel driver in use: i801_smbus
        Kernel modules: i2c-i801

00:1f.5 IDE interface: Intel Corporation ICH10 2 port SATA IDE
Controller (rev 02) (prog-if 85 [Master SecO PriO])
        Subsystem: Intel Corporation Device 1003
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 21
        Region 0: I/O ports at e170 [size=8]
        Region 1: I/O ports at e160 [size=4]
        Region 2: I/O ports at e150 [size=8]
        Region 3: I/O ports at e140 [size=4]
        Region 4: I/O ports at e130 [size=16]
        Region 5: I/O ports at e120 [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] Vendor Specific Information <?>
        Kernel driver in use: ata_piix
        Kernel modules: ata_piix

01:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
(rev 78)
        Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC
Management NIC
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32 (2500ns min, 2500ns max), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: I/O ports at d000 [size=128]
        Region 1: Memory at d0521100 (32-bit, non-prefetchable) [size=128]
        Expansion ROM at d0700000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-
        Kernel driver in use: 3c59x
        Kernel modules: 3c59x

01:01.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) (prog-if 10
[OHCI])
        Subsystem: Intel Corporation Device 1003
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32 (3000ns min, 6000ns max), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at d0520000 (32-bit, non-prefetchable) [size=4K]
        Region 1: Memory at d0521000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [44] 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+
        Kernel driver in use: ohci1394
        Kernel modules: ohci1394

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 18:39                       ` Ross Philipson
@ 2009-04-27 19:01                         ` Pasi Kärkkäinen
  2009-04-27 19:07                           ` Ross Philipson
  0 siblings, 1 reply; 28+ messages in thread
From: Pasi Kärkkäinen @ 2009-04-27 19:01 UTC (permalink / raw)
  To: Ross Philipson; +Cc: Tim Kaufmann, xen-devel

On Mon, Apr 27, 2009 at 02:39:40PM -0400, Ross Philipson wrote:
> So using com4, you will need something like this:
> 
>         xen.gz console=com4 com4=115200,8n1,0xe1c0,0
> 
> Note that 0xe1c0 is the IO port for the KT Controller below. Give that a shot. I am interested to see if this works since this would be a useful method of debugging.
> 

This is my DQ35JO configuration for AMT/SOL remote console (that server is NOT running Xen though):

grub.conf:

# Intel AMT serial-over-lan console
serial --port=0x3440 --speed=115200
terminal --timeout=10 console serial

kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=.. console=ttyS1,115200n8 console=tty0

0x3440 is the IOport for AMT serial port from lspci.
Linux detects DQ35JO AMT serial port as ttyS1.

Then I connect to the serial console from a Linux desktop using "gamt" tool.
Hopefully that helps.

-- Pasi

> Thanks
> Ross
> 
> -----Original Message-----
> From: Tim Kaufmann [mailto:tk@taquiri.de]
> Sent: Monday, April 27, 2009 2:31 PM
> To: Ross Philipson
> Cc: xen-devel
> Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
> 
> 
> > connect the tools.
> 
> Done.
> 
> > Then you can setup the xen command line to do serial tracing - try
> > it first with COM4.
> 
> A hint on how to *properly* set this up would be very welcome.
> 
> > Also can you send a more verbose lspci trace (lspci -vv e.g.)?
> 
> Attached.
> 
> Tim
> 

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 19:01                         ` Pasi Kärkkäinen
@ 2009-04-27 19:07                           ` Ross Philipson
  2009-04-27 21:15                             ` Tim Kaufmann
  0 siblings, 1 reply; 28+ messages in thread
From: Ross Philipson @ 2009-04-27 19:07 UTC (permalink / raw)
  To: Pasi Kärkkäinen; +Cc: Tim Kaufmann, xen-devel

Cool, thanks. So maybe xen will just see it as com1 - Tim, you can try that instead of com4 but you will still have to specify the IO port for xen as below.

Thanks
Ross

-----Original Message-----
From: Pasi Kärkkäinen [mailto:pasik@iki.fi] 
Sent: Monday, April 27, 2009 3:02 PM
To: Ross Philipson
Cc: Tim Kaufmann; xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

On Mon, Apr 27, 2009 at 02:39:40PM -0400, Ross Philipson wrote:
> So using com4, you will need something like this:
> 
>         xen.gz console=com4 com4=115200,8n1,0xe1c0,0
> 
> Note that 0xe1c0 is the IO port for the KT Controller below. Give that a shot. I am interested to see if this works since this would be a useful method of debugging.
> 

This is my DQ35JO configuration for AMT/SOL remote console (that server is NOT running Xen though):

grub.conf:

# Intel AMT serial-over-lan console
serial --port=0x3440 --speed=115200
terminal --timeout=10 console serial

kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=.. console=ttyS1,115200n8 console=tty0

0x3440 is the IOport for AMT serial port from lspci.
Linux detects DQ35JO AMT serial port as ttyS1.

Then I connect to the serial console from a Linux desktop using "gamt" tool.
Hopefully that helps.

-- Pasi

> Thanks
> Ross
> 
> -----Original Message-----
> From: Tim Kaufmann [mailto:tk@taquiri.de]
> Sent: Monday, April 27, 2009 2:31 PM
> To: Ross Philipson
> Cc: xen-devel
> Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
> 
> 
> > connect the tools.
> 
> Done.
> 
> > Then you can setup the xen command line to do serial tracing - try
> > it first with COM4.
> 
> A hint on how to *properly* set this up would be very welcome.
> 
> > Also can you send a more verbose lspci trace (lspci -vv e.g.)?
> 
> Attached.
> 
> Tim
> 

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 19:07                           ` Ross Philipson
@ 2009-04-27 21:15                             ` Tim Kaufmann
  2009-04-27 21:23                               ` Ross Philipson
  2009-04-28 17:56                               ` Ross Philipson
  0 siblings, 2 replies; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-27 21:15 UTC (permalink / raw)
  To: Ross Philipson; +Cc: xen-devel

Got SOL workin'.

Grub looks like this:

title           Xen 3.4.0-rc3-pre / Debian GNU/Linux, kernel 2.6.18.8- 
xen
root            (hd0,0)
kernel          /xen-3.4.0-rc3-pre.gz console=com1  
com1=115200,8n1,0xe1c0,0
module          /vmlinuz-2.6.18.8-xen root=/dev/mapper/raidvg-lv-- 
dom0--root ro console=tty0
module          /initrd.img-2.6.18.8-xen

I'm using amtterm on the client machine. It's in Debian testing  
currently, but can easily be downloaded and installed via dpkg -i in  
Ubuntu 8.04 LTS.

I connected to AMT with

amtterm -u admin -p supersecretpassword 10.11.1.31

As soon as I rebooted the AMT computer the client was receiving data.

Attached is the output of booting with iommu=1. For reasons unknown,  
the lines I quoted as an example a couple of mails ago aren't in there.

Tim

Some tags for Google: Xen SOL Serial over LAN Intel AMT Console DQ45CB

root@obelix:~# amtterm -u admin -p ****** 10.11.1.31
amtterm: NONE -> CONNECT (connection to host)
ipv4 10.11.1.31 [10.11.1.31] 16994 open
amtterm: CONNECT -> INIT (redirection initialization)
amtterm: INIT -> AUTH (session authentication)
amtterm: AUTH -> INIT_SOL (serial-over-lan initialization)
amtterm: INIT_SOL -> RUN_SOL (serial-over-lan active)
serial-over-lan redirection ok
connected now, use ^] to escape
  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6c1000 (usable)
(XEN)  00000000bd6c1000 - 00000000bd703000 (ACPI NVS)
(XEN)  00000000bd703000 - 00000000bd826000 (reserved)
(XEN)  00000000bd826000 - 00000000bd83a000 (ACPI NVS)
(XEN)  00000000bd83a000 - 00000000bd93c000 (reserved)
(XEN)  00000000bd93c000 - 00000000bd93d000 (ACPI NVS)
(XEN)  00000000bd93d000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd94c000 (ACPI data)
(XEN)  00000000bd94c000 - 00000000bd967000 (ACPI NVS)
(XEN)  00000000bd967000 - 00000000bd986000 (reserved)
(XEN)  00000000bd986000 - 00000000bd98c000 (ACPI NVS)
(XEN)  00000000bd98c000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8281932kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94AE18, 005C (r1 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: FACP BD949D98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD942018, 6818 (r1 INTEL  DQ45CB         4F INTL  
20051117)
(XEN) ACPI: FACS BD952F40, 0040
(XEN) ACPI: APIC BD949F18, 006C (r2 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: MCFG BD954E18, 003C (r1 INTEL  DQ45CB         4F  
MSFT       97)
(XEN) ACPI: ASF! BD953D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM     
F4240)
(XEN) ACPI: SPCR BD954D18, 0050 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: TCPA BD954C98, 0032 (r2 INTEL  DQ45CB         4F MSFT   
1000013)
(XEN) ACPI: DMAR BD93CC18, 0120 (r1 INTEL  DQ45CB         4F  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd952f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.099 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 21:15                             ` Tim Kaufmann
@ 2009-04-27 21:23                               ` Ross Philipson
  2009-04-28 17:56                               ` Ross Philipson
  1 sibling, 0 replies; 28+ messages in thread
From: Ross Philipson @ 2009-04-27 21:23 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

That is cool that SOL worked easily. I just found that Fedora had the AMT sol client gamt that was mentioned earlier. I will have to try it out.

I will check some of the stuff out that you sent. One thing that jumped right out:

(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  

That looks like an invalid RMRR value so there are probably some issues with this particular BIOS version. Though the iommu_inclusive_mapping=1 should have gotten you by that issue if it was causing the hang so there are probably other problems.

Thanks
Ross

-----Original Message-----
From: Tim Kaufmann [mailto:tk@taquiri.de] 
Sent: Monday, April 27, 2009 5:16 PM
To: Ross Philipson
Cc: Pasi Kärkkäinen; xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

Got SOL workin'.

Grub looks like this:

title           Xen 3.4.0-rc3-pre / Debian GNU/Linux, kernel 2.6.18.8- 
xen
root            (hd0,0)
kernel          /xen-3.4.0-rc3-pre.gz console=com1  
com1=115200,8n1,0xe1c0,0
module          /vmlinuz-2.6.18.8-xen root=/dev/mapper/raidvg-lv-- 
dom0--root ro console=tty0
module          /initrd.img-2.6.18.8-xen

I'm using amtterm on the client machine. It's in Debian testing  
currently, but can easily be downloaded and installed via dpkg -i in  
Ubuntu 8.04 LTS.

I connected to AMT with

amtterm -u admin -p supersecretpassword 10.11.1.31

As soon as I rebooted the AMT computer the client was receiving data.

Attached is the output of booting with iommu=1. For reasons unknown,  
the lines I quoted as an example a couple of mails ago aren't in there.

Tim

Some tags for Google: Xen SOL Serial over LAN Intel AMT Console DQ45CB

root@obelix:~# amtterm -u admin -p ****** 10.11.1.31
amtterm: NONE -> CONNECT (connection to host)
ipv4 10.11.1.31 [10.11.1.31] 16994 open
amtterm: CONNECT -> INIT (redirection initialization)
amtterm: INIT -> AUTH (session authentication)
amtterm: AUTH -> INIT_SOL (serial-over-lan initialization)
amtterm: INIT_SOL -> RUN_SOL (serial-over-lan active)
serial-over-lan redirection ok
connected now, use ^] to escape
  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6c1000 (usable)
(XEN)  00000000bd6c1000 - 00000000bd703000 (ACPI NVS)
(XEN)  00000000bd703000 - 00000000bd826000 (reserved)
(XEN)  00000000bd826000 - 00000000bd83a000 (ACPI NVS)
(XEN)  00000000bd83a000 - 00000000bd93c000 (reserved)
(XEN)  00000000bd93c000 - 00000000bd93d000 (ACPI NVS)
(XEN)  00000000bd93d000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd94c000 (ACPI data)
(XEN)  00000000bd94c000 - 00000000bd967000 (ACPI NVS)
(XEN)  00000000bd967000 - 00000000bd986000 (reserved)
(XEN)  00000000bd986000 - 00000000bd98c000 (ACPI NVS)
(XEN)  00000000bd98c000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8281932kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94AE18, 005C (r1 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: FACP BD949D98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD942018, 6818 (r1 INTEL  DQ45CB         4F INTL  
20051117)
(XEN) ACPI: FACS BD952F40, 0040
(XEN) ACPI: APIC BD949F18, 006C (r2 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: MCFG BD954E18, 003C (r1 INTEL  DQ45CB         4F  
MSFT       97)
(XEN) ACPI: ASF! BD953D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM     
F4240)
(XEN) ACPI: SPCR BD954D18, 0050 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: TCPA BD954C98, 0032 (r2 INTEL  DQ45CB         4F MSFT   
1000013)
(XEN) ACPI: DMAR BD93CC18, 0120 (r1 INTEL  DQ45CB         4F  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd952f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.099 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 21:15                             ` Tim Kaufmann
  2009-04-27 21:23                               ` Ross Philipson
@ 2009-04-28 17:56                               ` Ross Philipson
  2009-04-29 23:47                                 ` Tim Kaufmann
  1 sibling, 1 reply; 28+ messages in thread
From: Ross Philipson @ 2009-04-28 17:56 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

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

Attached is a textual version of your DMAR and some notes. In notes.txt at the bottom I noted that both RMRRs seem to have some issues but the iommu_inclusive_mapping=1 should have handled them. The rest of the DMAR looks OK to me. There are the DRHDs that I would expect to see for AUDIO, GFX, AMT/ME, and the INCLUDE_ALL. 

So from what I see and what is in the logs, I am not sure. You said the BIOS you have is the latest - did you check with Intel to see if there are any known issues?

Thanks
Ross

-----Original Message-----
From: Tim Kaufmann [mailto:tk@taquiri.de] 
Sent: Monday, April 27, 2009 5:16 PM
To: Ross Philipson
Cc: Pasi Kärkkäinen; xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

Got SOL workin'.

Grub looks like this:

title           Xen 3.4.0-rc3-pre / Debian GNU/Linux, kernel 2.6.18.8- 
xen
root            (hd0,0)
kernel          /xen-3.4.0-rc3-pre.gz console=com1  
com1=115200,8n1,0xe1c0,0
module          /vmlinuz-2.6.18.8-xen root=/dev/mapper/raidvg-lv-- 
dom0--root ro console=tty0
module          /initrd.img-2.6.18.8-xen

I'm using amtterm on the client machine. It's in Debian testing  
currently, but can easily be downloaded and installed via dpkg -i in  
Ubuntu 8.04 LTS.

I connected to AMT with

amtterm -u admin -p supersecretpassword 10.11.1.31

As soon as I rebooted the AMT computer the client was receiving data.

Attached is the output of booting with iommu=1. For reasons unknown,  
the lines I quoted as an example a couple of mails ago aren't in there.

Tim

Some tags for Google: Xen SOL Serial over LAN Intel AMT Console DQ45CB

root@obelix:~# amtterm -u admin -p ****** 10.11.1.31
amtterm: NONE -> CONNECT (connection to host)
ipv4 10.11.1.31 [10.11.1.31] 16994 open
amtterm: CONNECT -> INIT (redirection initialization)
amtterm: INIT -> AUTH (session authentication)
amtterm: AUTH -> INIT_SOL (serial-over-lan initialization)
amtterm: INIT_SOL -> RUN_SOL (serial-over-lan active)
serial-over-lan redirection ok
connected now, use ^] to escape
  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6c1000 (usable)
(XEN)  00000000bd6c1000 - 00000000bd703000 (ACPI NVS)
(XEN)  00000000bd703000 - 00000000bd826000 (reserved)
(XEN)  00000000bd826000 - 00000000bd83a000 (ACPI NVS)
(XEN)  00000000bd83a000 - 00000000bd93c000 (reserved)
(XEN)  00000000bd93c000 - 00000000bd93d000 (ACPI NVS)
(XEN)  00000000bd93d000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd94c000 (ACPI data)
(XEN)  00000000bd94c000 - 00000000bd967000 (ACPI NVS)
(XEN)  00000000bd967000 - 00000000bd986000 (reserved)
(XEN)  00000000bd986000 - 00000000bd98c000 (ACPI NVS)
(XEN)  00000000bd98c000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8281932kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94AE18, 005C (r1 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: FACP BD949D98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD942018, 6818 (r1 INTEL  DQ45CB         4F INTL  
20051117)
(XEN) ACPI: FACS BD952F40, 0040
(XEN) ACPI: APIC BD949F18, 006C (r2 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: MCFG BD954E18, 003C (r1 INTEL  DQ45CB         4F  
MSFT       97)
(XEN) ACPI: ASF! BD953D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM     
F4240)
(XEN) ACPI: SPCR BD954D18, 0050 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: TCPA BD954C98, 0032 (r2 INTEL  DQ45CB         4F MSFT   
1000013)
(XEN) ACPI: DMAR BD93CC18, 0120 (r1 INTEL  DQ45CB         4F  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd952f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.099 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer


[-- Attachment #2: dmar.txt --]
[-- Type: text/plain, Size: 6798 bytes --]

DMAR dump utility - reading input file DMAR: ../dmar.bin size: 288
DMA Remapping Reporting Structure
==================================================
Signature:        DMAR
Length:           0x00000120
Revision:         0x01
Checksum:         0xdd
OEMID:            INTEL 
OEM Table ID:     DQ45CB  
OEM Revision:     0x0000004f
Creator ID:       INTL
Creator Revision: 0x00000001
HAW:              0x23
Flags:            0x00
Reserved[10]: 00 00 00 00 00 00 00 00 00 00

Remapping Structures...

DMA Remapping Hardware Unit Definition (DRHD) Structure #1
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0018
Flags:          0x00  -- INCLUDE_ALL = no
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed90000
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1b Function: 0x00

DMA Remapping Hardware Unit Definition (DRHD) Structure #2
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0020
Flags:          0x00  -- INCLUDE_ALL = no
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed91000
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x02 Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x02 Function: 0x01

DMA Remapping Hardware Unit Definition (DRHD) Structure #3
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0028
Flags:          0x00  -- INCLUDE_ALL = no
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed92000
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x02
    Device Scope Structure #3
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x03

DMA Remapping Hardware Unit Definition (DRHD) Structure #4
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0010
Flags:          0x01  -- INCLUDE_ALL = yes
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed93000

Reserved Memory Region Reporting (RMRR) Structure #1
Type:           0x0001 (ACPI_DMAR_RMRR)
Length:         0x0058
Reserved:       0x0000
Segment Number: 0x0000
Base Address:   0xbd626000
End Address:    0xbd639fff
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x01
    Device Scope Structure #3
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x02
    Device Scope Structure #4
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x07
    Device Scope Structure #5
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x00
    Device Scope Structure #6
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x01
    Device Scope Structure #7
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x02
    Device Scope Structure #8
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x07

Reserved Memory Region Reporting (RMRR) Structure #2
Type:           0x0001 (ACPI_DMAR_RMRR)
Length:         0x0028
Reserved:       0x0000
Segment Number: 0x0000
Base Address:   0xbdc00000
End Address:    0xffffffffbfffffff
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x02 Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x02 Function: 0x01

==================================================
End DMAR

[-- Attachment #3: lspci.txt --]
[-- Type: text/plain, Size: 19312 bytes --]

00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03)
00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller (rev 03)
00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller (rev 03)
00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #5 (rev 02)
00:1a.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #6 (rev 02)
00:1a.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation ICH10 HD Audio Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2)
00:1f.0 ISA bridge: Intel Corporation ICH10 LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation ICH10 6 port SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation ICH10 SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation ICH10 2 port SATA IDE Controller (rev 02)
01:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
01:01.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)

automatix:~# lspci -vv
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information <?>

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at e220 [size=8]
	Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Capabilities: [d0] 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-

00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Region 0: Memory at d0400000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [d0] 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-

00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03)
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx+
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d0627100 (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 4 Series Chipset PT IDER Controller (rev 03) (prog-if 85 [Master SecO PriO])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 10
	Region 0: I/O ports at e210 [size=8]
	Region 1: I/O ports at e200 [size=4]
	Region 2: I/O ports at e1f0 [size=8]
	Region 3: I/O ports at e1e0 [size=4]
	Region 4: I/O ports at e1d0 [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 4 Series Chipset Serial KT Controller (rev 03) (prog-if 02 [16550])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 3
	Region 0: I/O ports at e1c0 [size=8]
	Region 1: Memory at d0625000 (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 82567LM-3 Gigabit Network Connection (rev 02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 255
	Region 0: Memory at d0600000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at d0624000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at e100 [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: 00000000fee0100c  Data: 41c0
	Capabilities: [e0] Vendor Specific Information <?>
	Kernel driver in use: e1000e

00:1a.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 17
	Region 4: I/O ports at e0e0 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1a.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #5 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 18
	Region 4: I/O ports at e0c0 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1a.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #6 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 4: I/O ports at e0a0 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1a.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller
#2 (rev 02) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 0: Memory at d0626c00 (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: BAR=1 offset=00a0
	Capabilities: [98] Vendor Specific Information <?>
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd

00:1b.0 Audio device: Intel Corporation ICH10 HD Audio Controller (rev
02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at d0620000 (64-bit, non-prefetchable) [disabled] [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 (v1) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- RBE- FLReset+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0  
<64ns, L1 <1us
			ClockPM- Suprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive-  
BWMgmt- ABWMgmt-
	Kernel modules: snd-hda-intel

00:1d.0 USB Controller: Intel Corporation ICH10 USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 20
	Region 4: I/O ports at e080 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1d.1 USB Controller: Intel Corporation ICH10 USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 21
	Region 4: I/O ports at e060 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1d.2 USB Controller: Intel Corporation ICH10 USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 4: I/O ports at e040 [size=32]
	Capabilities: [50] Vendor Specific Information <?>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd

00:1d.7 USB Controller: Intel Corporation ICH10 USB2 EHCI Controller
#1 (rev 02) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 20
	Region 0: Memory at d0626800 (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: BAR=1 offset=00a0
	Capabilities: [98] Vendor Specific Information <?>
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2) (prog- if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: d0500000-d05fffff
	Prefetchable memory behind bridge: 00000000d0700000-00000000d07fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [50] Subsystem: Gammagraphx, Inc. Device 0000

00:1f.0 ISA bridge: Intel Corporation ICH10 LPC Interface Controller (rev 02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information <?>

00:1f.2 SATA controller: Intel Corporation ICH10 6 port SATA AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 254
	Region 0: I/O ports at e1b0 [size=8]
	Region 1: I/O ports at e1a0 [size=4]
	Region 2: I/O ports at e190 [size=8]
	Region 3: I/O ports at e180 [size=4]
	Region 4: I/O ports at e020 [size=32]
	Region 5: Memory at d0626000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/3 Enable+
		Address: fee0100c  Data: 4139
	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: [a8] SATA HBA <?>
	Capabilities: [b0] Vendor Specific Information <?>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation ICH10 SMBus Controller (rev 02)
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 19
	Region 0: Memory at d0627000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at e000 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c-i801

00:1f.5 IDE interface: Intel Corporation ICH10 2 port SATA IDE Controller (rev 02) (prog-if 85 [Master SecO PriO])
	Subsystem: Intel Corporation Device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 21
	Region 0: I/O ports at e170 [size=8]
	Region 1: I/O ports at e160 [size=4]
	Region 2: I/O ports at e150 [size=8]
	Region 3: I/O ports at e140 [size=4]
	Region 4: I/O ports at e130 [size=16]
	Region 5: I/O ports at e120 [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] Vendor Specific Information <?>
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix

01:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
	Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC Management NIC
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (2500ns min, 2500ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: I/O ports at d000 [size=128]
	Region 1: Memory at d0521100 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at d0700000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot 
+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-
	Kernel driver in use: 3c59x
	Kernel modules: 3c59x

01:01.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) (prog-if 10
[OHCI])
	Subsystem: Intel Corporation Device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (3000ns min, 6000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at d0520000 (32-bit, non-prefetchable) [size=4K]
	Region 1: Memory at d0521000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [44] 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+
	Kernel driver in use: ohci1394
	Kernel modules: ohci1394



[-- Attachment #4: notes.txt --]
[-- Type: text/plain, Size: 4939 bytes --]

** The RMRRs, one for USB and one for GFX

Reserved Memory Region Reporting (RMRR) Structure #1
Type:           0x0001 (ACPI_DMAR_RMRR)
Length:         0x0058
Reserved:       0x0000
Segment Number: 0x0000
Base Address:   0xbd626000
End Address:    0xbd639fff
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x01
    Device Scope Structure #3
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x02
    Device Scope Structure #4
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x07
    Device Scope Structure #5
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x00
    Device Scope Structure #6
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x01
    Device Scope Structure #7
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x02
    Device Scope Structure #8
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x07

Reserved Memory Region Reporting (RMRR) Structure #2
Type:           0x0001 (ACPI_DMAR_RMRR)
Length:         0x0028
Reserved:       0x0000
Segment Number: 0x0000
Base Address:   0xbdc00000
End Address:    0xffffffffbfffffff
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x02 Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x02 Function: 0x01
       
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6c1000 (usable)
(XEN)  00000000bd6c1000 - 00000000bd703000 (ACPI NVS)
(XEN)  00000000bd703000 - 00000000bd826000 (reserved)
(XEN)  00000000bd826000 - 00000000bd83a000 (ACPI NVS)
(XEN)  00000000bd83a000 - 00000000bd93c000 (reserved)
(XEN)  00000000bd93c000 - 00000000bd93d000 (ACPI NVS)
(XEN)  00000000bd93d000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd94c000 (ACPI data)
(XEN)  00000000bd94c000 - 00000000bd967000 (ACPI NVS)
(XEN)  00000000bd967000 - 00000000bd986000 (reserved)
(XEN)  00000000bd986000 - 00000000bd98c000 (ACPI NVS)
(XEN)  00000000bd98c000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)

** RMRR 0xbd626000 - 0xbd639fff for USB falls in this e820 range. It should be reserved but is
   in a usable range. Not really correct.
(XEN)  0000000000100000 - 00000000bd6c1000 (usable) 

** RMRR 0xbdc00000 - 0xffffffffbfffffff for GFX seems way off. It starts in this range but just
   keeps going and going.
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)

[-- Attachment #5: xen.txt --]
[-- Type: text/plain, Size: 8420 bytes --]

root@obelix:~# amtterm -u admin -p ****** 10.11.1.31
amtterm: NONE -> CONNECT (connection to host)
ipv4 10.11.1.31 [10.11.1.31] 16994 open
amtterm: CONNECT -> INIT (redirection initialization)
amtterm: INIT -> AUTH (session authentication)
amtterm: AUTH -> INIT_SOL (serial-over-lan initialization)
amtterm: INIT_SOL -> RUN_SOL (serial-over-lan active) serial-over-lan redirection ok connected now, use ^] to escape
  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version
4.3.2 (Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6c1000 (usable) 
(XEN)  00000000bd6c1000 - 00000000bd703000 (ACPI NVS)
(XEN)  00000000bd703000 - 00000000bd826000 (reserved)
(XEN)  00000000bd826000 - 00000000bd83a000 (ACPI NVS)
(XEN)  00000000bd83a000 - 00000000bd93c000 (reserved)
(XEN)  00000000bd93c000 - 00000000bd93d000 (ACPI NVS)
(XEN)  00000000bd93d000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd94c000 (ACPI data)
(XEN)  00000000bd94c000 - 00000000bd967000 (ACPI NVS)
(XEN)  00000000bd967000 - 00000000bd986000 (reserved)
(XEN)  00000000bd986000 - 00000000bd98c000 (ACPI NVS)
(XEN)  00000000bd98c000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8281932kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94AE18, 005C (r1 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: FACP BD949D98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD942018, 6818 (r1 INTEL  DQ45CB         4F INTL  
20051117)
(XEN) ACPI: FACS BD952F40, 0040
(XEN) ACPI: APIC BD949F18, 006C (r2 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: MCFG BD954E18, 003C (r1 INTEL  DQ45CB         4F  
MSFT       97)
(XEN) ACPI: ASF! BD953D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM     
F4240)
(XEN) ACPI: SPCR BD954D18, 0050 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: TCPA BD954C98, 0032 (r2 INTEL  DQ45CB         4F MSFT   
1000013)
(XEN) ACPI: DMAR BD93CC18, 0120 (r1 INTEL  DQ45CB         4F  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd952f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base = bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.099 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer


[-- Attachment #6: 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] 28+ messages in thread

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-28 17:56                               ` Ross Philipson
@ 2009-04-29 23:47                                 ` Tim Kaufmann
  2009-04-30  1:00                                   ` Tim Kaufmann
  2009-04-30  4:38                                   ` Cui, Dexuan
  0 siblings, 2 replies; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-29 23:47 UTC (permalink / raw)
  To: Ross Philipson; +Cc: xen-devel


Am 28.04.2009 um 19:56 schrieb Ross Philipson:

> Attached is a textual version of your DMAR and some notes. In  
> notes.txt at the bottom I noted that both RMRRs seem to have some  
> issues but the iommu_inclusive_mapping=1 should have handled them.

I tried again with no success, logfile attached.

> You said the BIOS you have is the latest - did you check with Intel  
> to see if there are any known issues?

No, I wouldn't know where to ask. The support pages for the  
motherboard show nothing. I tried to downgrade to an earlier BIOS  
which was said to be ok here:

http://lists.xensource.com/archives/html/xen-users/2008-10/msg00618.html

Unfortunately the flash tool didn't flash the older BIOS.

Tim

  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1  
iommu_inclusive_mapping=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 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6c1000 (usable)
(XEN)  00000000bd6c1000 - 00000000bd703000 (ACPI NVS)
(XEN)  00000000bd703000 - 00000000bd826000 (reserved)
(XEN)  00000000bd826000 - 00000000bd83a000 (ACPI NVS)
(XEN)  00000000bd83a000 - 00000000bd93c000 (reserved)
(XEN)  00000000bd93c000 - 00000000bd93d000 (ACPI NVS)
(XEN)  00000000bd93d000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd94c000 (ACPI data)
(XEN)  00000000bd94c000 - 00000000bd967000 (ACPI NVS)
(XEN)  00000000bd967000 - 00000000bd986000 (reserved)
(XEN)  00000000bd986000 - 00000000bd98c000 (ACPI NVS)
(XEN)  00000000bd98c000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8281932kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94AE18, 005C (r1 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: FACP BD949D98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD942018, 6818 (r1 INTEL  DQ45CB         4F INTL  
20051117)
(XEN) ACPI: FACS BD952F40, 0040
(XEN) ACPI: APIC BD949F18, 006C (r2 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: MCFG BD954E18, 003C (r1 INTEL  DQ45CB         4F  
MSFT       97)
(XEN) ACPI: ASF! BD953D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM     
F4240)
(XEN) ACPI: SPCR BD954D18, 0050 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: TCPA BD954C98, 0032 (r2 INTEL  DQ45CB         4F MSFT   
1000013)
(XEN) ACPI: DMAR BD93CC18, 0120 (r1 INTEL  DQ45CB         4F  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd952f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.069 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-29 23:47                                 ` Tim Kaufmann
@ 2009-04-30  1:00                                   ` Tim Kaufmann
  2009-04-30  4:38                                   ` Cui, Dexuan
  1 sibling, 0 replies; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-30  1:00 UTC (permalink / raw)
  To: xen-devel; +Cc: Ross Philipson


> No, I wouldn't know where to ask. The support pages for the  
> motherboard show nothing. I tried to downgrade to an earlier BIOS  
> which was said to be ok here:
>
> http://lists.xensource.com/archives/html/xen-users/2008-10/msg00618.html
>
> Unfortunately the flash tool didn't flash the older BIOS.

Ok, I managed to downgrade using the board's BIOS recovery feature.  
But even with that BIOS I cannot get a VT-d enabled Xen to boot.

Tim

  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1  
max_loop=128 dom0_mem=1024M noreboot
(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 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6df000 (usable)
(XEN)  00000000bd6df000 - 00000000bd721000 (ACPI NVS)
(XEN)  00000000bd721000 - 00000000bd83f000 (reserved)
(XEN)  00000000bd83f000 - 00000000bd842000 (ACPI NVS)
(XEN)  00000000bd842000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd943000 (ACPI NVS)
(XEN)  00000000bd943000 - 00000000bd948000 (reserved)
(XEN)  00000000bd948000 - 00000000bd950000 (ACPI data)
(XEN)  00000000bd950000 - 00000000bd96b000 (ACPI NVS)
(XEN)  00000000bd96b000 - 00000000bd98a000 (reserved)
(XEN)  00000000bd98a000 - 00000000bd990000 (ACPI NVS)
(XEN)  00000000bd990000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8282036kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94EE18, 005C (r1 INTEL  DQ45CB         3D MSFT     
10013)
(XEN) ACPI: FACP BD94DD98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD948018, 4E9A (r1 INTEL  DQ45CB         3D INTL  
20051117)
(XEN) ACPI: FACS BD956F40, 0040
(XEN) ACPI: APIC BD94DF18, 006C (r2 INTEL  DQ45CB         3D MSFT     
10013)
(XEN) ACPI: MCFG BD958E18, 003C (r1 INTEL  DQ45CB         3D  
MSFT       97)
(XEN) ACPI: ASF! BD957D18, 00A0 (r32 INTEL  DQ45CB         3D TFSM     
F4240)
(XEN) ACPI: SPCR BD958D18, 0050 (r1 INTEL  DQ45CB         3D  
AMI.        3)
(XEN) ACPI: TCPA BD958C98, 0032 (r2 INTEL  DQ45CB         3D MSFT   
1000013)
(XEN) ACPI: DMAR BD942C18, 0120 (r1 INTEL  DQ45CB         3D  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd956f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.128 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-29 23:47                                 ` Tim Kaufmann
  2009-04-30  1:00                                   ` Tim Kaufmann
@ 2009-04-30  4:38                                   ` Cui, Dexuan
  2009-04-30 10:44                                     ` Tim Kaufmann
  2009-04-30 11:49                                     ` Tim Kaufmann
  1 sibling, 2 replies; 28+ messages in thread
From: Cui, Dexuan @ 2009-04-30  4:38 UTC (permalink / raw)
  To: Tim Kaufmann, Ross Philipson; +Cc: xen-devel

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

Hi Tim,
DQ45CB should be Eaglelake/ICH10 based vPro McCreary platform.
Our McCreary test boxes can work fine with VT-d enabled and we don't meet with the hang you see.
You said your McCreary is a custom assembly; not sure what HW/BIOS differences cause your issue.

Can you apply the attached  patch to the latest xen-unstable and build xen and try it again? And please post the serial log.
Per my experience, such issues generally are caused by not mapping some pages into VT-d page tables somehow. So let's try the attached patch.

Thanks,
-- Dexuan


-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tim Kaufmann
Sent: Thursday, April 30, 2009 7:48 AM
To: Ross Philipson
Cc: xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB


Am 28.04.2009 um 19:56 schrieb Ross Philipson:

> Attached is a textual version of your DMAR and some notes. In  
> notes.txt at the bottom I noted that both RMRRs seem to have some  
> issues but the iommu_inclusive_mapping=1 should have handled them.

I tried again with no success, logfile attached.

> You said the BIOS you have is the latest - did you check with Intel  
> to see if there are any known issues?

No, I wouldn't know where to ask. The support pages for the  
motherboard show nothing. I tried to downgrade to an earlier BIOS  
which was said to be ok here:

http://lists.xensource.com/archives/html/xen-users/2008-10/msg00618.html

Unfortunately the flash tool didn't flash the older BIOS.

Tim

  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Sun Apr 26 16:00:39 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1  
iommu_inclusive_mapping=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 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6c1000 (usable)
(XEN)  00000000bd6c1000 - 00000000bd703000 (ACPI NVS)
(XEN)  00000000bd703000 - 00000000bd826000 (reserved)
(XEN)  00000000bd826000 - 00000000bd83a000 (ACPI NVS)
(XEN)  00000000bd83a000 - 00000000bd93c000 (reserved)
(XEN)  00000000bd93c000 - 00000000bd93d000 (ACPI NVS)
(XEN)  00000000bd93d000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd94c000 (ACPI data)
(XEN)  00000000bd94c000 - 00000000bd967000 (ACPI NVS)
(XEN)  00000000bd967000 - 00000000bd986000 (reserved)
(XEN)  00000000bd986000 - 00000000bd98c000 (ACPI NVS)
(XEN)  00000000bd98c000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8281932kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94AE18, 005C (r1 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: FACP BD949D98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD942018, 6818 (r1 INTEL  DQ45CB         4F INTL  
20051117)
(XEN) ACPI: FACS BD952F40, 0040
(XEN) ACPI: APIC BD949F18, 006C (r2 INTEL  DQ45CB         4F MSFT     
10013)
(XEN) ACPI: MCFG BD954E18, 003C (r1 INTEL  DQ45CB         4F  
MSFT       97)
(XEN) ACPI: ASF! BD953D18, 00A0 (r32 INTEL  DQ45CB         4F TFSM     
F4240)
(XEN) ACPI: SPCR BD954D18, 0050 (r1 INTEL  DQ45CB         4F  
AMI.        3)
(XEN) ACPI: TCPA BD954C98, 0032 (r2 INTEL  DQ45CB         4F MSFT   
1000013)
(XEN) ACPI: DMAR BD93CC18, 0120 (r1 INTEL  DQ45CB         4F  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd952f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.069 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer



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

[-- Attachment #2: map_all.patch --]
[-- Type: application/octet-stream, Size: 1303 bytes --]

diff -r cc6db34c2996 xen/drivers/passthrough/iommu.c
--- a/xen/drivers/passthrough/iommu.c	Wed Apr 29 13:54:57 2009 +0100
+++ b/xen/drivers/passthrough/iommu.c	Thu Apr 30 12:19:01 2009 +0800
@@ -51,9 +51,9 @@ static void __init parse_iommu_param(cha
 {
     char *ss;
     iommu_enabled = 1;
-    iommu_snoop = 1;
-    iommu_qinval = 1;
-    iommu_intremap = 1;
+    iommu_snoop = 0;
+    iommu_qinval = 0;
+    iommu_intremap = 0;
 
     do {
         ss = strchr(s, ',');
diff -r cc6db34c2996 xen/drivers/passthrough/vtd/x86/vtd.c
--- a/xen/drivers/passthrough/vtd/x86/vtd.c	Wed Apr 29 13:54:57 2009 +0100
+++ b/xen/drivers/passthrough/vtd/x86/vtd.c	Thu Apr 30 12:20:37 2009 +0800
@@ -168,6 +168,7 @@ void iommu_set_dom0_mapping(struct domai
          * inclusive mapping maps in everything below 4GB except unusable
          * ranges. 
          */
+#if 0
         if ( !page_is_ram_type(i, RAM_TYPE_CONVENTIONAL) &&
              (!iommu_inclusive_mapping ||
               page_is_ram_type(i, RAM_TYPE_UNUSABLE)) )
@@ -176,6 +177,7 @@ void iommu_set_dom0_mapping(struct domai
         /* Exclude Xen bits */
         if ( xen_in_range(i << PAGE_SHIFT, (i + 1) << PAGE_SHIFT) )
             continue;
+#endif
 
         tmp = 1 << (PAGE_SHIFT - PAGE_SHIFT_4K);
         for ( j = 0; j < tmp; j++ )

[-- 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] 28+ messages in thread

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-30  4:38                                   ` Cui, Dexuan
@ 2009-04-30 10:44                                     ` Tim Kaufmann
  2009-04-30 11:49                                     ` Tim Kaufmann
  1 sibling, 0 replies; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-30 10:44 UTC (permalink / raw)
  To: Cui, Dexuan; +Cc: xen-devel, Ross Philipson

Hi Dexuan,

> You said your McCreary is a custom assembly; not sure what HW/BIOS  
> differences cause your issue.

May be there's a misunderstanding. I bought a boxed motherboard and  
cpu, a case and a psu and had them assembled by a local computer  
company. And I downloaded the official BIOS from intel.com.

> Can you apply the attached  patch to the latest xen-unstable and  
> build xen and try it again?

Like this?

cd /usr/src/xen-unstable
patch -p1 < ../map.all.patch

Tim

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-30  4:38                                   ` Cui, Dexuan
  2009-04-30 10:44                                     ` Tim Kaufmann
@ 2009-04-30 11:49                                     ` Tim Kaufmann
  2009-05-04 21:48                                       ` Tim Kaufmann
  2009-05-05  7:57                                       ` Cui, Dexuan
  1 sibling, 2 replies; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-30 11:49 UTC (permalink / raw)
  To: Cui, Dexuan; +Cc: xen-devel


Am 30.04.2009 um 06:38 schrieb Cui, Dexuan:

> So let's try the attached patch.

Couldn't wait, so I patched with

$ patch -p1 < ../map.all.patch

Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1

Output below.

Tim

  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Thu Apr 30 13:21:56 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6df000 (usable)
(XEN)  00000000bd6df000 - 00000000bd721000 (ACPI NVS)
(XEN)  00000000bd721000 - 00000000bd83f000 (reserved)
(XEN)  00000000bd83f000 - 00000000bd842000 (ACPI NVS)
(XEN)  00000000bd842000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd943000 (ACPI NVS)
(XEN)  00000000bd943000 - 00000000bd948000 (reserved)
(XEN)  00000000bd948000 - 00000000bd950000 (ACPI data)
(XEN)  00000000bd950000 - 00000000bd96b000 (ACPI NVS)
(XEN)  00000000bd96b000 - 00000000bd98a000 (reserved)
(XEN)  00000000bd98a000 - 00000000bd990000 (ACPI NVS)
(XEN)  00000000bd990000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8282036kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94EE18, 005C (r1 INTEL  DQ45CB         3D MSFT     
10013)
(XEN) ACPI: FACP BD94DD98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD948018, 4E9A (r1 INTEL  DQ45CB         3D INTL  
20051117)
(XEN) ACPI: FACS BD956F40, 0040
(XEN) ACPI: APIC BD94DF18, 006C (r2 INTEL  DQ45CB         3D MSFT     
10013)
(XEN) ACPI: MCFG BD958E18, 003C (r1 INTEL  DQ45CB         3D  
MSFT       97)
(XEN) ACPI: ASF! BD957D18, 00A0 (r32 INTEL  DQ45CB         3D TFSM     
F4240)
(XEN) ACPI: SPCR BD958D18, 0050 (r1 INTEL  DQ45CB         3D  
AMI.        3)
(XEN) ACPI: TCPA BD958C98, 0032 (r2 INTEL  DQ45CB         3D MSFT   
1000013)
(XEN) ACPI: DMAR BD942C18, 0120 (r1 INTEL  DQ45CB         3D  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd956f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.079 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-30 11:49                                     ` Tim Kaufmann
@ 2009-05-04 21:48                                       ` Tim Kaufmann
  2009-05-05  7:41                                         ` Re[2]: " Sander Eikelenboom
  2009-05-20 19:38                                         ` Sander Eikelenboom
  2009-05-05  7:57                                       ` Cui, Dexuan
  1 sibling, 2 replies; 28+ messages in thread
From: Tim Kaufmann @ 2009-05-04 21:48 UTC (permalink / raw)
  To: xen-devel; +Cc: Dexuan Cui

Nobody's got a clue on how to solve this? Should I get myself another  
motherboard, and if so, which one is recommended?

Tim

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

* Re[2]: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-05-04 21:48                                       ` Tim Kaufmann
@ 2009-05-05  7:41                                         ` Sander Eikelenboom
  2009-05-20 19:38                                         ` Sander Eikelenboom
  1 sibling, 0 replies; 28+ messages in thread
From: Sander Eikelenboom @ 2009-05-05  7:41 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

There are also VT-D troubles on ASUS motherboards, perhaps it's even AMI-bios
related. I'm having support requests running at both at the moment. I will
keep the list informed if it's solved (or not)

I was considering the DQ45CB if those support calls don't result in a fix,
but from what I hear from you even Intel isn't able to make it work out of
the box too :-(. And i'm not going to buy something again without knowing
sure it does what it promises and has error-free VT-D/IOMMU support.

I hope it gets straightened out soon, else AMD will release there first
chipset with IOMMU, perhaps they did a better job...

Perhaps it would be wise to make a list on the VT-D passthrough wiki of
motherboards that do or don't have error free VT-D.

--
Sander

Monday, May 4, 2009, 11:48:53 PM, you wrote:

> Nobody's got a clue on how to solve this? Should I get myself another  
> motherboard, and if so, which one is recommended?

> Tim

-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it

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

* Re[2]: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-05-04 21:48                                       ` Tim Kaufmann
  2009-05-05  7:41                                         ` Re[2]: " Sander Eikelenboom
@ 2009-05-20 19:38                                         ` Sander Eikelenboom
  2009-05-20 21:33                                           ` Tim Kaufmann
  1 sibling, 1 reply; 28+ messages in thread
From: Sander Eikelenboom @ 2009-05-20 19:38 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

Hello Tim,

Are you problems with VT-D and the Intel-Board DQ45CB fixed ?

Since i'm considering buying this motherboard for VT-D use ...

Regards,

Sander Eikelenboom


Monday, May 4, 2009, 11:48:53 PM, you wrote:

> Nobody's got a clue on how to solve this? Should I get myself another  
> motherboard, and if so, which one is recommended?

> Tim







-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it

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

* Re: Re[2]: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-05-20 19:38                                         ` Sander Eikelenboom
@ 2009-05-20 21:33                                           ` Tim Kaufmann
  2009-05-22  2:45                                             ` Cui, Dexuan
  0 siblings, 1 reply; 28+ messages in thread
From: Tim Kaufmann @ 2009-05-20 21:33 UTC (permalink / raw)
  To: xen-devel
  Cc: Anthony Bosio, "Matthias P. Würfl",
	Sander Eikelenboom


Am 20.05.2009 um 21:38 schrieb Sander Eikelenboom:

> Are you problems with VT-D and the Intel-Board DQ45CB fixed ?

Almost.

In fact, the hang occurs with RAM > 2 GB and is caused by a BIOS  
error. As one of the Intel guys on this list told me after several  
tests:

> Please let me offer more technical details about the hang you suffer  
> from:
> Due to the very very big and bad rmrr->end_address  
> 0xffffffffbfffffff, in setup_dom0_rmrr() ->  
> iommu_prepare_rmrr_dev(),  intel_iommu_map_page() is invoked too too  
> many times and you see the hang...

I already received a patch for Xen 3.4RC4 which I can properly enable  
VT-d with. But there'll be a BIOS-Update soon, they promised.

Tim

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

* RE: Re[2]: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-05-20 21:33                                           ` Tim Kaufmann
@ 2009-05-22  2:45                                             ` Cui, Dexuan
  0 siblings, 0 replies; 28+ messages in thread
From: Cui, Dexuan @ 2009-05-22  2:45 UTC (permalink / raw)
  To: Tim Kaufmann, xen-devel
  Cc: Anthony Bosio, "Matthias P. Würfl", Eikelenboom

Tim Kaufmann wrote:
> Am 20.05.2009 um 21:38 schrieb Sander Eikelenboom:
> 
>> Are you problems with VT-D and the Intel-Board DQ45CB fixed ?
> 
> Almost.
> 
> In fact, the hang occurs with RAM > 2 GB and is caused by a BIOS
> error. As one of the Intel guys on this list told me after several
> tests:
Actually the VT-d support of the motherboard is good.
The issue is caused by a small mistake in RMRR reporting in BIOS.

> 
>> Please let me offer more technical details about the hang you suffer
>> from: Due to the very very big and bad rmrr->end_address
>> 0xffffffffbfffffff, in setup_dom0_rmrr() ->
>> iommu_prepare_rmrr_dev(),  intel_iommu_map_page() is invoked too too
>> many times and you see the hang...
> 
> I already received a patch for Xen 3.4RC4 which I can properly enable
> VT-d with. But there'll be a BIOS-Update soon, they promised.

Yes, I think a BIOS update should come out soon.
For now, we can use the following small patch as a workaround. :-)

diff -r f80cf52a4fb6 xen/drivers/passthrough/vtd/iommu.c
--- a/xen/drivers/passthrough/vtd/iommu.c	Thu Apr 30 14:34:15 2009 +0100
+++ b/xen/drivers/passthrough/vtd/iommu.c	Mon May 18 16:12:14 2009 +0800
@@ -1541,6 +1541,8 @@ static int iommu_prepare_rmrr_dev(struct
     ASSERT(spin_is_locked(&pcidevs_lock));
     ASSERT(rmrr->base_address < rmrr->end_address);
     
+    if ( (rmrr->end_address >> 32) & 0x80000000 )
+        rmrr->end_address &= 0xFFFFFFFF;
     base = rmrr->base_address & PAGE_MASK_4K;
     base_pfn = base >> PAGE_SHIFT_4K;
     end = PAGE_ALIGN_4K(rmrr->end_address);


Thanks,
-- Dexuan

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

* RE: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-30 11:49                                     ` Tim Kaufmann
  2009-05-04 21:48                                       ` Tim Kaufmann
@ 2009-05-05  7:57                                       ` Cui, Dexuan
  1 sibling, 0 replies; 28+ messages in thread
From: Cui, Dexuan @ 2009-05-05  7:57 UTC (permalink / raw)
  To: Tim Kaufmann; +Cc: xen-devel

Since you still meet with the hang even with all MFNs mapped, I have no idea now. :-(

Could you please try the latest native Linux kernel with IOMMU on?
If native Linux has the same symptom, I personally tend to think this is a BIOS issue.

Thanks,
-- Dexuan



-----Original Message-----
From: Tim Kaufmann [mailto:tk@taquiri.de] 
Sent: 2009年4月30日 19:49
To: Cui, Dexuan
Cc: xen-devel
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB


Am 30.04.2009 um 06:38 schrieb Cui, Dexuan:

> So let's try the attached patch.

Couldn't wait, so I patched with

$ patch -p1 < ../map.all.patch

Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1

Output below.

Tim

  __  __            _____ _  _    ___              _____
  \ \/ /___ _ __   |___ /| || |  / _ \    _ __ ___|___ /    _ __  _ __  
___
   \  // _ \ '_ \    |_ \| || |_| | | |__| '__/ __| |_ \ __| '_ \|  
'__/ _ \
   /  \  __/ | | |  ___) |__   _| |_| |__| | | (__ ___) |__| |_) | |  
|  __/
  /_/\_\___|_| |_| |____(_) |_|(_)___/   |_|  \___|____/   | .__/|_|   
\___|
                                                           |_|
(XEN) Xen version 3.4.0-rc3-pre (root@taquiri.dyndns.org) (gcc version  
4.3.2 (Debian 4.3.2-1.1) ) Thu Apr 30 13:21:56 CEST 2009
(XEN) Latest ChangeSet: Fri Apr 24 13:46:17 2009 +0100  
19575:dc5bd14a4675
(XEN) Command line: console=com1 com1=115200,8n1,0xe1c0,0 iommu=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6df000 (usable)
(XEN)  00000000bd6df000 - 00000000bd721000 (ACPI NVS)
(XEN)  00000000bd721000 - 00000000bd83f000 (reserved)
(XEN)  00000000bd83f000 - 00000000bd842000 (ACPI NVS)
(XEN)  00000000bd842000 - 00000000bd942000 (reserved)
(XEN)  00000000bd942000 - 00000000bd943000 (ACPI NVS)
(XEN)  00000000bd943000 - 00000000bd948000 (reserved)
(XEN)  00000000bd948000 - 00000000bd950000 (ACPI data)
(XEN)  00000000bd950000 - 00000000bd96b000 (ACPI NVS)
(XEN)  00000000bd96b000 - 00000000bd98a000 (reserved)
(XEN)  00000000bd98a000 - 00000000bd990000 (ACPI NVS)
(XEN)  00000000bd990000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8282036kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94EE18, 005C (r1 INTEL  DQ45CB         3D MSFT     
10013)
(XEN) ACPI: FACP BD94DD98, 00F4 (r4  INTEL    A M I  6222004 MSFT     
10013)
(XEN) ACPI: DSDT BD948018, 4E9A (r1 INTEL  DQ45CB         3D INTL  
20051117)
(XEN) ACPI: FACS BD956F40, 0040
(XEN) ACPI: APIC BD94DF18, 006C (r2 INTEL  DQ45CB         3D MSFT     
10013)
(XEN) ACPI: MCFG BD958E18, 003C (r1 INTEL  DQ45CB         3D  
MSFT       97)
(XEN) ACPI: ASF! BD957D18, 00A0 (r32 INTEL  DQ45CB         3D TFSM     
F4240)
(XEN) ACPI: SPCR BD958D18, 0050 (r1 INTEL  DQ45CB         3D  
AMI.        3)
(XEN) ACPI: TCPA BD958C98, 0032 (r2 INTEL  DQ45CB         3D MSFT   
1000013)
(XEN) ACPI: DMAR BD942C18, 0120 (r1 INTEL  DQ45CB         3D  
INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000023c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd956f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base  
= bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter  
may be needed.
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2833.079 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz stepping 0a
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-26 14:29 No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB Tim Kaufmann
  2009-04-26 14:51 ` Tim Kaufmann
@ 2009-04-27 10:41 ` Christian Tramnitz
  2009-04-27 11:16   ` Tim Kaufmann
  1 sibling, 1 reply; 28+ messages in thread
From: Christian Tramnitz @ 2009-04-27 10:41 UTC (permalink / raw)
  To: xen-devel

So what is your actual problem then?

 > (XEN) I/O virtualisation enabled
This means VT-d is enabled.

If you are wondering about:
 > (XEN) I/O virtualisation for PV guests disabled
You may want to have a look at iommu=pv if that is what you need...


Best regards,
    Christian

Tim Kaufmann wrote:
> Hello,
> 
> my system: Intel DQ45CB with latest BIOS (0079 as of April 6th 2009) and 
> VT-d enabled, Core 2 Quad Q9550 (E0), 8 GB RAM.
> 
> Tested with OpenSuse 11.1, packaged Kernel/Xen 3.3 and kernel opts 
> "iommu=1", "iommu=1 msi=1", "dom0_mem=1024M iommu=1", "dom0_mem=1024M 
> iommu=1 msi=1". System freezes on boot, last messages displayed are
> 
> (XEN) I/O virtualisation enabled
> (XEN) I/O virtualisation for PV guests disabled
> 
> Installed Debian Lenny and compiled 2.6.18.8 / Xen 3.4rc3 - same result 
> as above.
> 
> I'd like to help debugging this, but I'd need someone to help me setting 
> up Serial-over-LAN with one of my other computers (Ubuntu 8.04 LTS, XP, 
> Mac OS X 10.5).
> 
> Tim

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

* Re: Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 10:41 ` Christian Tramnitz
@ 2009-04-27 11:16   ` Tim Kaufmann
  2009-04-27 14:51     ` Christian Tramnitz
  0 siblings, 1 reply; 28+ messages in thread
From: Tim Kaufmann @ 2009-04-27 11:16 UTC (permalink / raw)
  To: Christian Tramnitz; +Cc: xen-devel


Am 27.04.2009 um 12:41 schrieb Christian Tramnitz:

> So what is your actual problem then?

As I wrote: I cannot boot with iommu=1 because the system freezes.

Tim

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

* Re: No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
  2009-04-27 11:16   ` Tim Kaufmann
@ 2009-04-27 14:51     ` Christian Tramnitz
  0 siblings, 0 replies; 28+ messages in thread
From: Christian Tramnitz @ 2009-04-27 14:51 UTC (permalink / raw)
  To: xen-devel

Tim Kaufmann wrote:
> As I wrote: I cannot boot with iommu=1 because the system freezes.

Sorry I should have paid more attention on the actual text and not just 
to the topic.
Have you tried any of the "no-" params yet (no-snoop, no-qinval, 
no-intremap)?

It could also be related to powersaving, could you disable (xen-)cpuidle 
for testing?

Best regards,
    Christian

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

end of thread, other threads:[~2009-05-22  2:45 UTC | newest]

Thread overview: 28+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-26 14:29 No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB Tim Kaufmann
2009-04-26 14:51 ` Tim Kaufmann
2009-04-26 21:04   ` Ross Philipson
2009-04-26 23:35     ` Tim Kaufmann
2009-04-27 13:39       ` Ross Philipson
     [not found]         ` <F126C20F-9063-4FCC-BF8F-FE4CCDBCF1E5@taquiri.de>
     [not found]           ` <831D55AF5A11D64C9B4B43F59EEBF72035FCB540E5@FTLPMAILBOX02.citrite.net>
     [not found]             ` <21F81074-ADE6-4913-A77E-4615F84E5CB9@taquiri.de>
     [not found]               ` <831D55AF5A11D64C9B4B43F59EEBF72035FCB540F1@FTLPMAILBOX02.citrite.net>
2009-04-27 16:48                 ` Tim Kaufmann
2009-04-27 18:00                   ` Ross Philipson
2009-04-27 18:31                     ` Tim Kaufmann
2009-04-27 18:39                       ` Ross Philipson
2009-04-27 19:01                         ` Pasi Kärkkäinen
2009-04-27 19:07                           ` Ross Philipson
2009-04-27 21:15                             ` Tim Kaufmann
2009-04-27 21:23                               ` Ross Philipson
2009-04-28 17:56                               ` Ross Philipson
2009-04-29 23:47                                 ` Tim Kaufmann
2009-04-30  1:00                                   ` Tim Kaufmann
2009-04-30  4:38                                   ` Cui, Dexuan
2009-04-30 10:44                                     ` Tim Kaufmann
2009-04-30 11:49                                     ` Tim Kaufmann
2009-05-04 21:48                                       ` Tim Kaufmann
2009-05-05  7:41                                         ` Re[2]: " Sander Eikelenboom
2009-05-20 19:38                                         ` Sander Eikelenboom
2009-05-20 21:33                                           ` Tim Kaufmann
2009-05-22  2:45                                             ` Cui, Dexuan
2009-05-05  7:57                                       ` Cui, Dexuan
2009-04-27 10:41 ` Christian Tramnitz
2009-04-27 11:16   ` Tim Kaufmann
2009-04-27 14:51     ` Christian Tramnitz

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.