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

Re: [Xen-devel] Xen-unstable panic: FATAL PAGE FAULT

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xen-unstable panic: FATAL PAGE FAULT
From: Bastian Blank <waldi@xxxxxxxxxx>
Date: Fri, 30 Apr 2010 22:52:23 +0200
Delivery-date: Fri, 30 Apr 2010 13:53:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7945AEA.95CD%keir.fraser@xxxxxxxxxxxxx>
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: <1265497008.11252.38.camel@bespin> <C7945AEA.95CD%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sun, Feb 07, 2010 at 11:56:26AM +0000, Keir Fraser wrote:
> I'll have to decode the backtrace a bit, but I would guess most likely is
> some memory got corrupted along the way, which would be rather nasty. I
> already need to follow up on a report of apparent memory corruption in a
> domU userspace (testing with the 'memtester' utility), so with a bit of luck
> they could be maifestations of the same bug.

I saw a similar crash with 4.0.0 release. The server survived memtest86
for several time and works (mostly) with Xen 3.4.

(XEN) ----[ Xen-4.0.0  x86_64  debug=n  Tainted:    C ]----
(XEN) CPU:    8
(XEN) RIP:    e008:[<ffff82c480114e26>] free_heap_pages+0x366/0x4b0
(XEN) RFLAGS: 0000000000010286   CONTEXT: hypervisor
(XEN) rax: ffff82c480375070   rbx: ffff82f6143cc240   rcx: ffff8315ffffffe0
(XEN) rdx: ffff8315ffffffe0   rsi: 00000000ffffffff   rdi: 0000000000a1e613
(XEN) rbp: 0000000000000000   rsp: ffff830a2fee7cf8   r8:  0000000000000020
(XEN) r9:  0000000000000001   r10: 0200000000000000   r11: 0080000000000000
(XEN) r12: ffff82f6143cc260   r13: 00007d0a00000000   r14: 0180000000000000
(XEN) r15: 00000000000001b5   cr0: 000000008005003b   cr4: 00000000000006f0
(XEN) cr3: 0000000a1ff80000   cr2: ffff8315ffffffe4
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff830a2fee7cf8:
(XEN)    0000000000000000 ffff82c4803764c0 00000000000001b5 00000000143cc240
(XEN)    ffff830840060000 ffff830840060000 ffff82f6143cc240 0000000000000000
(XEN)    ffff830840060014 00000000000ffea5 0000000000000000 ffff82c4801150b8
(XEN)    ffff830840060000 ffff82f6143cc240 ffff8300cfe2c000 0000000000000000
(XEN)    ffff8300cfe2c000 0000000000000001 0010000a1e612067 ffff830840060000
(XEN)    ffff83092f69c9c8 ffff82c48016371f ffff830a2fee7f28 ffff82c48015b9f8
(XEN)    0080000000000000 ffff8800ffa55db0 ffff830a2fee7ed0 ffff830840060000
(XEN)    000000000092f69c 000000000092f69c 000000000092f69c 0000000000000000
(XEN)    00000000125ed380 ffff830840060000 ffff82f6125ed380 0000000000000000
(XEN)    ffff8300cfe2c000 ffff880002939000 ffff830840060000 ffff82c480166b1c
(XEN)    0000000000000001 0000000000000000 ffff83092f69c9c8 ffff830a2fee7f28
(XEN)    0000000000000001 ffff830a2fee7f28 ffff830840060000 0000000000000001
(XEN)    ffff8800ffa55dd8 000000000092f69c 0000000000000000 ffff82c480266008
(XEN)    ffff8800038c7060 0000000000000000 ffff82c480266000 0000000000000000
(XEN)    ffff830a2fee7f28 ffff82c480114129 0000000100000006 ffff830a2fee7f28
(XEN)    ffff830a2fee7f28 ffff82c480266010 0000000000000000 ffff8300cfe2c000
(XEN)    0000000000000000 ffff8800010060a0 ffff88000293a000 0000000000000260
(XEN)    0000000000000000 ffff82c4801e7169 0000000000000000 0000000000000260
(XEN)    ffff88000293a000 ffff8800010060a0 0000000000000000 ffff8800038c7060
(XEN)    0000000000000212 0000000000000000 ffff8800ffc03080 0000000000000000
(XEN) Xen call trace:
(XEN)    [<ffff82c480114e26>] free_heap_pages+0x366/0x4b0
(XEN)    [<ffff82c4801150b8>] free_domheap_pages+0x148/0x380
(XEN)    [<ffff82c48016371f>] mod_l1_entry+0x16f/0x740
(XEN)    [<ffff82c48015b9f8>] get_page+0x28/0xf0
(XEN)    [<ffff82c480166b1c>] __do_update_va_mapping+0x64c/0x6e0
(XEN)    [<ffff82c480114129>] do_multicall+0x189/0x320
(XEN)    [<ffff82c4801e7169>] syscall_enter+0xa9/0xae
(XEN)    
(XEN) Pagetable walk from ffff8315ffffffe4:
(XEN)  L4[0x106] = 00000000cfd69027 5555555555555555
(XEN)  L3[0x057] = 0000000000000000 ffffffffffffffff
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 8:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0002]
(XEN) Faulting linear address: ffff8315ffffffe4
(XEN) ****************************************

> > (XEN) Pagetable walk from ffff8315ffffffe4:
> > (XEN)  L4[0x106] = 00000000bf4f5027 5555555555555555
> > (XEN)  L3[0x057] = 0000000000000000 ffffffffffffffff
> > (XEN)
> > (XEN) ****************************************
> > (XEN) Panic on CPU 2:
> > (XEN) FATAL PAGE FAULT
> > (XEN) [error_code=0002]
> > (XEN) Faulting linear address: ffff8315ffffffe4
> > (XEN) ****************************************

The addresses are even identical.

Bastian

-- 
I have never understood the female capacity to avoid a direct answer to
any question.
                -- Spock, "This Side of Paradise", stardate 3417.3

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

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] Xen-unstable panic: FATAL PAGE FAULT, Bastian Blank <=