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

Re: [Xen-devel] VT-d: xen hangs while booting with iommu=1


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
  • Date: Thu, 3 Dec 2009 11:08:37 +0100
  • Cc: Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • Delivery-date: Thu, 03 Dec 2009 02:09:08 -0800
  • Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Subject:Date:User-Agent:Cc: References:In-Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Message-Id; b=XCHLnF8+Ln5I3lZESWINhTwPG5vwHLOJy0yNzUJJiBJIje7gww4+597g UCNp+JVKzLtd60SMdPLxKLny/OhHcNjJkWi6QMINWfQiF32qJrZz9eeR2 /QmEPH6BmbcRcNONRXLqYctLORhr00TgBlTyvsTadlmoxCrjqH+eRh2iH g+aSrbibRibkQRVW8k8aeYv1N2zgdrEaiEH8SWJtpS3aULgNPDPuKdUju s5NitRJrGCvahWEvJiJGfOfh+5jOQ;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> On Wed, Dec 2, 2009 at 2:23 PM, Dietmar Hahn
> <dietmar.hahn@xxxxxxxxxxxxxx> wrote:
> > Hi,
> >
> > I tried xen-unstable from last week with iommu=1 and xen hangs during boot.
> > Xen found 3 drhd structures. After enabling the translation for drhd
> > structure 3 in iommu_enable_translation() line
> > dmar_writel(iommu->reg, DMAR_GCMD_REG, sts | DMA_GCMD_TE);
> > it hangs forever.
> > Attached is the output of the serial console.
> >
> > I hope anyone understanding this better than me can give me a hint ;-).
> > Thanks.
> > Dietmar
> >
> >
> > (XEN) Xen version 3.5-unstable (hahn@xxxxxxxxxxx) (gcc version 4.4.1 
> > [gcc-4_4-branch revision 150839] (SUSE Linux) ) Wed Dec  2 15:08:17 CET 2009
> > (XEN) Latest ChangeSet: Tue Nov 24 14:43:07 2009 +0000 20491:d44371e6e5d6
> > (XEN) Console output is synchronous.
> > (XEN) Command line: iommu=1 console=com1 com1=38400,8n1 sync_console 
> > debug=yes loglvl=all guest_loglvl=all
> > (XEN) Video information:
> > (XEN)  VGA is text mode 80x25, font 8x16
> > (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
> > (XEN)  EDID info not retrieved because no DDC retrieval method detected
> > (XEN) Disc information:
> > (XEN)  Found 1 MBR signatures
> > (XEN)  Found 1 EDD information structures
> > (XEN) Xen-e820 RAM map:
> > (XEN)  0000000000000000 - 000000000009c400 (usable)
> > (XEN)  000000000009c400 - 00000000000a0000 (reserved)
> > (XEN)  00000000000dc000 - 0000000000100000 (reserved)
> > (XEN)  0000000000100000 - 00000000bf8b1000 (usable)
> > (XEN)  00000000bf8b1000 - 00000000bf8b7000 (reserved)
> > (XEN)  00000000bf8b7000 - 00000000bf9b4000 (usable)
> > (XEN)  00000000bf9b4000 - 00000000bfa0f000 (reserved)
> > (XEN)  00000000bfa0f000 - 00000000bfb08000 (usable)
> > (XEN)  00000000bfb08000 - 00000000bfd0f000 (reserved)
> > (XEN)  00000000bfd0f000 - 00000000bfd18000 (usable)
> > (XEN)  00000000bfd18000 - 00000000bfd1f000 (reserved)
> > (XEN)  00000000bfd1f000 - 00000000bfd53000 (usable)
> > (XEN)  00000000bfd53000 - 00000000bfd9f000 (ACPI NVS)
> > (XEN)  00000000bfd9f000 - 00000000bfdcc000 (usable)
> > (XEN)  00000000bfdcc000 - 00000000bfdfd000 (ACPI data)
> > (XEN)  00000000bfdfd000 - 00000000bfe00000 (usable)
> > (XEN)  0000000100000000 - 000000023c000000 (usable)
> > (XEN) ACPI: RSDP 000F6230, 0024 (r2 PTLTD )
> > (XEN) ACPI: XSDT BFDEFEBD, 008C (r1 FSC    PC        6040000  LTP        0)
> > (XEN) ACPI: FACP BFDD0000, 00F4 (r3 INTEL  CRESTLNE  6040000 ALAN        1)
> > (XEN) ACPI: DSDT BFDD1000, CC0A (r2 IEC    Z118M4A   6040000 INTL 20050624)
> > (XEN) ACPI: FACS BFD8EFC0, 0040
> > (XEN) ACPI: HPET BFDFCCD3, 0038 (r1 INTEL  CRESTLNE  6040000 LOHR       5A)
> > (XEN) ACPI: MCFG BFDFCD0B, 003C (r1 INTEL  CRESTLNE  6040000 LOHR       5A)
> > (XEN) ACPI: SLIC BFDFCD47, 0176 (r1 FSC    PC        6040000 PTL_        0)
> > (XEN) ACPI: APIC BFDFCEBD, 0068 (r1 PTLTD        APIC    6040000  LTP       
> >  0)
> > (XEN) ACPI: BOOT BFDFCF25, 0028 (r1 PTLTD  $SBFTBL$  6040000  LTP        1)
> > (XEN) ACPI: SPCR BFDFCF4D, 0050 (r1 PTLTD  $UCRTBL$  6040000 PTL         1)
> > (XEN) ACPI: ASF! BFDFCF9D, 0063 (r16   CETP     CETP  6040000 PTL         1)
> > (XEN) ACPI: TCPA BFDDF000, 0032 (r0                        0             0)
> > (XEN) ACPI: DMAR BFDDE000, 00D8 (r1                       1             0)
> > (XEN) ACPI: SSDT BFDCF000, 0655 (r1  PmRef    CpuPm     3000 INTL 20050624)
> > (XEN) ACPI: SSDT BFDCE000, 0259 (r1  PmRef  Cpu0Tst     3000 INTL 20050624)
> > (XEN) ACPI: SSDT BFDCD000, 020F (r1  PmRef    ApTst     3000 INTL 20050624)
> > (XEN) System RAM: 8086MB (8280272kB)
> > (XEN) NUMA turned off
> > (XEN) Faking a node at 0000000000000000-000000023c000000
> > (XEN) Domain heap initialised
> > (XEN) found SMP MP-table at 000f6300
> > (XEN) DMI 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[bfd8efcc], vec_size[20]
> > (XEN) ACPI: Local APIC address 0xfee00000
> > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> > (XEN) Processor #0 7:7 APIC version 20
> > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> > (XEN) Processor #1 7:7 APIC version 20
> > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> > (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> > (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
> > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
> > (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: 0x8086a201 base: 0xfed00000
> > (XEN) [VT-D]dmar.c:535: Host address width 36
> > (XEN) [VT-D]dmar.c:544: found ACPI_DMAR_DRHD
> > (XEN) [VT-D]dmar.c:374: dmaru->address = feb03000
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0
> > (XEN) [VT-D]dmar.c:544: found ACPI_DMAR_DRHD
> > (XEN) [VT-D]dmar.c:374: dmaru->address = feb00000
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:3.0
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:3.2
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:3.3
> > (XEN) [VT-D]dmar.c:544: found ACPI_DMAR_DRHD
> > (XEN) [VT-D]dmar.c:374: dmaru->address = feb02000
> > (XEN) [VT-D]dmar.c:386: found INCLUDE_ALL
> > (XEN) [VT-D]dmar.c:548: found ACPI_DMAR_RMRR
> > (XEN) [VT-D]dmar.c:429: RMRR address range not in reserved memory base = 
> > fe326c00 end = fe3273ff; iommu_inclusive_mapping=1 parameter may be needed.
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
> > (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
> > (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 2793.072 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) xsave_init: cpu0: cntxt_max_size: 0x240 and states: 00000000:00000003
> > (XEN) xsave_init: using cntxt_size: 0x240 and states: 00000000:00000003
> > (XEN) Intel machine check reporting enabled on CPU#0.
> > (XEN) CPU0: Thermal monitoring enabled (TM2)
> > (XEN) CMCI: CPU0 has no CMCI support
> > (XEN) [VT-D]iommu.c:1774: DMAR: Forcing write-buffer flush
> > (XEN) [VT-D]iommu.c:1016: drhd->address = feb00000
> > (XEN) [VT-D]iommu.c:1017: iommu->reg = ffff82c3fff57000
> > (XEN) [VT-D]iommu.c:1016: drhd->address = feb03000
> > (XEN) [VT-D]iommu.c:1017: iommu->reg = ffff82c3fff56000
> > (XEN) [VT-D]iommu.c:1016: drhd->address = feb02000
> > (XEN) [VT-D]iommu.c:1017: iommu->reg = ffff82c3fff55000
> > (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) CPU0: Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz 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) xsave_init: cpu1: cntxt_max_size: 0x240 and states: 00000000:00000003
> > (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 Duo CPU     T9600  @ 2.80GHz stepping 0a
> > (XEN) Total of 2 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 2 CPUs: passed.
> > (XEN) Platform timer is 14.318MHz HPET
> > (XEN) Brought up 2 CPUs
> > (XEN) microcode.c:73:d32767 microcode: CPU1 resumed
> > (XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
> > (XEN) ACPI sleep modes: S3
> > (XEN) mcheck_poll: Machine check polling timer started.
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:0.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:0.0:  no extended config
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:3.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:3.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:3.2
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:3.2:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:3.3
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:3.3:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:19.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:19.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.1:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.2:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.7:  no extended config
> > (XEN) [VT-D]iommu.c:1247:d32767 domain_context_mapping:PCIe: bdf = 0:1b.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1b.0:  no extended config
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1c.0:  no extended config
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1c.1:  no extended config
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1c.2:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.1:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.2:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.7:  no extended config
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1e.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1f.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1f.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1f.2
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1f.2:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1f.3
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1f.3:  no extended config
> > (XEN) [VT-D]iommu.c:1247:d32767 domain_context_mapping:PCIe: bdf = 1:0.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:1:0.0:  no extended config
> > (XEN) [VT-D]iommu.c:1247:d32767 domain_context_mapping:PCIe: bdf = 5:0.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:5:0.0:  no extended config
> > (XEN) [VT-D]iommu.c:1247:d32767 domain_context_mapping:PCIe: bdf = 8:0.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:8:0.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 11:6.0
> > (XEN) [VT-D]mmconfig-shared.c:460: next cap:11:6.0:  no extended config
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
> > (XEN) [VT-D]iommu.c:1254:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
> > (XEN) [VT-D]iommu.c:638: iommu_enable_translation: iommu->reg = 
> > ffff82c3fff57000
> > (XEN) [VT-D]iommu.c:638: iommu_enable_translation: iommu->reg = 
> > ffff82c3fff56000
> > (XEN) [VT-D]iommu.c:638: iommu_enable_translation: iommu->reg = 
> > ffff82c3fff55000
> >
> >
> > --
> > Company details: http://ts.fujitsu.com/imprint.html
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
> 
> Try adding iommu_inclusive_mapping=1  to your xen boot arguments.
> 
> Andy

Thanks this worked!
I didn't search enough. After your hint I found lots of mails discussing this 
issue :-(
Sorry for the noise.
Dietmar.

> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
-- 
Company details: http://ts.fujitsu.com/imprint.html

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