[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB


  • To: Tim Kaufmann <tk@xxxxxxxxxx>, Ross Philipson <Ross.Philipson@xxxxxxxxxx>
  • From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
  • Date: Thu, 30 Apr 2009 12:38:26 +0800
  • Accept-language: zh-CN, en-US
  • Acceptlanguage: zh-CN, en-US
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 29 Apr 2009 21:39:27 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcnJJQWkY4KzLp8yQfWt/WwC6EvhqAAJuhNQ
  • Thread-topic: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

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@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] 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@xxxxxxxxxxxxxxxxxx) (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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Attachment: map_all.patch
Description: map_all.patch

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.