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-users

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

RE: [Xen-users] FATAL TRAP 18 (machine check)

from [Petersson, Mats] [Permanent Link][Original]
To: "Robert Hulme" <robert.hulme@xxxxxxxxx>, "Xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] FATAL TRAP 18 (machine check)
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Tue, 29 Aug 2006 15:59:18 +0200
Delivery-date: Tue, 29 Aug 2006 07:00:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <e50d039c0608250309h1c6b1c13x85a5211a1ba7f657@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbILtQZ594QGBm4S5aB4DmbxhwLhwDRCtjA
Thread-topic: [Xen-users] FATAL TRAP 18 (machine check) 
Possibly because you have some PCI device that doesn't respond for a
long time... From one of my colleagues, the time is around 4 sceonds
from the request to reply-timeout. Although without getting the actual
error code from the MCE registers, I can't really say what the exact
cause is. The above would be my "75% sure" guess... 

--
Mats

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Robert Hulme
> Sent: 25 August 2006 11:10
> To: Xen-users
> Subject: [Xen-users] FATAL TRAP 18 (machine check)
> 
> Can someone please help? I've just rebooted my dual dual core Opteron
> box and got this error "FATAL TRAP 18 (machine check)".
> 
> On boot I get this:
>  Xen version 3.0.2 (root@[unknown]) (gcc version 4.1.2 20060729
> (prerelease) (Debian 4.1.1-10)) Thu Aug 17 17:30:29 BST 2006
>  Latest ChangeSet: Sat Apr  8 12:14:27 2006 +0100 
> 9598:1bce05ff1e52         
>   
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 0000000000098c00 (usable)
> (XEN)  0000000000098c00 - 00000000000a0000 (reserved)
> (XEN)  00000000000d8000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 000000007ff90000 (usable)
> (XEN)  000000007ff90000 - 000000007ff99000 (ACPI data)
> (XEN)  000000007ff99000 - 0000000080000000 (ACPI NVS)
> (XEN)  0000000080000000 - 00000000bff80000 (usable)
> (XEN)  00000000bff80000 - 00000000c0000000 (reserved)
> (XEN)  00000000e0000000 - 00000000e8000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec00400 (reserved)y in 5 seconds.
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000fff80000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000240000000 (usable)
> (XEN) System RAM: 8190MB (8387232kB)
> (XEN) Xen heap: 13MB (14328kB)
> (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> (XEN) found SMP MP-table at 000f6fc0
> (XEN) DMI present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v000 PTLTD                                 ) @
> 0x00000000000f7040
> (XEN) ACPI: RSDT (v001 PTLTD    RSDT   0x06040000  LTP 0x00000000) @
> 0x000000007ff953c7
> (XEN) ACPI: FADT (v001 NVIDIA CK8S     0x06040000 PTL_ 0x000f4240) @
> 0x000000007ff98d36
> (XEN) ACPI: SRAT (v001 AMD    HAMMER   0x06040000 AMD  0x00000001) @
> 0x000000007ff98daa
> (XEN) ACPI: SPCR (v001 PTLTD  $UCRTBL$ 0x06040000 PTL  0x00000001) @
> 0x000000007ff98eba
> (XEN) ACPI: MCFG (v001 PTLTD    MCFG   0x06040000  LTP 0x00000000) @
> 0x000000007ff98f0a
> (XEN) ACPI: MADT (v001 PTLTD     APIC   0x06040000  LTP 0x00000000) @
> 0x000000007ff98f46
> (XEN) ACPI: BOOT (v001 PTLTD  $SBFTBL$ 0x06040000  LTP 0x00000001) @
> 0x000000007ff98fd8
> (XEN) ACPI: DSDT (v001 NVIDIA      CK8 0x06040000 MSFT 0x0100000e) @
> 0x0000000000000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:1 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:1 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
> (XEN) Processor #2 15:1 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
> (XEN) Processor #3 15:1 APIC version 16
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x05] address[0xdf200000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 5, version 17, address 0xdf200000, GSI 24-27
> (XEN) ACPI: IOAPIC (id[0x06] address[0xdf201000] gsi_base[28])
> (XEN) IOAPIC[2]: apic_id 6, version 17, address 0xdf201000, GSI 28-31
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
> (XEN) ACPI: IRQ9 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 3 I/O APICs
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Initializing CPU#0
> (XEN) Detected 1808.361 MHz processor.
> (XEN) CPU0: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 
> bytes/line)
> (XEN) CPU: L2 Cache: 1024K (64 bytes/line)
> (XEN) CPU 0(2) -> Core 0
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#0.
> (XEN) CPU0: AMD Dual Core AMD Opteron(tm) Processor 265 stepping 02
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) CPU1: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 
> bytes/line)
> (XEN) CPU: L2 Cache: 1024K (64 bytes/line)
> (XEN) CPU 1(2) -> Core 1
> (XEN) AMD: Disabling C1 Clock Ramping Node #0
> (XEN) AMD: Disabling C1 Clock Ramping Node #1
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#1.
> (XEN) CPU1: AMD Dual Core AMD Opteron(tm) Processor 265 stepping 02
> (XEN) Booting processor 2/2 eip 90000
> (XEN) Initializing CPU#2
> (XEN) CPU2: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 
> bytes/line)
> (XEN) CPU: L2 Cache: 1024K (64 bytes/line)
> (XEN) CPU 2(2) -> Core 0
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#2.
> (XEN) CPU2: AMD Dual Core AMD Opteron(tm) Processor 265 stepping 02
> (XEN) Booting processor 3/3 eip 90000
> (XEN) Initializing CPU#3
> (XEN) CPU3: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 
> bytes/line)
> (XEN) CPU: L2 Cache: 1024K (64 bytes/line)
> (XEN) CPU 3(2) -> Core 1
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#3.
> (XEN) CPU3: AMD Dual Core AMD Opteron(tm) Processor 265 stepping 02
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 1.193MHz PIT
> (XEN) Brought up 4 CPUs
> (XEN) Machine check exception polling timer started.
> (XEN) Using IPI Shortcut mode
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Domain 0 kernel supports features = { 0000000f }.
> (XEN) Domain 0 kernel requires features = { 00000000 }.
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   000000007e000000->000000007f000000 (61440 pages
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff805a0008
> (XEN)  Init. ramdisk: ffffffff805a1000->ffffffff80833000
> (XEN)  Phys-Mach map: ffffffff80833000->ffffffff808b3000
> (XEN)  Start info:    ffffffff808b3000->ffffffff808b4000
> (XEN)  Page tables:   ffffffff808b4000->ffffffff808bd000
> (XEN)  Boot stack:    ffffffff808bd000->ffffffff808be000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff80c00000
> (XEN)  ENTRY ADDRESS: ffffffff80100000
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Initrd len 0x292000, start at 0xffffffff805a1000
> (XEN) Scrubbing Free RAM:
> ..............................................................
> ..........----[
> Xen-3.0.2    Not tainted ]----
> (XEN) CPU:    2
> (XEN) RIP:    e010:[<ffff830000119105>]. idle_loop+0x75/0xa0
> (XEN) RFLAGS: 0000000000000246   CONTEXT: hypervisor
> (XEN) rax: 0000000000000100   rbx: 0000000000000002   rcx: 
> 00000000009895b9
> (XEN) rdx: ffff830000194500   rsi: 000000004f245c70   rdi: 
> 00000000b52e4a98
> (XEN) rbp: 0000000000000000   rsp: ffff830000209f20   r8:  
> ffff8300001b3e00
> (XEN) r9:  ffff830000193fd0   r10: 0000000000000001   r11: 
> ffff8300001b3e20
> (XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 
> 0000000000000000
> (XEN) r15: 0000000000000000   cr0: 000000008005003b   cr3: 
> 0000000000102000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e010
> (XEN) .Xen stack trace from rsp=ffff830000209f20:
> (XEN)    00000000a5a5a5a5 .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)    0000000000000000 0000000000000000 0000000000000002 
> ffff83000020a080
> (XEN) Xen call trace:
> (XEN)    [<ffff830000119105>]. idle_loop+0x75/0xa0
> (XEN)
> (XEN) ************************************
> (XEN) CPU2 FATAL TRAP 18 (machine check), ERROR_CODE 0000.
> (XEN) System shutting down -- need manual reset.
> (XEN) ************************************
> 
> 
> -- 
> ------------------------------------------------------
> ASCII stupid question, get a stupid ANSI
> 
> "Sex is one of the most beautiful, natural, wholesome things that
> money can buy" --Steve Martin
> 
> http://www.robhulme.com/
> http://robhu.livejournal.com/
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: [Xen-users] Spam on xen-announce, James Bulpin
Next by Date:  [Xen-users] can't get multiple VLANs to work, Tomasz Chmielewski
Previous by Thread:  Re: [Xen-users] FATAL TRAP 18 (machine check), Robert Hulme
Next by Thread:  [Xen-users] Is it possible to run two or more multiboot linux installations on a single drive using Xen., nbitspoken
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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