Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

Hi,

I have cloned the latest xen 3,4 testing tree, changeset 19696:
	22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
table), and i have installed it on a Lenovo T500 machine, with VT-d
enabled.

When i rebooted the machine, and try to boot xen with 'iommu=1' it
hangs during boot.  If i try to boot it with 'iommu=0', it boots ok.

These are the last lines of the UART output:
(XEN) Command line: console=com1 com1=115200,8n1 iommu=1 loglvl=all
guest_loglvl=all
(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 - 000000000009ac00 (usable)
(XEN)  000000000009ac00 - 00000000000a0000 (reserved)
(XEN)  00000000000d6000 - 00000000000d8000 (reserved)
(XEN)  00000000000dc000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007c4a1000 (usable)
(XEN)  000000007c4a1000 - 000000007c4a7000 (reserved)
(XEN)  000000007c4a7000 - 000000007c5b7000 (usable)
(XEN)  000000007c5b7000 - 000000007c60f000 (reserved)
(XEN)  000000007c60f000 - 000000007c6c6000 (usable)
(XEN)  000000007c6c6000 - 000000007c6d1000 (ACPI NVS)
(XEN)  000000007c6d1000 - 000000007c6d4000 (ACPI data)
(XEN)  000000007c6d4000 - 000000007c6d8000 (reserved)
(XEN)  000000007c6d8000 - 000000007c6dc000 (ACPI NVS)
(XEN)  000000007c6dc000 - 000000007c6df000 (reserved)
(XEN)  000000007c6df000 - 000000007c706000 (ACPI NVS)
(XEN)  000000007c706000 - 000000007c708000 (ACPI data)
(XEN)  000000007c708000 - 000000007c90f000 (reserved)
(XEN)  000000007c90f000 - 000000007c99f000 (ACPI NVS)
(XEN)  000000007c99f000 - 000000007c9ff000 (ACPI data)
(XEN)  000000007c9ff000 - 000000007ca00000 (usable)
(XEN)  000000007cc00000 - 000000007f000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fed00000 - 00000000fed00400 (reserved)
(XEN)  00000000fed10000 - 00000000fed14000 (reserved)
(XEN)  00000000fed18000 - 00000000fed1a000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed90000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff800000 - 0000000100000000 (reserved)
(XEN) System RAM: 1990MB (2037772kB)
(XEN) ACPI: RSDP 000F6530, 0024 (r2 LENOVO)
(XEN) ACPI: XSDT 7C96A4DE, 009C (r1 LENOVO TP-6F        1160  LTP        0)
(XEN) ACPI: FACP 7C96A600, 00F4 (r3 LENOVO TP-6F        1160 LNVO        1)
(XEN) ACPI: DSDT 7C96A9DB, F190 (r1 LENOVO TP-6F        1160 MSFT  3000000)
(XEN) ACPI: FACS 7C98E000, 0040
(XEN) ACPI: SSDT 7C96A7B4, 0227 (r1 LENOVO TP-6F        1160 MSFT  3000000)
(XEN) ACPI: ECDT 7C979B6B, 0052 (r1 LENOVO TP-6F        1160 LNVO        1)
(XEN) ACPI: APIC 7C979BBD, 0078 (r1 LENOVO TP-6F        1160 LNVO        1)
(XEN) ACPI: MCFG 7C979C35, 003C (r1 LENOVO TP-6F        1160 LNVO        1)
(XEN) ACPI: HPET 7C979C71, 0038 (r1 LENOVO TP-6F        1160 LNVO        1)
(XEN) ACPI: SLIC 7C979DC2, 0176 (r1 LENOVO TP-6F        1160  LTP        0)
(XEN) ACPI: BOOT 7C979F38, 0028 (r1 LENOVO TP-6F        1160  LTP        1)
(XEN) ACPI: ASF! 7C979F60, 00A0 (r16 LENOVO TP-6F        1160 PTL         1)
(XEN) ACPI: SSDT 7C98D213, 054F (r1 LENOVO TP-6F        1160 INTL 20050513)
(XEN) ACPI: TCPA 7C707000, 0032 (r0                        0             0)
(XEN) ACPI: DMAR 7C706000, 0120 (r1               \x01        1             0)
(XEN) ACPI: SSDT 7C6D3000, 0655 (r1  PmRef    CpuPm     3000 INTL 20050624)
(XEN) ACPI: SSDT 7C6D2000, 0274 (r1  PmRef  Cpu0Tst     3000 INTL 20050624)
(XEN) ACPI: SSDT 7C6D1000, 0242 (r1  PmRef    ApTst     3000 INTL 20050624)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000007ca00000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000f6570
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x1008
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[1004,0], pm1x_evt[1000,0]
(XEN) ACPI:                  wakeup_vec[7c98e00c], 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 (acpi_id[0x02] lapic_id[0x02] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
(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[0x01] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 1, 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: 0x8086a201 base: 0xfed00000
(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 = feb03000
(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 = feb01000
(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 = feb00000
(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 = feb02000
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base
= fc326c00 end = fc3273ff; iommu_inclusive_mapping=1 parameter may be
needed.
(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: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 2394.064 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(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) mce_init: init bank3
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz stepping 06
(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: 3072K
(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 Duo CPU     P8600  @ 2.40GHz stepping 06
(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) [VT-D]iommu.c:1761: DMAR: Forcing write-buffer flush
(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) 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:1252:d32767 domain_context_mapping:PCI: bdf = 0:0.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:2.1
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:3.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:3.2
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:3.3
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:19.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1245:d32767 domain_context_mapping:PCIe: bdf = 0:1b.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1f.0
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf = 0:1f.2
(XEN) [VT-D]iommu.c:1252:d32767 domain_context_mapping:PCI: bdf =


This is the output of 'lspci' on my machine:

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series
Chipset MEI Controller (rev 07)
00:03.2 IDE interface: Intel Corporation Mobile 4 Series Chipset PT
IDER Controller (rev 07)
00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset
AMT SOL Redirection (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network
Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2
EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2
EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN
[Shiloh] Network Connection
04:00.0 Memory controller: Intel Corporation Turbo Memory Controller (rev 11)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro
Host Adapter (rev 21)
15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host
Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)

Can someone please help me with this?

Tom

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Keir Fraser]

On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:

> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
> table), and i have installed it on a Lenovo T500 machine, with VT-d
> enabled.

When did it last work with the 3.4 tree?

 -- Keir

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

The last version, i have tried and tested (and it worked), was:

changeset 19607: 1ac7832a2fcd
author: Keir Fraser <keir.fraser@citrix.com>
date: Mon May 18 13:54:48 2009 +0100
files: README


On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>
>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>> enabled.
>
> When did it last work with the 3.4 tree?
>
>  -- Keir
>
>
>

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Keir Fraser]

I'd say changesets 19625 and 19632 are most likely suspects. You could try
reverting those patches, or updating your tree to just before those
changesets, and see if that helps.

 -- Keir

On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:

> The last version, i have tried and tested (and it worked), was:
> 
> changeset 19607: 1ac7832a2fcd
> author: Keir Fraser <keir.fraser@citrix.com>
> date: Mon May 18 13:54:48 2009 +0100
> files: README
> 
> 
> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>> 
>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>> enabled.
>> 
>> When did it last work with the 3.4 tree?
>> 
>>  -- Keir
>> 
>> 
>> 

[Patch][SVM]Disable intercepting CR3 writes when nested paging is enabled

[Wei Huang]

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

This patch disables intercepting CR3 writes when nested paging is 
enabled. For applications which cause excessive CR3 accesses, the patch 
can increases their performance.

Signed-off-by: Wei Huang <wei.huang2@amd.com>

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

diff -r c31edc59ae5d xen/arch/x86/hvm/svm/svm.c
--- a/xen/arch/x86/hvm/svm/svm.c	Sat Jul 25 19:31:35 2009 -0500
+++ b/xen/arch/x86/hvm/svm/svm.c	Sat Jul 25 19:31:51 2009 -0500
@@ -1299,6 +1299,8 @@ asmlinkage void svm_vmexit_handler(struc
     eventinj_t eventinj;
     int inst_len, rc;
 
+    if ( paging_mode_hap(v->domain) )
+        v->arch.hvm_vcpu.guest_cr[3] = v->arch.hvm_vcpu.hw_cr[3] = vmcb->cr3;
     /*
      * Before doing anything else, we need to sync up the VLAPIC's TPR with
      * SVM's vTPR. It's OK if the guest doesn't touch CR8 (e.g. 32-bit Windows)
diff -r c31edc59ae5d xen/arch/x86/hvm/svm/vmcb.c
--- a/xen/arch/x86/hvm/svm/vmcb.c	Sat Jul 25 19:31:35 2009 -0500
+++ b/xen/arch/x86/hvm/svm/vmcb.c	Sat Jul 25 19:31:51 2009 -0500
@@ -236,10 +236,10 @@ static int construct_vmcb(struct vcpu *v
         vmcb->h_cr3 = pagetable_get_paddr(v->domain->arch.phys_table);
 
         /*
-         * No point in intercepting CR3 reads, because the hardware will return
-         * the guest version anyway.
+         * No point in intercepting CR3 reads/writes
          */
         vmcb->cr_intercepts &= ~CR_INTERCEPT_CR3_READ;
+        vmcb->cr_intercepts &= ~CR_INTERCEPT_CR3_WRITE;
 
         /*
          * No point in intercepting INVLPG if we don't have shadow pagetables

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

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

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

It didn't help.
I will bisect the tree to find the problem.

On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
> I'd say changesets 19625 and 19632 are most likely suspects. You could try
> reverting those patches, or updating your tree to just before those
> changesets, and see if that helps.
>
>  -- Keir
>
> On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>
>> The last version, i have tried and tested (and it worked), was:
>>
>> changeset 19607: 1ac7832a2fcd
>> author: Keir Fraser <keir.fraser@citrix.com>
>> date: Mon May 18 13:54:48 2009 +0100
>> files: README
>>
>>
>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>
>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>>> enabled.
>>>
>>> When did it last work with the 3.4 tree?
>>>
>>>  -- Keir
>>>
>>>
>>>
>
>
>

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

Just bisected the tree, and i found out, that it's not because of Xen,
since even 19607 (which worked for me last time) didn't work. I tried
to play a little bit with some of the BIOS settings, but it didn't
help.
It looks like it's some kind of an hardware problem, which causes the
whole machine to freeze, when trying to work with the IOMMU. Any
suggestions on what to do next? to whom should i send this
information?

Tom

On Thu, Jul 16, 2009 at 11:26 AM, Tom Rotenberg<tom.rotenberg@gmail.com> wrote:
> It didn't help.
> I will bisect the tree to find the problem.
>
> On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>> I'd say changesets 19625 and 19632 are most likely suspects. You could try
>> reverting those patches, or updating your tree to just before those
>> changesets, and see if that helps.
>>
>>  -- Keir
>>
>> On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>
>>> The last version, i have tried and tested (and it worked), was:
>>>
>>> changeset 19607: 1ac7832a2fcd
>>> author: Keir Fraser <keir.fraser@citrix.com>
>>> date: Mon May 18 13:54:48 2009 +0100
>>> files: README
>>>
>>>
>>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>>>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>
>>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>>>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>>>> enabled.
>>>>
>>>> When did it last work with the 3.4 tree?
>>>>
>>>>  -- Keir
>>>>
>>>>
>>>>
>>
>>
>>
>

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Keir Fraser]

Did you upgrade the BIOS since your last successful test? There have been
problems which can persist across warm reboots. So did you power cycle
between tests?

 -- Keir

On 16/07/2009 10:54, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:

> Just bisected the tree, and i found out, that it's not because of Xen,
> since even 19607 (which worked for me last time) didn't work. I tried
> to play a little bit with some of the BIOS settings, but it didn't
> help.
> It looks like it's some kind of an hardware problem, which causes the
> whole machine to freeze, when trying to work with the IOMMU. Any
> suggestions on what to do next? to whom should i send this
> information?
> 
> Tom
> 
> On Thu, Jul 16, 2009 at 11:26 AM, Tom Rotenberg<tom.rotenberg@gmail.com>
> wrote:
>> It didn't help.
>> I will bisect the tree to find the problem.
>> 
>> On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>> wrote:
>>> I'd say changesets 19625 and 19632 are most likely suspects. You could try
>>> reverting those patches, or updating your tree to just before those
>>> changesets, and see if that helps.
>>> 
>>>  -- Keir
>>> 
>>> On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>> 
>>>> The last version, i have tried and tested (and it worked), was:
>>>> 
>>>> changeset 19607: 1ac7832a2fcd
>>>> author: Keir Fraser <keir.fraser@citrix.com>
>>>> date: Mon May 18 13:54:48 2009 +0100
>>>> files: README
>>>> 
>>>> 
>>>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>> wrote:
>>>>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>> 
>>>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>>>>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>>>>> enabled.
>>>>> 
>>>>> When did it last work with the 3.4 tree?
>>>>> 
>>>>>  -- Keir
>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
>>> 
>> 

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

No...
and i remember that there was a problem of warm boots, so i did a cold
boot. It's really strange, i have no clew about what can cause it...
I did 'make install' on a clean repository. There is no chance it had
any "left-overs", right?

On Thu, Jul 16, 2009 at 1:00 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
> Did you upgrade the BIOS since your last successful test? There have been
> problems which can persist across warm reboots. So did you power cycle
> between tests?
>
>  -- Keir
>
> On 16/07/2009 10:54, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>
>> Just bisected the tree, and i found out, that it's not because of Xen,
>> since even 19607 (which worked for me last time) didn't work. I tried
>> to play a little bit with some of the BIOS settings, but it didn't
>> help.
>> It looks like it's some kind of an hardware problem, which causes the
>> whole machine to freeze, when trying to work with the IOMMU. Any
>> suggestions on what to do next? to whom should i send this
>> information?
>>
>> Tom
>>
>> On Thu, Jul 16, 2009 at 11:26 AM, Tom Rotenberg<tom.rotenberg@gmail.com>
>> wrote:
>>> It didn't help.
>>> I will bisect the tree to find the problem.
>>>
>>> On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>> wrote:
>>>> I'd say changesets 19625 and 19632 are most likely suspects. You could try
>>>> reverting those patches, or updating your tree to just before those
>>>> changesets, and see if that helps.
>>>>
>>>>  -- Keir
>>>>
>>>> On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>
>>>>> The last version, i have tried and tested (and it worked), was:
>>>>>
>>>>> changeset 19607: 1ac7832a2fcd
>>>>> author: Keir Fraser <keir.fraser@citrix.com>
>>>>> date: Mon May 18 13:54:48 2009 +0100
>>>>> files: README
>>>>>
>>>>>
>>>>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>>> wrote:
>>>>>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>>>
>>>>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>>>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>>>>>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>>>>>> enabled.
>>>>>>
>>>>>> When did it last work with the 3.4 tree?
>>>>>>
>>>>>>  -- Keir
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>
>
>
>

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Keir Fraser]

Well, I would 'make clean' in the xen/ subdirectory just to be sure at this
point. But no, it doesn't really sound like a software issue. Have you tried
iommu_inclusive_mapping Xen boot parameter?

 -- Keir

On 16/07/2009 11:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:

> No...
> and i remember that there was a problem of warm boots, so i did a cold
> boot. It's really strange, i have no clew about what can cause it...
> I did 'make install' on a clean repository. There is no chance it had
> any "left-overs", right?
> 
> On Thu, Jul 16, 2009 at 1:00 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>> Did you upgrade the BIOS since your last successful test? There have been
>> problems which can persist across warm reboots. So did you power cycle
>> between tests?
>> 
>>  -- Keir
>> 
>> On 16/07/2009 10:54, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>> 
>>> Just bisected the tree, and i found out, that it's not because of Xen,
>>> since even 19607 (which worked for me last time) didn't work. I tried
>>> to play a little bit with some of the BIOS settings, but it didn't
>>> help.
>>> It looks like it's some kind of an hardware problem, which causes the
>>> whole machine to freeze, when trying to work with the IOMMU. Any
>>> suggestions on what to do next? to whom should i send this
>>> information?
>>> 
>>> Tom
>>> 
>>> On Thu, Jul 16, 2009 at 11:26 AM, Tom Rotenberg<tom.rotenberg@gmail.com>
>>> wrote:
>>>> It didn't help.
>>>> I will bisect the tree to find the problem.
>>>> 
>>>> On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>> wrote:
>>>>> I'd say changesets 19625 and 19632 are most likely suspects. You could try
>>>>> reverting those patches, or updating your tree to just before those
>>>>> changesets, and see if that helps.
>>>>> 
>>>>>  -- Keir
>>>>> 
>>>>> On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>> 
>>>>>> The last version, i have tried and tested (and it worked), was:
>>>>>> 
>>>>>> changeset 19607: 1ac7832a2fcd
>>>>>> author: Keir Fraser <keir.fraser@citrix.com>
>>>>>> date: Mon May 18 13:54:48 2009 +0100
>>>>>> files: README
>>>>>> 
>>>>>> 
>>>>>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>>>> wrote:
>>>>>>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>>>> 
>>>>>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>>>>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2
>>>>>>>> page
>>>>>>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>>>>>>> enabled.
>>>>>>> 
>>>>>>> When did it last work with the 3.4 tree?
>>>>>>> 
>>>>>>>  -- Keir
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>> 
>> 
>> 

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

Oops!!
That's what i forgot!!! i'll try it now.

Thanks :)

On Thu, Jul 16, 2009 at 1:10 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
> Well, I would 'make clean' in the xen/ subdirectory just to be sure at this
> point. But no, it doesn't really sound like a software issue. Have you tried
> iommu_inclusive_mapping Xen boot parameter?
>
>  -- Keir
>
> On 16/07/2009 11:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>
>> No...
>> and i remember that there was a problem of warm boots, so i did a cold
>> boot. It's really strange, i have no clew about what can cause it...
>> I did 'make install' on a clean repository. There is no chance it had
>> any "left-overs", right?
>>
>> On Thu, Jul 16, 2009 at 1:00 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>>> Did you upgrade the BIOS since your last successful test? There have been
>>> problems which can persist across warm reboots. So did you power cycle
>>> between tests?
>>>
>>>  -- Keir
>>>
>>> On 16/07/2009 10:54, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>
>>>> Just bisected the tree, and i found out, that it's not because of Xen,
>>>> since even 19607 (which worked for me last time) didn't work. I tried
>>>> to play a little bit with some of the BIOS settings, but it didn't
>>>> help.
>>>> It looks like it's some kind of an hardware problem, which causes the
>>>> whole machine to freeze, when trying to work with the IOMMU. Any
>>>> suggestions on what to do next? to whom should i send this
>>>> information?
>>>>
>>>> Tom
>>>>
>>>> On Thu, Jul 16, 2009 at 11:26 AM, Tom Rotenberg<tom.rotenberg@gmail.com>
>>>> wrote:
>>>>> It didn't help.
>>>>> I will bisect the tree to find the problem.
>>>>>
>>>>> On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>>> wrote:
>>>>>> I'd say changesets 19625 and 19632 are most likely suspects. You could try
>>>>>> reverting those patches, or updating your tree to just before those
>>>>>> changesets, and see if that helps.
>>>>>>
>>>>>>  -- Keir
>>>>>>
>>>>>> On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>>>
>>>>>>> The last version, i have tried and tested (and it worked), was:
>>>>>>>
>>>>>>> changeset 19607: 1ac7832a2fcd
>>>>>>> author: Keir Fraser <keir.fraser@citrix.com>
>>>>>>> date: Mon May 18 13:54:48 2009 +0100
>>>>>>> files: README
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>>>>> wrote:
>>>>>>>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>>>>>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2
>>>>>>>>> page
>>>>>>>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>>>>>>>> enabled.
>>>>>>>>
>>>>>>>> When did it last work with the 3.4 tree?
>>>>>>>>
>>>>>>>>  -- Keir
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>
>>>
>>>
>
>
>

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

Well, it worked!
Thanks!

On Thu, Jul 16, 2009 at 1:14 PM, Tom Rotenberg<tom.rotenberg@gmail.com> wrote:
> Oops!!
> That's what i forgot!!! i'll try it now.
>
> Thanks :)
>
> On Thu, Jul 16, 2009 at 1:10 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>> Well, I would 'make clean' in the xen/ subdirectory just to be sure at this
>> point. But no, it doesn't really sound like a software issue. Have you tried
>> iommu_inclusive_mapping Xen boot parameter?
>>
>>  -- Keir
>>
>> On 16/07/2009 11:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>
>>> No...
>>> and i remember that there was a problem of warm boots, so i did a cold
>>> boot. It's really strange, i have no clew about what can cause it...
>>> I did 'make install' on a clean repository. There is no chance it had
>>> any "left-overs", right?
>>>
>>> On Thu, Jul 16, 2009 at 1:00 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>>>> Did you upgrade the BIOS since your last successful test? There have been
>>>> problems which can persist across warm reboots. So did you power cycle
>>>> between tests?
>>>>
>>>>  -- Keir
>>>>
>>>> On 16/07/2009 10:54, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>
>>>>> Just bisected the tree, and i found out, that it's not because of Xen,
>>>>> since even 19607 (which worked for me last time) didn't work. I tried
>>>>> to play a little bit with some of the BIOS settings, but it didn't
>>>>> help.
>>>>> It looks like it's some kind of an hardware problem, which causes the
>>>>> whole machine to freeze, when trying to work with the IOMMU. Any
>>>>> suggestions on what to do next? to whom should i send this
>>>>> information?
>>>>>
>>>>> Tom
>>>>>
>>>>> On Thu, Jul 16, 2009 at 11:26 AM, Tom Rotenberg<tom.rotenberg@gmail.com>
>>>>> wrote:
>>>>>> It didn't help.
>>>>>> I will bisect the tree to find the problem.
>>>>>>
>>>>>> On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>>>> wrote:
>>>>>>> I'd say changesets 19625 and 19632 are most likely suspects. You could try
>>>>>>> reverting those patches, or updating your tree to just before those
>>>>>>> changesets, and see if that helps.
>>>>>>>
>>>>>>>  -- Keir
>>>>>>>
>>>>>>> On 15/07/2009 18:03, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>>>>
>>>>>>>> The last version, i have tried and tested (and it worked), was:
>>>>>>>>
>>>>>>>> changeset 19607: 1ac7832a2fcd
>>>>>>>> author: Keir Fraser <keir.fraser@citrix.com>
>>>>>>>> date: Mon May 18 13:54:48 2009 +0100
>>>>>>>> files: README
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com>
>>>>>>>> wrote:
>>>>>>>>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>>>>>>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2
>>>>>>>>>> page
>>>>>>>>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>>>>>>>>> enabled.
>>>>>>>>>
>>>>>>>>> When did it last work with the 3.4 tree?
>>>>>>>>>
>>>>>>>>>  -- Keir
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>

RE: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Cui, Dexuan]

Hi Tom,
Please add a xen parameter (not a dom0 parameter) "iommu_inclusive_mapping=1" to see if it still hangs.

Thanks,
-- Dexuan



-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tom Rotenberg
Sent: 2009?7?16? 1:03
To: Keir Fraser
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

The last version, i have tried and tested (and it worked), was:

changeset 19607: 1ac7832a2fcd
author: Keir Fraser <keir.fraser@citrix.com>
date: Mon May 18 13:54:48 2009 +0100
files: README


On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>
>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>> enabled.
>
> When did it last work with the 3.4 tree?
>
>  -- Keir
>
>
>

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

Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500

[Tom Rotenberg]

Keir already told me to do it, and it worked.
Thanks!

On Thu, Jul 16, 2009 at 3:08 PM, Cui, Dexuan<dexuan.cui@intel.com> wrote:
> Hi Tom,
> Please add a xen parameter (not a dom0 parameter) "iommu_inclusive_mapping=1" to see if it still hangs.
>
> Thanks,
> -- Dexuan
>
>
>
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tom Rotenberg
> Sent: 2009?7?16? 1:03
> To: Keir Fraser
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500
>
> The last version, i have tried and tested (and it worked), was:
>
> changeset 19607: 1ac7832a2fcd
> author: Keir Fraser <keir.fraser@citrix.com>
> date: Mon May 18 13:54:48 2009 +0100
> files: README
>
>
> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser<keir.fraser@eu.citrix.com> wrote:
>> On 15/07/2009 17:01, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>>
>>> I have cloned the latest xen 3,4 testing tree, changeset 19696:
>>>         22ef8e900a6d (i386: fix handling of Xen entries in final L2 page
>>> table), and i have installed it on a Lenovo T500 machine, with VT-d
>>> enabled.
>>
>> When did it last work with the 3.4 tree?
>>
>>  -- Keir
>>
>>
>>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>