thr3ads.net - Xen users - [Xen-users] CPU1 FATAL TRAP, Xen won''t boot [Nov 2006]

If this information is useful, please help other people find it:
Share via:

Tomasz Chmielewski

2006-Nov-20 16:46 UTC

[Xen-users] CPU1 FATAL TRAP, Xen won''t boot

This is a followup to my earlier post, "can''t start Xen kernel on
64 bit
Intel Xeon".

This time, I captured Xen log via the serial console.

Any ideas what''s wrong?

  __  __            _____  ___   _____     ___
  \ \/ /___ _ __   |___ / / _ \ |___ /   | | |  |_ \ __| | | |
   /  \  __/ | | |  ___) | |_| | ___) |__| |_| |
  /_/\_\___|_| |_| |____(_)___(_)____/    \___/

  http://www.cl.cam.ace Computer Laboratory

  Xen version 3.0.3-0 (root@(none)) (gcc version 4.1.1 20060724 
(prerelease) (4.1.1-3mdk)) Mon Nov 20 15:53:01 CET 2006
  Latest ChangeSet: unavailable

(XEN) Commandcom1=115200,8n1
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 000000007ffd8000 (usable)
(XEN)  000000007ffd8000 - 000000007ffe0000 (ACPI data)
(XEN)  000000007ffe0000 - 0000000080000000 (reserved)
(XEN)  00000000fec00000 - 00000000fed00000 (reserved)
000 (reserved)
(XEN)  00000000ffc00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096604kB)
(XEN) Xen heap: 14MB (14416kB)
(XEN) found SMP MP-table at 000f4f80
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP                         ) @ 0x00000000000f4f00
(XEN) ACPI: XSDT (v001 HP     W04      0x00000002 .. 0x0000162e) @ 
0x000000007ffd8300
(XEN) ACPI: FADT (v003 HP     W04      0x00000002 .. 0x0000162e) @ 
0x000000007ffd8380
(XEN) ACPI: SPCR (v001 HP     SPCRRBSU 0x00000001 .. 0x0000162e) @ 
0x000000007ffd8100
(XEN) ACPI: MCFG (v001 HP     ProLiant 0x00000001  0x00000000) @ 
0x000000007ffd8180
(XEN) ACPI: HPET (v001 HP     W04      0x00000002 .. 0x0000162e) @ 
0x000000007ffd81c0
(XEN) ACPI: SPMI (v005 HP     ProLiant 0x00000001 .. 0x0000162e) @ 
0x000000007ffd8200
(XEN) ACPI: MADT (v001 HP     00000083 0x0000000000007ffd8240
(XEN) ACPI: DSDT (v001 HP         DSDT 0x00000001 INTL 0x20030228) @ 
0x0000000000000000
(XEN) ACPI: Local APIC a(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] 
enabled)
(XEN) Processor #0 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] (XEN) Processor #1 6:15 
APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_bas(XEN) IOAPIC[0]: 
apic_id 8, 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: 0x10228201 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2133.482 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX disabled by Feature Control MSR.
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CP(XEN) CPU0: Intel(R) 
Xeon(R) CPU            3050  @ 2.13GHz stepping 06
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) BUG at vmcs.c:131
(XEN) ----[ Xen-3.0.3-0  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e010:[<ffff830000118154>] __bug+0x24/0x30
(XEN) RFLAGS: 0000000000010082   CONTEXT: hypervisor
(XEN) rax: 0000000000000000   rbx: 0000000000000083   rcx: 0000000000000f33
(XEN) rdx: 000000000000000a   rsi: 000000000000000a   rdi: ffff8300001bf012
(XEN) rbp: 000000000699e7fa   rsp: ffff830000ff3de0   r8:  ffff8300000b8000
(XE9:  0000000000000003   r10: fffffffffffffffd   r11: ffff830000118720
(XEN) r12: ffff830000176468   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 00000000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 0000000000102000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e010
(XEN) Xen trace from rsp=ffff830000ff3de0:
(XEN)    ffff8300001d6d00 000000000003efff 000000000000001f ffff830000145739
(XEN)    0000000001020800 ffffffffffffc000 0000000000000
                                                         (XEN) 
0000000000000000 ffff83000016c223 0000000000000001 0000000000000001
(XEN)    ffff8300001d6d00 ffff83000016bda8 0000000000000000 0000000000000001
(XEN)    ffff8300001d6d00 ffff830000168f2a 0000000000000001 ffff830000ff3f28
(XEN)    0000000000000001 ffff8300001690b2 ffff830000ff3f28 ffff830000ff3f28
(XEN)    0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffff8300001692c2 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000(XEN) 
  0000000000000000 0000000000000000 0000000000000000 00000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 
000000000000(XEN)    0000000000000000 0000000000000000 0000000000000001 
ffff80
(XEN) Xen call trace:
(XEN)    [<ffff830000118154>] __bug+0x24/0x30
(XEN)    [<ffff830000145739>] vmx_init_vmcs_config+0xb9/0x180
(XEN)    [<ffff830000147568>] start_vmx+0x78/0x290
(XEN)    [<ffff83000016c223>] init_intel+0xe3/0x1b0
(XEN)    [<ffff83000016bda8>] identify_cpu+0xa8/0x1f0
(XEN)    [<ffff830000168f2a>] smp_store_cpu_info+0x3a/0xc0
(XEN)    [<ffff8300001690b2>] smp_callin+0xe2/0x1d0
(XEN)    [<ffff8300001692c2>] start_secondary+0x62/0x3b0
(XEN)
(XEN) ************************************
(XEN) CPU1 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN IN(XEN) 
System shutting down -- need manual reset.
(XEN) ************************************



-- 
Tomasz Chmielewski
http://wpkg.org

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

Tomasz Chmielewski

2006-Nov-20 20:58 UTC

head link

Re: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot

Tomasz Chmielewski wrote:> This is a followup to my earlier post, "can''t start Xen
kernel on 64 bit
> Intel Xeon".
> 
> This time, I captured Xen log via the serial console.
> 
> Any ideas what''s wrong?
> (XEN) VMX disabled by Feature Control MSR.
> (XEN) ************************************
> (XEN) CPU1 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN IN(XEN) 
> System shutting down -- need manual reset.
> (XEN) ************************************
Enabling VMX in BIOS solved the issue...


-- 
Tomasz Chmielewski
http://wpkg.org

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

Ulrich Windl

2006-Nov-21 07:25 UTC

head link

Re: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot

On 20 Nov 2006 at 21:58, Tomasz Chmielewski wrote:
> Tomasz Chmielewski wrote:
> > This is a followup to my earlier post, "can''t start Xen
kernel on 64 bit
> > Intel Xeon".
> > 
> > This time, I captured Xen log via the serial console.
> > 
> > Any ideas what''s wrong?
> 
> > (XEN) VMX disabled by Feature Control MSR.
> 
> 
> > (XEN) ************************************
> > (XEN) CPU1 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN IN(XEN) 
> > System shutting down -- need manual reset.
> > (XEN) ************************************
> 
> Enabling VMX in BIOS solved the issue...
The XEN code should better check VMX availability I guess...

Ulrich


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

Petersson, Mats

2006-Nov-21 13:03 UTC

head link

RE: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot

Looks like it''s failing one of the sanity checks. I wonder if
it''s
difficult to add the string that failed to the "BUG_ON()" macro... 

Line 131 in my version of the code, that is a few weeks old, checks that
the (VMCS_REVISION_ID != vmx_msr_low) [and it fails if that''s
TRUE...]),
and it''s basicly comparing the other processors to the boot
processor...


I don''t think it should fail like that... :-(

--
Mats 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of 
> Tomasz Chmielewski
> Sent: 20 November 2006 16:47
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot
> 
> This is a followup to my earlier post, "can''t start Xen 
> kernel on 64 bit 
> Intel Xeon".
> 
> This time, I captured Xen log via the serial console.
> 
> Any ideas what''s wrong?
> 
>   __  __            _____  ___   _____     ___
>   \ \/ /___ _ __   |___ / / _ \ |___ /   | | |  |_ \ __| | | |
>    /  \  __/ | | |  ___) | |_| | ___) |__| |_| |
>   /_/\_\___|_| |_| |____(_)___(_)____/    \___/
> 
>   http://www.cl.cam.ace Computer Laboratory
> 
>   Xen version 3.0.3-0 (root@(none)) (gcc version 4.1.1 20060724 
> (prerelease) (4.1.1-3mdk)) Mon Nov 20 15:53:01 CET 2006
>   Latest ChangeSet: unavailable
> 
> (XEN) Commandcom1=115200,8n1
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009fc00 (usable)
> (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000f0000 - 0000000000100000 000000007ffd8000 (usable)
> (XEN)  000000007ffd8000 - 000000007ffe0000 (ACPI data)
> (XEN)  000000007ffe0000 - 0000000080000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fed00000 (reserved)
> 000 (reserved)
> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
> (XEN) System RAM: 2047MB (2096604kB)
> (XEN) Xen heap: 14MB (14416kB)
> (XEN) found SMP MP-table at 000f4f80
> (XEN) DMI 2.3 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP                         ) @ 0x00000000000f4f00
> (XEN) ACPI: XSDT (v001 HP     W04      0x00000002 .. 0x0000162e) @ 
> 0x000000007ffd8300
> (XEN) ACPI: FADT (v003 HP     W04      0x00000002 .. 0x0000162e) @ 
> 0x000000007ffd8380
> (XEN) ACPI: SPCR (v001 HP     SPCRRBSU 0x00000001 .. 0x0000162e) @ 
> 0x000000007ffd8100
> (XEN) ACPI: MCFG (v001 HP     ProLiant 0x00000001  0x00000000) @ 
> 0x000000007ffd8180
> (XEN) ACPI: HPET (v001 HP     W04      0x00000002 .. 0x0000162e) @ 
> 0x000000007ffd81c0
> (XEN) ACPI: SPMI (v005 HP     ProLiant 0x00000001 .. 0x0000162e) @ 
> 0x000000007ffd8200
> (XEN) ACPI: MADT (v001 HP     00000083 0x0000000000007ffd8240
> (XEN) ACPI: DSDT (v001 HP         DSDT 0x00000001 INTL 0x20030228) @ 
> 0x0000000000000000
> (XEN) ACPI: Local APIC a(XEN) ACPI: LAPIC (acpi_id[0x00] 
> lapic_id[0x00] 
> enabled)
> (XEN) Processor #0 6:15 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] (XEN) 
> Processor #1 6:15 
> APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_bas(XEN) 
> IOAPIC[0]: 
> apic_id 8, 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: 0x10228201 base: 0xfed00000
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Initializing CPU#0
> (XEN) Detected 2133.482 MHz processor.
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 2048K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 0
> (XEN) VMX disabled by Feature Control MSR.
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CP(XEN) CPU0: Intel(R) 
> Xeon(R) CPU            3050  @ 2.13GHz stepping 06
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 2048K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 1
> (XEN) BUG at vmcs.c:131
> (XEN) ----[ Xen-3.0.3-0  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    1
> (XEN) RIP:    e010:[<ffff830000118154>] __bug+0x24/0x30
> (XEN) RFLAGS: 0000000000010082   CONTEXT: hypervisor
> (XEN) rax: 0000000000000000   rbx: 0000000000000083   rcx: 
> 0000000000000f33
> (XEN) rdx: 000000000000000a   rsi: 000000000000000a   rdi: 
> ffff8300001bf012
> (XEN) rbp: 000000000699e7fa   rsp: ffff830000ff3de0   r8:  
> ffff8300000b8000
> (XE9:  0000000000000003   r10: fffffffffffffffd   r11: 
> ffff830000118720
> (XEN) r12: ffff830000176468   r13: 0000000000000000   r14: 
> 0000000000000000
> (XEN) r15: 00000000000008005003b   cr4: 00000000000026f0
> (XEN) cr3: 0000000000102000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e010
> (XEN) Xen trace from rsp=ffff830000ff3de0:
> (XEN)    ffff8300001d6d00 000000000003efff 000000000000001f 
> ffff830000145739
> (XEN)    0000000001020800 ffffffffffffc000 0000000000000
>                                                          (XEN) 
> 0000000000000000 ffff83000016c223 0000000000000001 0000000000000001
> (XEN)    ffff8300001d6d00 ffff83000016bda8 0000000000000000 
> 0000000000000001
> (XEN)    ffff8300001d6d00 ffff830000168f2a 0000000000000001 
> ffff830000ff3f28
> (XEN)    0000000000000001 ffff8300001690b2 ffff830000ff3f28 
> ffff830000ff3f28
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 ffff8300001692c2 0000000000000000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000(XEN) 
>   0000000000000000 0000000000000000 0000000000000000 00000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> 000000000000(XEN)    0000000000000000 0000000000000000 
> 0000000000000001 
> ffff80
> (XEN) Xen call trace:
> (XEN)    [<ffff830000118154>] __bug+0x24/0x30
> (XEN)    [<ffff830000145739>] vmx_init_vmcs_config+0xb9/0x180
> (XEN)    [<ffff830000147568>] start_vmx+0x78/0x290
> (XEN)    [<ffff83000016c223>] init_intel+0xe3/0x1b0
> (XEN)    [<ffff83000016bda8>] identify_cpu+0xa8/0x1f0
> (XEN)    [<ffff830000168f2a>] smp_store_cpu_info+0x3a/0xc0
> (XEN)    [<ffff8300001690b2>] smp_callin+0xe2/0x1d0
> (XEN)    [<ffff8300001692c2>] start_secondary+0x62/0x3b0
> (XEN)
> (XEN) ************************************
> (XEN) CPU1 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN IN(XEN) 
> System shutting down -- need manual reset.
> (XEN) ************************************
> 
> 
> 
> -- 
> Tomasz Chmielewski
> http://wpkg.org
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 
> 


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

Tomasz Chmielewski

2006-Nov-21 22:09 UTC

head link

Re: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot

Petersson, Mats wrote:> Looks like it''s failing one of the sanity checks. I wonder if
it''s
> difficult to add the string that failed to the "BUG_ON()"
macro...
> 
> Line 131 in my version of the code, that is a few weeks old, checks that
> the (VMCS_REVISION_ID != vmx_msr_low) [and it fails if that''s
TRUE...]),
> and it''s basicly comparing the other processors to the boot
processor...
> 
> 
> I don''t think it should fail like that... :-(
As I replied earlier, it boots properly[1] after I enable VMX in BIOS. 
Should it fail with VMX disabled, is a good question of course.


[1] Almost properly. This server, ProLiant DL320 G5, has problem with 
starting the system, when it uses a Xen kernel (with a non-Xen kernel 
the system starts just fine). When I blacklist USB modules, it boots 
just fine.
I don''t need USB here, so I didn''t investigate it anymore.


-- 
Tomasz Chmielewski
http://wpkg.org

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

Xen users - Nov 2006 - CPU1 FATAL TRAP, Xen won''t boot

[Xen-users] CPU1 FATAL TRAP, Xen won''t boot

Re: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot

Re: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot

RE: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot

Re: [Xen-users] CPU1 FATAL TRAP, Xen won''t boot