Mailing List Archive

[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #3 from darkbasic4@gmail.com 2010-12-09 05:58 -------
Bug is still not fixed with latest debian kernel:
linux-image-2.6.32-5-xen-amd64 2.6.32-28. Please help me.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #4 from konrad.wilk@oracle.com 2010-12-09 09:18 -------
What motherboard? What is the lspci output? Does baremetal Linux kernel boot
with VT-d enabled? Have you tried to boot without x2apic? ("x2apic=off" on Xen
hypervisor line)?


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #5 from darkbasic4@gmail.com 2010-12-11 13:23 -------
I don't think it's a kernel related problem, because the upgrade which broke it
was the hypervisor: from 4.0.1-rc3 to rc5. With rc3 I remember I had a similar
problem with iommu=1, a problem which I solved using iommu=passtrough.

>What motherboard?
Mobo is an Asrock X58 Extreme.

>Does baremetal Linux kernel boot with VT-d enabled?
Yes.

>Have you tried to boot without x2apic? ("x2apic=off" on Xen
hypervisor line)?
No, I will try as soon as possible.

>What is the lspci output?

root@xen-dom0:~# lspci
00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port (rev
13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
Port 1 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
Port 3 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
Port 7 (rev 13)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management
Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad
Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS
Registers (rev 13)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev
13)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio
Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root
Port 1
00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 2
00:1c.3 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root
Port 4
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root
Port 6
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface
Controller
00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE
Controller #1
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE
Controller #2
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 03)
02:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI
Bridge (rev aa)
03:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS
Analog AFT card
04:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire
Controller
04:00.1 IDE interface: VIA Technologies, Inc. PATA IDE Host Controller (rev a0)
05:00.0 SATA controller: JMicron Technology Corp. JMB360 AHCI Controller (rev
02)
06:00.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS
Analog AFT card
06:01.0 ATM network controller: Xilinx Corporation Device 0300
07:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev
04)
08:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev b5)
09:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5714 Gigabit
Ethernet (rev a3)
09:04.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5714 Gigabit
Ethernet (rev a3)
09:08.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (rev b4)
0a:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit
Ethernet (rev 10)
0a:06.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit
Ethernet (rev 10)
0b:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200
TurboCache(TM)] (rev a1)


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #6 from darkbasic4@gmail.com 2010-12-14 16:45 -------
>Have you tried to boot without x2apic? ("x2apic=off" on Xen
>hypervisor line)?

I just tried with x2apic=off, but it didn't solved the problem :(


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644


caz@caztech.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |caz@caztech.com




------- Comment #7 from caz@caztech.com 2010-12-17 05:46 -------
I believe even xen-4.0.0 does not work on ASRock X58 Extreme. I am running
SLES11.1 which runs xen-4.0.0. I have the same symptom. I tryied x2apic=off. No
difference. It seems this is a problem of mobo. Has anyone contacted ASRock?


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #8 from konrad.wilk@oracle.com 2010-12-17 06:54 -------
Can you provide the serial output or 'xm dmesg' with 'iommu=verbose' as
bootline? I am curious to see whether we detect the DMAR (Intel VT-D chipset)
or if it is busted.

You did upgrade to the latest BIOS, right?


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #9 from darkbasic4@gmail.com 2010-12-17 09:26 -------
>I believe even xen-4.0.0 does not work on ASRock X58 Extreme.
It works (or at least it boots flawlessly), you just need to boot with
iommu=passthrough.

>Can you provide the serial output or 'xm dmesg' with 'iommu=verbose' as
>bootline? I am curious to see whether we detect the DMAR (Intel VT-D chipset)
>or if it is busted.
Yes, if the RS232 serial port does work. I will try as soon as possible.

>You did upgrade to the latest BIOS, right?
Yes, when I filed the bug some months ago. In the meantime they released some
new versions, I will try to upgrade the bios once more.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #10 from caz@caztech.com 2010-12-17 20:17 -------
(In reply to comment #9)
> >I believe even xen-4.0.0 does not work on ASRock X58 Extreme.
> It works (or at least it boots flawlessly), you just need to boot with
> iommu=passthrough.
It does. Thank you.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #11 from caz@caztech.com 2010-12-18 12:33 -------
(In reply to comment #9)
> >Can you provide the serial output or 'xm dmesg' with 'iommu=verbose' as
> >bootline? I am curious to see whether we detect the DMAR (Intel VT-D chipset)
> >or if it is busted.
> Yes, if the RS232 serial port does work. I will try as soon as possible.
Here is my one.
[ 5642.577497] Restarting system.
(XEN) Domain 0 shutdown: rebooting machine.
__ __ _ _ ___ ____ _
\ \/ /___ _ __ | || | / _ \ |___ \ _ __ ___/ | _ __ _ __ ___
\ // _ \ '_ \ | || |_| | | | __) |__| '__/ __| |__| '_ \| '__/ _ \
/ \ __/ | | | |__ _| |_| | / __/|__| | | (__| |__| |_) | | | __/
/_/\_\___|_| |_| |_|(_)___(_)_____| |_| \___|_| | .__/|_| \___|
|_|
(XEN) Xen version 4.0.2-rc1-pre (caz@caztech.com) (gcc version 4.3.4
[gcc-4_3-branch revision 152973] (SUSE Linux) ) Sat Dec 18 09:13:05 PST 2010
(XEN) Latest ChangeSet: Thu Dec 09 16:15:55 2010 +0000 21398:116a979f9d0f
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: vga=mode-0x375 com1=115200,8n1 console=vga,com1L gdb=com1H
iommu=passthrough iommu=vergbose
(XEN) Video information:
(XEN) VGA is graphics mode 1600x1200, 16 bpp
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) EDID info not retrieved because of reasons unknown
(XEN) Disc information:
(XEN) Found 3 MBR signatures
(XEN) Found 3 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000097400 (usable)
(XEN) 0000000000097400 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bbe80000 (usable)
(XEN) 0e80000 - 00000000bbe90000 (ACPI data)
(XEN) 00000000bbe90000 - 00000000EN) 00000000bbed0000 - 00000000bbee0000
(reserved)
(XEN) 00000000bbeeb800 - 00000000bc000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 00000001c4000000 (usable)
(XEN) ACPI: RSDP 000FA1F0, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT BBE80000, 0044 (r1 111510 RSDT1542 20101115 MSFT 97)
(XEN) ACPI: FACP BBE80200, 0084 (r1 A_M_I OEM: DSDT BBE80480, 7129 (r1 AS244
AS244263 263 INTL 20051117)
(XEN) ACPI: FACS BBE90000, 0040
(XEN) ACPI: AIC BBE80390, 00AC (r1 111510 APIC1542 20101115 MSFT 97)
(XEN) ACPI: MCFG BBE80440, 003C (r1 111510 OEMMCFG 20101115 MSFT 97)
(XEN) ACPI: OEMB BBE90040, 0073 (r1 111510 OEMB1542 20101115 MSFT 97)
(XEN) ACPI: AAFT BBE8A480, 0027 (r1 111510 OEMAAFT 20101115 MSFT 97)
(XEN) ACPI: HPET BBE8A4B0, 0038 (r1 111510 OEMHPET 20101115 MSFT 97)
(XEN) ACPI: DMAR BBE900C0, 0130 (r1 AMI OEMDMAR 1 MSFT 97)
(XEN) ACPI: SSDT BBE92430, 0363 (r1 DpgPmm CpuPm 12 INTL 20051117)
(XEN) System RAM: 6142MB (6289500kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC version 21
(XEN) Processor #4 7:10 APIC version 21
(XEN) Processor #6 7:10 APIC version 21
(XEN) Processor #1 7:10 APIC version 21
(XEN) Processor #3 7:10 APIC version 21
(XEN) Processor #5 7:10 APIC version 21
(XEN) Processor #7 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) [VT-D]dmar.c:524: RMRR address range not in reserved memory base =
bbeeb800 end = bbefffff; iommu_inclusive_mapping=1 parameter may be needed.
(XEN) Using scheduler: S(XEN) Detected 3135.466 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assiste Passthrough not (XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Total of 8 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
ÿ(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 8 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1bff000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000138000000->000000013c000000 (1503632 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff81bff000
(XEN) Init. ramdisk: ffffffff81bff000->ffffffff82794000
(XEN) Phys-Mach map: ffffffff82794000->ffffffff8332cc80
(XEN) Start info: ffffffff8332d000->ffffffff8332d4b4
(XEN) Page tables: ffffffff8332e000->ffffffff8334b000
(XEN) Boot stack: ffffffff8334b000->ffffffff8334c000
(XEN) TOTAL: ffffffff80000000->ffffffff83400000
(XEN) ENTRY ADDRESS: ffffffff81973200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
Xen)
(XEN) Freed 176kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) mm.c:779:d0 Bad L1 flags 800000
(XEN) mm.c:1186:d0 Failure in alloc_l1_table: entry 400
(XEN) mm.c:2117:d0 Error while validating mfn 13b6e5 (pf) crashed on
cpu#0000001 rdi: ffffffff81891ba8
(XEN) rbp: ffffffff81891bc8 rsp: ffffffff81891b68 r8: 0000000000000728
(XEN) r9: ffff880000000000 r10: 0000000000007ff0 r11: 00000001731ff063
(XEN) r12: ffffffff818a3f30 r13: ffffffffff400cc0 r14: 0000000173000000
(XEN) r15: 0000000173200000 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 0000000139001000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff81891b68:
(XEN) 000000000000001b 00000001731ff063 ffffffff81037e99 000000010000e030
(XEN) 0000000000010082 ffffffff81891ba8 000000000000e02b ffffffff81037e95
(XEN) 0000000000000000 0000000f 80000000000001e3
(XEN) 0000000000000000 0000000081988849 0000000207b09000 ffffffffff400000
(XEN) 0000000000000000 ffffffff81891d28 0000000140000000 8000000000000163
(XEN) 0000000000000198 ffffffff819888e9 00000000036e5000 ffffffffff400000
(XEN) 8000000000000163 ffff880001002028 0000000140000000 0000000140000000
(XEN) ffffffff81891d58 ffffffff815b690d 0000000000000000 0000000000000003
(XEN) 0000000000000fff880207b09000 ffff880001007070
(XEN) ffffffff81891db8 ffffffff81891e20 0000000000000001 0000000000000000
(XEN) ffffffff817e9ee2 0000000207b09000 ffffffff81891eb8 ffffffff81595a3c
(XEN) ffffffff00000008 0000000081891e28 0000000100000000 0000000000000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
__ __ _ _ ___ ____ _
\ \/ /____|
mu=passthrough iommu=vergbose
(XEN) Video information:
(XEN) VGA is graphics mode 1600x1200, 16 bpp
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) EDID info not retrieved because of reasons unknown
(XEN) Disc information:
(XEN) Found 3 MBR signatures
(XEN) Found 3 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000097400 (usable)
(XEN) 0000000000097400 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bbe80000 (usable)
(XEN) 00000000bbe80000 - 00000000bbe90000 (ACPI data)
(XEN) 00000000bbe90000 - 00000000bbed0000 (ACPI NVS)
(XEN) 00000000bbed0000 - 00000000bbee0000 (reserved)
(XEN) 00000000bbeeb800 - 00000000bc000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 00000001c4000000 (usable)
(XEN) ACPI: RSDP 000FA1F0, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT BBE80000, 0044 (r1 111510 RSDT1542 20101115 MSFT 97)
(XEN) ACPI: FACP BBE80200, 0084 (r1 A_M_I OEMFACP 12000601 MSFT 97)
(XEN) ACPI: DSDT BBE80480, 7129 (r1 AS244 AS244263 263 INTL 20051117)
(XEN) ACPI: FACS BBE90000, 0040
(XEN) ACPI: APIC BBE80390, 00AC (r1 111510 APIC1542 20101115 MSFT 97)
(XEN) ACPI: MCFG BBE80440, 003C (r1 111510 OEMMCFG 20101115 MSFT 97)
(XEN) ACPI: OEMB BBE90040, 0073 (r1 111510 OEMB1542 20101115 MSFT 97)
(XEN) ACPI: AAFT BBE8A480, 0027 (r1 111510 OEMAAFT 20101115 MSFT 97)
(XEN) ACPI: HPET BBE8A4B0, 0038 (r1 111510 OEMHPET 20101115 MSFT 97)
(XEN) ACPI: DMAR BBE900C0, 0130 (r1 AMI OEMDMAR 1 MSFT 97)
(XEN) ACPI: SSDT BBE92430, 0363 (r1 DpgPmm CpuPm 12 INTL 20051117)
(XEN) System RAM: 6142MB (6289500kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC ve000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) [VT-D]dmar.c:524: RMRR address range not in reserved memory base =
bbeeb800 end = bbefffff; iommu_inclusive_mapping=1 parameter may be needed.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 335.416 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware As
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Total of 8
(XEN) ENABLING IO-APIC IRQs
(XE(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
ÿ(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 8 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kern> 0x1bff000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000138000000->000000013c000000 (1503632 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff81bff000
(XEN) Init. ramdisk: ffffffff81bff000->ffffffff82794000
(XEN) Phys-Mach map: ffffffff82794000->ffffffff8332cc80
(XEN) Start info: ffffffff8332d000->ffffffff8332d4b4
(XEN) Page tables: ffffffff8332e000->ffffffff8334b000
(XEN) Boot stack: ffffffff8334b000->ffffffff8334c000
(XEN) TOTAL: ffffffff80000000->ffffffff83400000
(XEN) ENTRY ADDRESS: ffffffff81973200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xenlinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
Xen)
(XEN) Freed 176kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) mm.c:779:d0 Bad L1 flags 800000
(XEN) mm.c:1186:d0 Failure in alloc_l1_table: entry 400
(XEN) mm.c:2117:d0 Error while validating mfn 13b6e5 (pfn 36e5) for type
1000000000000000: caf=8000000000000003 taf=1000000000000001
(XEN) mm.c:2733:d0 Error while pinning mfn 13b6e5
(XEN) traps.c:466:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0
[ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.0.2-rc1-pre x86_64 debug=n Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff81037e99>]
(XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest
(XEN) rax: 00000000ffffffea rbx: 00000000000036e5 rcx: 000000000000001b
(XEN) rdx: 0000000000000000 rsi: 0000000000000001 rdi: ffffffff81891ba8
(XEN) rbp: ffffffff81891bc8 rsp: ffffffff81891b68 r8: 0000000000000728
(XEN) r9: ffff880000000000 r10: 0000000000007ff0 r11: 00000001731ff063
(XEN) r12: ffffffff818a3f30 r13: ffffffffff400cc0 r14: 0000000173000000
(XEN) r15: 0000000173200000 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 0000000139001000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff81891b68:
(XEN) 000000000000001b 00000001731ff063 ffffffff81037e99 000000010000e030
(XEN) 0000000000010082 f000000000000e02b ffffffff81037e95
(XEN) 0000000000000000 000000000013b6e5 0000000181891bf8 00000000000036e5
(XEN) ffffffff81891be8 ffffffff81978fc2 8000000000000163 ffff8800036e5000
(XEN) ffffffff81891c18 ffffffff8105e90a ffffffff81891c08 ffffffffff440000
(XEN) 8000000000000163 ffffffffff400cc0 ffffffff81891cc8 ffffffff815b661b
(XEN) 0000000000000000 0000000000000001 00000001000009ff 80000000000001e3
(XEN) 0000000000000000 0000000081988849 0000000207b09000 ffffffffff400000
(XEN) 0000000000000000 ffffffff81891d28 0000000140000000 8000000000000163
(XEN) 0000000000000198 ffffffff819888e9 00000000036e5000 ffffffffff400000
(XEN) 80000
(XEN) 0000000000000000 0000000000000004 0000000000000001 000000000000000f
(XEN) 000000000354c000 0000000207b09000 0000000000000001 ffffffff81001880
(XEN) ffff880100000000 ffff880207b09000 ffffffff81891db8 ffffffff815b6ab6
(XEN 0000000000000000 ffff880207b09000 ffff880001007070
(XEN) ffffffff81891db8 ffffffff81891e20 0000000000000001 0000000000000000
(XEN) ffffffff817e9ee2 0000000207b09000 ffffffff81891eb8 ffffffff81595a3c
(XEN) ffffffff00000008 0000000081891e28 0000000100000000 0000000000000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

> >You did upgrade to the latest BIOS, right?
> Yes, when I filed the bug some months ago. In the meantime they released some
> new versions, I will try to upgrade the bios once more.
I updated BIOS to the latest one, 2.70.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #12 from pasik@iki.fi 2010-12-18 16:45 -------

Please fix the xen command line, there's a typo in it: iommu=vergbose . It
should be "verbose", of course.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #13 from pasik@iki.fi 2010-12-18 16:47 -------

Also please add the following options for dom0 Linux kernel (vmlinuz):
console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #14 from caz@caztech.com 2010-12-18 18:47 -------
Created an attachment (id=968)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=968&action=view)
Xen boot message


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #15 from caz@caztech.com 2010-12-18 18:48 -------
(In reply to comment #13)
> Also please add the following options for dom0 Linux kernel (vmlinuz):
> console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10
Sorry for typo. I have attached the new boot message.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #16 from pasik@iki.fi 2010-12-19 06:54 -------

Ok, thanks for the new log.

Last lines from dom0 kernel:
[ 0.000000] initial memory mapped : 0 - 03bff000
[ 0.000000] init_memory_mapping: 0000000000000000-00000000bbe80000
[ 0.000000] 0000000000 - 00bbe80000 page 4k
[ 0.000000] kernel direct mapping tables up to bbe80000 @ 100000-6e4000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000207b09000
[ 0.000000] 0100000000 - 0207b09000 page 4k
[ 0.000000] kernel direct mapping tables up to 207b09000 @ 334b000-4393000

And then kaboom:

(XEN) mm.c:779:d0 Bad L1 flags 800000
(XEN) mm.c:1186:d0 Failure in alloc_l1_table: entry 400
(XEN) mm.c:2117:d0 Error while validating mfn 13b6e5 (pfn 36e5) for type
1000000000000000: caf=8000000000000003 taf=1000000000000001
(XEN) mm.c:2733:d0 Error while pinning mfn 13b6e5
(XEN) traps.c:466:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0
[ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.0.2-rc1-pre x86_64 debug=n Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff81037e99>]
(XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest
(XEN) rax: 00000000ffffffea rbx: 00000000000036e5 rcx: 000000000000001b
(XEN) rdx: 0000000000000000 rsi: 0000000000000001 rdi: ffffffff81891ba8
(XEN) rbp: ffffffff81891bc8 rsp: ffffffff81891b68 r8: 0000000000000728
(XEN) r9: ffff880000000000 r10: 0000000000007ff0 r11: 00000001731ff063
(XEN) r12: ffffffff818a3f30 r13: ffffffffff400cc0 r14: 0000000173000000
(XEN) r15: 0000000173200000 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 0000000139001000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff81891b68:
(XEN) 000000000000001b 00000001731ff063 ffffffff81037e99 000000010000e030
(XEN) 0000000000010082 ffffffff81891ba8 000000000000e02b ffffffff81037e95
(XEN) 0000000000000000 000000000013b6e5 0000000181891bf8 00000000000036e5
(XEN) ffffffff81891be8 ffffffff81978fc2 8000000000000163 ffff8800036e5000
(XEN) ffffffff81891c18 ffffffff8105e90a ffffffff81891c08 ffffffffff440000
(XEN) 8000000000000163 ffffffffff400cc0 ffffffff81891cc8 ffffffff815b661b
(XEN) 0000000000000000 0000000000000001 00000001000009ff 80000000000001e3
(XEN) 0000000000000000 0000000081988849 0000000207b09000 ffffffffff400000
(XEN) 0000000000000000 ffffffff81891d28 0000000140000000 8000000000000163
(XEN) 0000000000000198 ffffffff819888e9 00000000036e5000 ffffffffff400000
(XEN) 8000000000000163 ffff880001002028 0000000140000000 0000000140000000
(XEN) ffffffff81891d58 ffffffff815b690d 0000000000000000 0000000000000003
(XEN) 0000000000000000 0000000000000000 0000000207b09000 ffff880001002000
(XEN) 0000000000000000 0000000000000004 0000000000000001 000000000000000f
(XEN) 000000000354c000 0000000207b09000 0000000000000001 ffffffff81001880
(XEN) ffff880100000000 ffff880207b09000 ffffffff81891db8 ffffffff815b6ab6
(XEN) ffffffff00000020 0000000000000000 ffff880207b09000 ffff880001007070
(XEN) ffffffff81891db8 ffffffff81891e20 0000000000000001 000000000
(XEN) ffffffff817e9ee2 0000000207b09000 ffffffff81891eb8 ffffffff81595a3c
(XEN) ffffffff00000008 0000000081891e28 0000000100000000 0000000000000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #17 from pasik@iki.fi 2010-12-19 06:58 -------

One more thing.. does "iommu=off" (for xen.gz) help ?


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #18 from darkbasic4@gmail.com 2010-12-19 08:07 -------
> One more thing.. does "iommu=off" (for xen.gz) help ?
If ioomu=no is the same, it does help for me. So I think it does help for him
too.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #19 from caz@caztech.com 2010-12-19 09:51 -------
Created an attachment (id=971)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=971&action=view)
boot xen-4.0.2-rc1-pre with iommu=off.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #20 from caz@caztech.com 2010-12-19 09:52 -------
(In reply to comment #17)
> One more thing.. does "iommu=off" (for xen.gz) help ?
No. dom0 crashs as the attachment tells.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #21 from konrad.wilk@oracle.com 2010-12-20 08:10 -------
(In reply to comment #14)
> Created an attachment (id=968)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=968&action=view) [edit]
> Xen boot message
>

So in the boot log, it says:

(XEN) [VT-D]dmar.c:524: RMRR address range not in reserved memory base =
bbeeb800 end = bbefffff; iommu_inclusive_mapping=1 parame
ter may be needed.

Did you try that parameter?

Second, for the Dom0 crash, can you decode the eip address to find where it
crashes? Here is how you can do it:
http://lists.xensource.com/archives/cgi-bin/mesg.cgi?a=xen-devel&i=486D0DA6.7010901%40goop.org


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3 [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #22 from caz@caztech.com 2010-12-20 12:51 -------
(In reply to comment #21)
> (XEN) [VT-D]dmar.c:524: RMRR address range not in reserved memory base =
> bbeeb800 end = bbefffff; iommu_inclusive_mapping=1 parameter may be needed.
> Did you try that parameter?
No, it does not help.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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