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

Re: [Xen-devel] VT-d failure on Intel DQ43AP board


  • To: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
  • From: Takeshi HASEGAWA <hasegaw@xxxxxxxxx>
  • Date: Wed, 2 Sep 2009 11:56:26 +0900
  • Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 01 Sep 2009 20:01:39 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iKGoXk72WRQVCQd57ZJAJcHfjHLERNEdFkRc5FIioQxAJ4Tlw/Yanjm3/liKkjqObc nRrpiwBzb1qhgZBj/AKTgg1OfbkFncqI5ZICw6e9l3uWBXnZ5VdQo9QG4QM+fbZq2i5k S3hN9N1Yb+PGE5YdJ0Hhw4zkOA2mMfDYMgLQE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Dexuan,

I already tried settings such as switching disabled<->enabled, cold
boot, cold boot
that I I could think of. But I haven't unplugging power cord, so I'll
try tonight.

thanks,
Takeshi HASEGAWA

2009/8/31 Cui, Dexuan <dexuan.cui@xxxxxxxxx>:
> After you change your BIOS's VT-d setting from Disabled to Enabled (or from 
> Enabled to Disabled), can you try power cycle your host (unplug the power 
> cord and wait for some time)? If this works, it would be a BIOS issue.
>
> Thanks,
> -- Dexuan
>
>
>
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Takeshi HASEGAWA
> Sent: 2009?8?30? 0:21
> To: Xen-devel@xxxxxxxxxxxxxxxxxxx; Takeshi HASEGAWA
> Subject: [Xen-devel] VT-d failure on Intel DQ43AP board
>
> FYI
>
> I got an Intel DQ43AP board and tried enabling VT-d,
> but had a same problem that described below.
> http://lists.xensource.com/archives/cgi-bin/extract-mesg.cgi?a=xen-devel&m=2009-06&i=8686c3cd0906300041r3b59d2c9i7a9d7c6705aa1ed4%40mail.gmail.com
>
>> (XEN) clear_fault_bits: CAP_REG=0xffffffffffffffff
>
> Chasing the thread, I figured out that BIOS on the board looks
> have some problems around VT-d feature.
>
> - already updated BIOS to recent version (ver 0027, 2009-7-28).
>  http://downloadcenter.intel.com/Filter_Results.aspx?strOSs=All&strTypes=All&ProductID=3119
> - VT-d is enabled in BIOS configuration.
> - tried not only xen 3.4.0 but also xen-unstable that I got a few
>  hours ago, but got same result.
>
> I expect to wait for BIOS updates, although let me know what I can do
> if anyone have any ideas.
>
>
>
>  __  __            _____  ____                     _        _     _
>  \ \/ /___ _ __   |___ / | ___|    _   _ _ __  ___| |_ __ _| |__ | | ___
>  \  // _ \ '_ \    |_ \ |___ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
>  /  \  __/ | | |  ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
>  /_/\_\___|_| |_| |____(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
>
> (XEN) Xen version 3.5-unstable (root@) (gcc  4.1.2 20080704 (Red Hat
> 4.1.2-44)) Sat Aug 29 23:51:56 JST 2009
> (XEN) Latest ChangeSet: Thu Aug 27 11:25:34 2009 +0100 20128:e8004f6c254a
> (XEN) Command line: iommu=1 com1=9600,8n1 console=com1,vga
> iommu_inclusive_mapping=1
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000bd63d000 (usable)
> (XEN)  00000000bd63d000 - 00000000bd6c0000 (ACPI NVS)
> (XEN)  00000000bd6c0000 - 00000000bd81e000 (reserved)
> (XEN)  00000000bd81e000 - 00000000bd832000 (ACPI NVS)
> (XEN)  00000000bd832000 - 00000000bd93b000 (reserved)
> (XEN)  00000000bd93b000 - 00000000bd943000 (ACPI data)
> (XEN)  00000000bd943000 - 00000000bd95e000 (ACPI NVS)
> (XEN)  00000000bd95e000 - 00000000bd97f000 (reserved)
> (XEN)  00000000bd97f000 - 00000000bd985000 (ACPI NVS)
> (XEN)  00000000bd985000 - 00000000bdb00000 (usable)
> (XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
> (XEN)  00000000ff000000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 000000013c000000 (usable)
> (XEN) System RAM: 3991MB (4087128kB)
> (XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
> (XEN) ACPI: XSDT BD941E18, 0064 (r1 INTEL  DQ43AP         1B MSFT    10013)
> (XEN) ACPI: FACP BD940D98, 00F4 (r4  INTEL    A M I  6222004 MSFT    10013)
> (XEN) ACPI: DSDT BD93B018, 49C1 (r1 INTEL  DQ43AP         1B INTL 20051117)
> (XEN) ACPI: FACS BD949F40, 0040
> (XEN) ACPI: APIC BD940F18, 006C (r2 INTEL  DQ43AP         1B MSFT    10013)
> (XEN) ACPI: MCFG BD94BE18, 003C (r1 INTEL  DQ43AP         1B MSFT       97)
> (XEN) ACPI: ASF! BD94AD18, 00A0 (r32 INTEL  DQ43AP         1B TFSM    F4240)
> (XEN) ACPI: HPET BD94BD98, 0038 (r1 INTEL  DQ43AP         1B AMI.        3)
> (XEN) ACPI: SPCR BD94BD18, 0050 (r1 INTEL  DQ43AP         1B AMI.        3)
> (XEN) ACPI: TCPA BD94BC98, 0032 (r2 INTEL  DQ43AP         1B MSFT  1000013)
> (XEN) ACPI: DMAR BD6BFD98, 0120 (r1 INTEL  DQ43AP         1B INTL        1)
> (XEN) NUMA turned off
> (XEN) Faking a node at 0000000000000000-000000013c000000
> (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[bd949f4c], 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) [VT-D]dmar.c:527: Host address width 36
> (XEN) [VT-D]dmar.c:536: found ACPI_DMAR_DRHD
> (XEN) [VT-D]dmar.c:372: dmaru->address = fed90000
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1b.0
> (XEN) [VT-D]dmar.c:536: found ACPI_DMAR_DRHD
> (XEN) [VT-D]dmar.c:372: dmaru->address = fed91000
> (XEN) [VT-D]dmar.c:325: endpoint: 0:2.0
> (XEN) [VT-D]dmar.c:325: endpoint: 0:2.1
> (XEN) [VT-D]dmar.c:536: found ACPI_DMAR_DRHD
> (XEN) [VT-D]dmar.c:372: dmaru->address = fed92000
> (XEN) [VT-D]dmar.c:325: endpoint: 0:3.0
> (XEN) [VT-D]dmar.c:325: endpoint: 0:3.2
> (XEN) [VT-D]dmar.c:325: endpoint: 0:3.3
> (XEN) [VT-D]dmar.c:536: found ACPI_DMAR_DRHD
> (XEN) [VT-D]dmar.c:372: dmaru->address = fed93000
> (XEN) [VT-D]dmar.c:381: found INCLUDE_ALL
> (XEN) [VT-D]dmar.c:540: found ACPI_DMAR_RMRR
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1d.1
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1d.2
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1d.7
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1a.0
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1a.1
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1a.2
> (XEN) [VT-D]dmar.c:325: endpoint: 0:1a.7
> (XEN) [VT-D]dmar.c:540: found ACPI_DMAR_RMRR
> (XEN) [VT-D]dmar.c:424: RMRR address range not in reserved memory base
> = bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1 parameter
> may be needed.
> (XEN) [VT-D]dmar.c:325: endpoint: 0:2.0
> (XEN) [VT-D]dmar.c:325: endpoint: 0:2.1
> (XEN) Intel VT-d DMAR tables have been parsed.
> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
> (XEN) PCI: Not using MMCONFIG.
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Initializing CPU#0
> (XEN) Detected 2666.437 MHz processor.
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 2048K
> (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    Q8400  @ 2.66GHz 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: 2048K
> (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    Q8400  @ 2.66GHz 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: 2048K
> (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    Q8400  @ 2.66GHz 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: 2048K
> (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    Q8400  @ 2.66GHz 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) Brought up 4 CPUs
> (XEN) microcode.c:73:d32767 microcode: CPU3 resumed
> (XEN) microcode.c:73:d32767 microcode: CPU2 resumed
> (XEN) [VT-D]iommu.c:942:d32767 drhd->address = fed92000
> (XEN) [VT-D]iommu.c:943:d32767 iommu->reg = ffff828bfff57000
> (XEN) [VT-D]iommu.c:942:d32767 drhd->address = fed91000
> (XEN) [VT-D]iommu.c:943:d32767 iommu->reg = ffff828bfff56000
> (XEN) [VT-D]iommu.c:942:d32767 drhd->address = fed90000
> (XEN) [VT-D]iommu.c:943:d32767 iommu->reg = ffff828bfff55000
> (XEN) [VT-D]iommu.c:942:d32767 drhd->address = fed93000
> (XEN) [VT-D]iommu.c:943:d32767 iommu->reg = ffff828bfff54000
> (XEN) Intel VT-d Snoop Control supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping supported.
> (XEN) clear_fault_bits: CAP_REG=0xffffffffffffffff
> (XEN) ----[ Xen-3.5-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<ffff828c80137375>] clear_fault_bits+0x5d/0xe6
> (XEN) RFLAGS: 0000000000010006   CONTEXT: hypervisor
> (XEN) rax: ffff828bfff5aff0   rbx: ffff8301387fd8a0   rcx: ffff828bfff57000
> (XEN) rdx: 00000000ffffffff   rsi: 0000000000000282   rdi: ffff8301387fd8dc
> (XEN) rbp: ffff828c80297d68   rsp: ffff828c80297d58   r8:  ffff8300000b8000
> (XEN) r9:  0000000000000004   r10: 0000000000000010   r11: 0000000000000010
> (XEN) r12: ffff8301387fd8d8   r13: ffff83013be726f0   r14: 0000000000000018
> (XEN) r15: 0000000000000c00   cr0: 000000008005003b   cr4: 00000000000026f0
> (XEN) cr3: 00000000bd49c000   cr2: ffff828bfff5aff8
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff828c80297d58:
> (XEN)    00000000000000c0 ffff8301387fd8a0 ffff828c80297da8 ffff828c80138024
> (XEN)    0000000080297d88 ffff828bfff54000 ffff8301387fdb10 ffff828c80223790
> (XEN)    0000000000000040 0000000000100000 ffff828c80297de8 ffff828c80138f69
> (XEN)    0000000000000040 ffff828c80222400 000000000000001f ffff828c8024a350
> (XEN)    ffff828c8024a470 0000000000000003 ffff828c80297e08 ffff828c80134e95
> (XEN)    ffff828c80297e08 ffff828c8024a350 ffff828c80297f18 ffff828c8023d223
> (XEN)    0000000000000000 0000000000000000 ffff828c80228675 ffffffffc0290000
> (XEN)    ffff8300bd49cff8 ffff8300bd49dff8 0000000000228610 0000000000000000
> (XEN)    0000000000000000 0000000000000000 ffff83000008bfc0 ffff83000008bf50
> (XEN)    0000000000d1cbb0 0000000000000000 ffff83000008bf50 000000000008bf50
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000001000000 0000000800000000 000000010000006e
> (XEN)    0000000000000003 00000000000002f8 0000000000000000 0000000000000000
> (XEN)    0000000000000000 000000000000001f 00000000014b8018 0000000000000000
> (XEN)    0000000000067ebc ffff828c801000b5 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) Xen call trace:
> (XEN)    [<ffff828c80137375>] clear_fault_bits+0x5d/0xe6
> (XEN)    [<ffff828c80138024>] init_vtd_hw+0x186/0x3fd
> (XEN)    [<ffff828c80138f69>] intel_vtd_setup+0x586/0x6aa
> (XEN)    [<ffff828c80134e95>] iommu_setup+0x1f/0xd2
> (XEN)    [<ffff828c8023d223>] __start_xen+0x436b/0x4678
> (XEN)
> (XEN) Pagetable walk from ffff828bfff5aff8:
> (XEN)  L4[0x105] = 00000000bd4a2027 5555555555555555
> (XEN)  L3[0x02f] = 000000013be79063 5555555555555555
> (XEN)  L2[0x1ff] = 000000013be78063 5555555555555555
> (XEN)  L1[0x15a] = 0000000000000000 ffffffffffffffff
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: ffff828bfff5aff8
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
>
>
> --
> Takeshi HASEGAWA <hasegaw@xxxxxxxxx>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>



-- 
Takeshi HASEGAWA <hasegaw@xxxxxxxxx>

_______________________________________________
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®.