WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: [Xen-devel] xen 3.4.1 fails to boot with iommu=1 on d5400xs intel sk

from [c4pt] [Permanent Link][Original]
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] xen 3.4.1 fails to boot with iommu=1 on d5400xs intel skulltrail using e5410 xeon cpus http://www.pa
From: c4pt <c4pt4inkrunch@xxxxxxxxx>
Date: Mon, 31 Aug 2009 12:46:41 -0700 (PDT)
Delivery-date: Mon, 31 Aug 2009 12:47:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EADF0A36011179459010BDF5142A457501CD7F16A7@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <0016362843028e5113047261e5cc@xxxxxxxxxx> <EADF0A36011179459010BDF5142A457501CD7F16A7@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
doesnt seem to work weather i power cycle or not after choosing vt and vt-d
in the bios




Cui, Dexuan wrote:
> 
> 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
> 
> ________________________________
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> c4pt4inkrunch@xxxxxxxxx
> Sent: 2009?8?31? 4:38
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] xen 3.4.1 fails to boot with iommu=1 on d5400xs intel
> skulltrail using e5410 xeon cpus http://www.pa
> 
> hello i am trying to boot xen on a intel skulltrail d5400xs motherboard
> with two xeon e5410 cpus running ubuntu i386 9.04
> 
> here is the serial console output
> 
> 
> 
> 
> 
> __ __ _____ _ _ _
> \ \/ /___ _ __ |___ /| || | / |
> \ // _ \ '_ \ |_ \| || |_ | |
> / \ __/ | | | ___) |__ _|| |
> /_/\_\___|_| |_| |____(_) |_|(_)_|
> 
> (XEN) Xen version 3.4.1 (root@) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
> ) Thu Aug 27 19:02:10 EDT 2009
> (XEN) Latest ChangeSet: unavailable
> (XEN) Command line: console=com1 com1=115200,8n1,0x1030,18 iommu=1
> iommu=passthrough iommu_inclusive_mapping=1 noreboot
> (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 4 MBR signatures
> (XEN) Found 4 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN) 0000000000000000 - 000000000009e000 (usable)
> (XEN) 000000000009e000 - 00000000000a0000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 000000007ecca000 (usable)
> (XEN) 000000007ecca000 - 000000007ed44000 (ACPI NVS)
> (XEN) 000000007ed44000 - 000000007fdb2000 (usable)
> (XEN) 000000007fdb2000 - 000000007fdb4000 (reserved)
> (XEN) 000000007fdb4000 - 000000007fe72000 (usable)
> (XEN) 000000007fe72000 - 000000007fee5000 (ACPI NVS)
> (XEN) 000000007fee5000 - 000000007fee8000 (usable)
> (XEN) 000000007fee8000 - 000000007fef2000 (ACPI data)
> (XEN) 000000007fef2000 - 000000007fef3000 (usable)
> (XEN) 000000007fef3000 - 000000007feff000 (ACPI data)
> (XEN) 000000007feff000 - 000000007ff00000 (usable)
> (XEN) 000000007ff00000 - 0000000080000000 (reserved)
> (XEN) 00000000f0000000 - 00000000f8000000 (reserved)
> (XEN) 00000000ffe00000 - 0000000100000000 (reserved)
> (XEN) System RAM: 2045MB (2094692kB)
> (XEN) ACPI: RSDP 000FE020, 0014 (r0 INTEL )
> (XEN) ACPI: RSDT 7FEFD038, 0064 (r1 INTEL D5400XS 549 1000013)
> (XEN) ACPI: FACP 7FEFC000, 0074 (r1 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: DSDT 7FEF8000, 3C26 (r1 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: FACS 7FE7D000, 0040
> (XEN) ACPI: APIC 7FEF7000, 00D4 (r1 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: WDDT 7FEF6000, 0040 (r1 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: MCFG 7FEF5000, 003C (r1 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: ASF! 7FEF4000, 00A7 (r32 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: HPET 7FEF3000, 0038 (r1 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: DMAR 7FEF1000, 00C8 (r1 INTEL D5400XS 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEF0000, 03CC (r1 INTEL CpuPm 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEEF000, 00DD (r1 INTEL Cpu0Cst 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEEE000, 00DD (r1 INTEL Cpu1Cst 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEED000, 00DD (r1 INTEL Cpu2Cst 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEEC000, 00DD (r1 INTEL Cpu3Cst 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEEB000, 00DD (r1 INTEL Cpu4Cst 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEEA000, 00DD (r1 INTEL Cpu5Cst 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEE9000, 00DD (r1 INTEL Cpu6Cst 549 MSFT 1000013)
> (XEN) ACPI: SSDT 7FEE8000, 00DD (r1 INTEL Cpu7Cst 549 MSFT 1000013)
> (XEN) Xen heap: 9MB (9784kB)
> (XEN) Domain heap initialised
> (XEN) Processor #0 7:7 APIC version 20
> (XEN) Processor #4 7:7 APIC version 20
> (XEN) Processor #1 7:7 APIC version 20
> (XEN) Processor #5 7:7 APIC version 20
> (XEN) Processor #2 7:7 APIC version 20
> (XEN) Processor #6 7:7 APIC version 20
> (XEN) Processor #3 7:7 APIC version 20
> (XEN) Processor #7 7:7 APIC version 20
> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
> (XEN) IOAPIC[1]: apic_id 9, version 255, address 0xfec88000, GSI 24-279
> (XEN) IOAPIC[2]: apic_id 10, version 255, address 0xfec90000, GSI 48-303
> (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
> (XEN) Intel VT-d DMAR tables have been parsed.
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2327.540 MHz processor.
> (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) CPU0: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Booting processor 1/4 eip 8c000
> (XEN) CPU1: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Booting processor 2/1 eip 8c000
> (XEN) CPU2: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Booting processor 3/5 eip 8c000
> (XEN) CPU3: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Booting processor 4/2 eip 8c000
> (XEN) CPU4: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Booting processor 5/6 eip 8c000
> (XEN) CPU5: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Booting processor 6/3 eip 8c000
> (XEN) CPU6: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Booting processor 7/7 eip 8c000
> (XEN) CPU7: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping 06
> (XEN) Total of 8 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) -> Using new ACK method
> (XEN) checking TSC synchronization across 8 CPUs: passed.
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Brought up 8 CPUs
> (XEN) Intel VT-d Snoop Control supported.
> (XEN) Intel VT-d DMA Passthrough supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping supported.
> (XEN) ----[ Xen-3.4.1 x86_32p debug=n Not tainted ]----
> (XEN) CPU: 0
> (XEN) EIP: e008:[<ff1288ad>] clear_fault_bits+0x2d/0xc0
> (XEN) EFLAGS: 00010206 CONTEXT: hypervisor
> (XEN) eax: fff7aff8 ebx: 00000000 ecx: ffffffff edx: ffffffff
> (XEN) esi: 00000098 edi: ffbcc858 ebp: fff77000 esp: ff227e0c
> (XEN) cr0: 8005003b cr4: 000026f0 cr3: 00100120 cr2: fff7aff8
> (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008
> (XEN) Xen stack trace from esp=ff227e0c:
> (XEN) 00000098 00000098 ffbcc858 ffbcc884 ff12971b ffbcc858 00000246
> 00000000
> (XEN) ff1c53bc ffbcc858 00000000 ff1c53d4 ff227e6c 00004c00 ff272660
> 00000206
> (XEN) ff1c9fd6 ff1c9fd6 ffbb8008 00000001 ff129f39 00008000 00000004
> ff1c9fd6
> (XEN) 00000000 ff203100 329ca2a5 00000009 00000000 00000000 ffffffff
> 00000000
> (XEN) ffffffff ff1d5fa0 ff1d605c 00000010 ff272df4 00000020 0000001f
> 00000000
> (XEN) ffffffed 00000000 00000007 00000167 ff126b96 ff1d5fa0 ff117e80
> ff202c2c
> (XEN) ff1f69d5 00000020 00000008 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 013e6bc4 00000000
> 00000000
> (XEN) ff1e6250 ff08bf20 00000001 00000000 00000000 00000000 ffe00000
> 0008bf20
> (XEN) 00000000 00000000 ff08bfc0 013e6bc4 00000000 ffffffff 00000000
> 00000000
> (XEN) 00000000 00000000 ffea6980 ff200c40 ff200ab0 01000000 00000000
> 3ec19000
> (XEN) 00000000 00000000 00000013 00000000 00000000 00000000 00000008
> 0000006e
> (XEN) 00000001 00000003 000002f8 00000000 00000000 001e0e66 ff25bf40
> 00067e2c
> (XEN) ff10006c 0008bfc0 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 ff220000
> (XEN) Xen call trace:
> (XEN) [<ff1288ad>] clear_fault_bits+0x2d/0xc0
> (XEN) [<ff12971b>] init_vtd_hw+0x13b/0x3c0
> (XEN) [<ff129f39>] intel_vtd_setup+0x599/0x600
> (XEN) [<ff126b96>] iommu_setup+0x26/0x100
> (XEN) [<ff117e80>] stopmachine_softirq+0x0/0xa0
> (XEN) [<ff1f69d5>] __start_xen+0xef5/0x1570
> (XEN) [<ff1e6250>] e820nr+0x0/0x4
> (XEN) [<ff10006c>] __high_start+0x58/0x5a
> (XEN)
> (XEN) Pagetable walk from fff7aff8:
> (XEN) L3[0x003] = 000000000022f001 55555555
> (XEN) L2[0x1ff] = 0000000000271063 55555555
> (XEN) L1[0x17a] = 0000000000000000 ffffffff
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: fff7aff8
> (XEN) ****************************************
> (XEN)
> (XEN) Manual reset required ('noreboot' specified)
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 

-- 
View this message in context: 
http://www.nabble.com/xen-3.4.1-fails-to-boot-with-iommu%3D1-on-d5400xs-intel-skulltrail-using-e5410-xeon-cpus-http%3A--www.pa-tp25215520p25229358.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] Xenclient build error for crti.o, Vaghasia, Vinu
Next by Date:  RE: [Xen-devel] write_tsc in a PV domain?, Dan Magenheimer
Previous by Thread:  RE: [Xen-devel] xen 3.4.1 fails to boot with iommu=1 on d5400xs intel skulltrail using e5410 xeon cpus http://www.pa, c4pt
Next by Thread:  [Xen-devel] Biweekly VMX status report. Xen: #20125 & Xen0: #16529..., Xu, Jiajun
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy