James Ray
2007-Sep-10 10:28 UTC
[Pkg-xen-devel] Bug#441539: xen-hypervisor-3.0.3-1-amd64: Xen failing to boot with FATAL TRAP error
Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important about every 1 in 10 boots I am getting the following error: (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This seems to happen in the CPU detection stage. This is a Quad-Core, Dual CPU system currently running with 4Gb of RAM with a Intel S5000PAL server motherboard. I have tried tweaking around the APIC options to be bigsmp to no help at all. I am kind of at a loss right now as to how to progress. I have upgraded the BIOS to the latest revision to no avail also. Here is a full failed boot log: (XEN) Command line: /xen-3.0.3-1-amd64.gz com2=19200,8n1 console=com2 noirqbalance watchdog (XEN) Physical RAM map:ry will be booted automatically in 1 seconds. (XEN) 0000000000000000 - 000000000009fc00 (usable) (XEN) 000000000009fc00 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000009e4a1000 (usable) (XEN) 000000009e4a1000 - 000000009e562000 (ACPI NVS) (XEN) 000000009e562000 - 000000009fa42000 (usable) (XEN) 000000009fa42000 - 000000009fa9a000 (reserved) (XEN) 000000009fa9a000 - 000000009fab1000 (usable) (XEN) 000000009fab1000 - 000000009fb1a000 (ACPI NVS) (XEN) 000000009fb1a000 - 000000009fb2a000 (usable) (XEN) 000000009fb2a000 - 000000009fb3a000 (ACPI data) (XEN) 000000009fb3a000 - 000000009fc00000 (usable) (XEN) 000000009fc00000 - 00000000b0000000 (reserved) (XEN) 00000000ffc00000 - 00000000ffc0c000 (reserved) (XEN) 0000000100000000 - 0000000160000000 (usable) (XEN) System RAM: 4090MB (4188212kB) (XEN) Xen heap: 13MB (14304kB) (XEN) found SMP MP-table at 000fd1b0 (XEN) DMI 2.5 present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v002 INTEL ) @ 0x00000000000f03c0 (XEN) ACPI: XSDT (v001 INTEL S5000PAL 0x00000000 INTL 0x01000013) @ 0x000000009fb39120 (XEN) ACPI: FADT (v003 INTEL S5000PAL 0x00000000 INTL 0x01000013) @ 0x000000009fb37000 (XEN) ACPI: MADT (v001 INTEL S5000PAL 0x00000000 INTL 0x01000013) @ 0x000000009fb36000 (XEN) ACPI: SPCR (v001 INTEL S5000PAL 0x00000000 INTL 0x01000013) @ 0x000000009fb2f000 (XEN) ACPI: HPET (v001 INTEL S5000PAL 0x00000001 INTL 0x01000013) @ 0x000000009fb2e000 (XEN) ACPI: MCFG (v001 INTEL S5000PAL 0x00000001 INTL 0x01000013) @ 0x000000009fb2d000 (XEN) ACPI: OEM1 (v001 INTEL S5000PAL 0x00000001 INTL 0x01000013) @ 0x000000009fb2c000 (XEN) ACPI: SSDT (v002 INTEL EIST 0x00004000 INTL 0x01000013) @ 0x000000009fb2b000 (XEN) ACPI: SSDT (v002 INTEL IPMI 0x00004000 INTL 0x01000013) @ 0x000000009fb2a000 (XEN) ACPI: DSDT (v002 INTEL S5000PAL 0x00000008 INTL 0x01000013) @ 0x0000000000000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) (XEN) Processor #2 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) (XEN) Processor #4 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) (XEN) Processor #6 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) (XEN) Processor #1 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) (XEN) Processor #3 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) (XEN) Processor #5 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) (XEN) Processor #7 6:15 APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1]) (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) (XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 (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 2 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 1861.936 MHz processor. (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) VMXON is done (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Intel(R) Xeon(R) CPU E5320 @ 1.86GHz stepping 07 (XEN) Booting processor 1/2 eip 90000 (XEN) Initializing CPU#1 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 2 (XEN) VMXON is done (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#1. (XEN) CPU1: Intel(R) Xeon(R) CPU E5320 @ 1.86GHz stepping 07 (XEN) Booting processor 2/4 eip 90000 (XEN) Initializing CPU#2 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: Physical Processor ID: 1 (XEN) CPU: Processor Core ID: 0 (XEN) VMXON is done (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#2. (XEN) CPU2: Intel(R) Xeon(R) CPU E5320 @ 1.86GHz stepping 07 (XEN) Booting processor 3/6 eip 90000 (XEN) Not responding. (XEN) Inquiring remote APIC #6... (XEN) ... APIC #6 ID: failed (XEN) ... APIC #6 VERSION: failed (XEN) ... APIC #6 SPIV: failed (XEN) CPU #6 not responding - cannot use it. (XEN) BUG at domain.c:78 (XEN) ----[ Xen-3.0.3-1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e010:[<ffff8300001180f4>] __bug+0x24/0x30 (XEN) RFLAGS: 0000000000010086 CONTEXT: hypervisor (XEN) rax: 0000000000000000 rbx: 000000000000004e rcx: 00000000000015b6 (XEN) rdx: 000000000000000a rsi: 000000000000000a rdi: ffff8300001bf013 (XEN) rbp: ffff830000ffb080 rsp: ffff8300001b7d78 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 00000000fffffffb r11: ffff8300001186b0 (XEN) r12: ffff830000172cf5 r13: 0000000000000003 r14: 0000000000000003 (XEN) r15: 0000000000000003 cr0: 000000008005003b cr4: 00000000000026f0 (XEN) cr3: 0000000000102000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e010 (XEN) Xen stack trace from rsp=ffff8300001b7d78: (XEN) ffff830000ffb080 0000000000000003 0000000000000003 ffff830000106f15 (XEN) ffff8300001b7da8 0001000000000005 0000000000000003 0000000000000003 (XEN) 0000000000000001 0000000000000004 ffff83000017f9a4 ffff830000107369 (XEN) 0000000000000006 0000000000000000 0000000000000003 ffff830000169f49 (XEN) ffff8300001b7e48 0000000000000006 ffff8300001b7e68 0000000300000020 (XEN) 0000000306000000 0000000000090000 000000000000000e 0000000000000092 (XEN) 000000000020a000 0000000500000690 ffff83000017656a ffff830000175506 (XEN) ffff83000017550e ffff83000017fa80 0000000300000002 ffff83000000000f (XEN) ffff83000002dd40 ffff830000ffb080 ffff830000191000 000000000000000e (XEN) ffff8300000229e0 ffff83000002dd40 0000000000000002 ffff830000168f0c (XEN) 0000000800000000 000000010000006e 0000000000000003 00000000000002f8 (XEN) 0000000000000000 000000000000000e 0000000000000000 0000000000000000 (XEN) 0000000000067eac 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 ffff8300001001c1 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 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) Xen call trace: (XEN) [<ffff8300001180f4>] __bug+0x24/0x30 (XEN) [<ffff830000106f15>] alloc_vcpu+0x45/0x130 (XEN) [<ffff830000107369>] alloc_idle_vcpu+0x59/0x80 (XEN) [<ffff830000169f49>] smp_prepare_cpus+0x4a9/0xd10 (XEN) [<ffff830000168f0c>] __start_xen+0x75c/0xac0 (XEN) [<ffff8300001001c1>] __high_start+0x94/0x96 (XEN) (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This happends the same on two identical systems that pass all of the Intel Platform Confidance tests. Any further information I would be happy to provide. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (700, 'stable'), (650, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-xen-amd64 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages xen-hypervisor-3.0.3-1-amd64 depends on: ii xen-utils-3.0.3-1 3.0.3-0-2 XEN administrative tools xen-hypervisor-3.0.3-1-amd64 recommends no packages. -- no debconf information
Ian Campbell
2015-Aug-21 09:52 UTC
[Pkg-xen-devel] Bug#441539: xen-hypervisor-3.0.3-1-amd64: Xen failing to boot with FATAL TRAP error
Control: tags -1 +morienfo On Mon, 10 Sep 2007 11:28:05 +0100 James Ray <j.ray at qmul.ac.uk> wrote:> Package: xen-hypervisor-3.0.3-1-amd64 > Version: 3.0.3-0-2 > Severity: important > > about every 1 in 10 boots I am getting the following error: > (XEN) ************************************ > (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. > (XEN) System shutting down -- need manual reset. > (XEN) ************************************ > > This seems to happen in the CPU detection stage.It seems this bug fell through the cracks at some point. I think it is very likely that this issue has been fixed at some point. Please can you confirm if you are still seeing it? Cheers, Ian.
Debian Bug Tracking System
2015-Aug-21 09:57 UTC
[Pkg-xen-devel] Processed (with 1 errors): Re: xen-hypervisor-3.0.3-1-amd64: Xen failing to boot with FATAL TRAP error
Processing control commands:> tags -1 +morienfoUnknown tag/s: morienfo. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore. Bug #441539 [src:xen] xen-hypervisor-3.0.3-1-amd64: Xen failing to boot with FATAL TRAP error Requested to add no tags; doing nothing. -- 441539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441539 Debian Bug Tracking System Contact owner at bugs.debian.org with problems
Debian Bug Tracking System
2015-Aug-21 09:57 UTC
[Pkg-xen-devel] Processed (with 1 errors): Re: xen-hypervisor-3.0.3-1-amd64: Xen failing to boot with FATAL TRAP error
Processing control commands:> tags -1 +morienfoUnknown tag/s: morienfo. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore. Bug #441539 [src:xen] xen-hypervisor-3.0.3-1-amd64: Xen failing to boot with FATAL TRAP error Requested to add no tags; doing nothing. -- 441539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441539 Debian Bug Tracking System Contact owner at bugs.debian.org with problems