xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Mark Hurenkamp <mark.hurenkamp@xs4all.nl>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen-unstable panic: FATAL PAGE FAULT
Date: Sun, 07 Feb 2010 11:56:26 +0000	[thread overview]
Message-ID: <C7945AEA.95CD%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1265497008.11252.38.camel@bespin>

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.

 -- Keir

On 06/02/2010 22:56, "Mark Hurenkamp" <mark.hurenkamp@xs4all.nl> wrote:

> Hi,
> 
> 
> While playing with my xen server (which is running xen-unstable/linux pvops),
> it suddenly crashed with the following messages on the serial port.
> This is a recent version of xen-unstable, but i am a few updates behind.
> I've seen this only once, so perhaps it is hard to reproduce. I hope this
> info is still of use to someone.
> 
> 
> Regards,
> Mark.
> 
> 
> (XEN) tmem: all pools frozen for all domains
> (XEN) tmem: all pools frozen for all domains
> (XEN) tmem: all pools thawed for all domains
> (XEN) tmem: all pools thawed for all domains
> (XEN) paging.c:170: paging_free_log_dirty_bitmap: used 19 pages for domain 3
> dirty logging
> (XEN) ----[ Xen-4.0.0-rc3-pre  x86_64  debug=y  Tainted:    C ]----
> (XEN) CPU:    2
> (XEN) RIP:    e008:[<ffff82c4801150c5>] free_heap_pages+0x53a/0x555
> (XEN) RFLAGS: 0000000000010282   CONTEXT: hypervisor
> (XEN) rax: ffff82c4803004c0   rbx: ffff82f600ae4b40   rcx: ffff8315ffffffe0
> (XEN) rdx: 00000000ffffffff   rsi: ffff8315ffffffe0   rdi: ffff82f600000000
> (XEN) rbp: ffff83013ff27bc8   rsp: ffff83013ff27b68   r8:  0000000000000000
> (XEN) r9:  0200000000000000   r10: 0000000000000001   r11: 0080000000000000
> (XEN) r12: ffff82f600ae4b60   r13: 0000000000000000   r14: 00007d0a00000000
> (XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026f0
> (XEN) cr3: 0000000101001000   cr2: ffff8315ffffffe4
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
> (XEN) Xen stack trace from rsp=ffff83013ff27b68:
> (XEN)    c2c2c2c2c2c2c2c2 0000000000000064 0000000000000000 0000000000000012
> (XEN)    0000000000000297 000000000000017a ffff82c48011e1e3 0000000000000000
> (XEN)    ffff83010fc50000 ffff82f600ae4b60 0000000000069f65 ffff82f600ae4b80
> (XEN)    ffff83013ff27c18 ffff82c4801153ee 0000000000000001 0000000000000001
> (XEN)    ffff82f600ae49c8 ffff82f600ae4b60 0000000000800727 ffff83013fef0000
> (XEN)    ffff82f600ae4b60 ffff83010fc50000 ffff83013ff27c38 ffff82c48015d4d0
> (XEN)    000000000000e010 800000005725b727 ffff83013ff27c78 ffff82c48015f8d8
> (XEN)    80000000571bf727 ffff8300aae3ac60 ffff83013fef0000 ffff8300aae3b000
> (XEN)    ffff83013ff27f28 0000000000000000 ffff83013ff27cd8 ffff82c48015eaf4
> (XEN)    ffff83013ff27d08 ffff82c48015fe3d ffff83013ff27cf8 ffff82c48015d4fe
> (XEN)    ffff83013ff27cc8 1400000000000001 ffff82f60155c740 ffff82f60155c740
> (XEN)    ffff83013ff27f28 007fffffffffffff ffff83013ff27d28 ffff82c48015f11c
> (XEN)    000000003fef0000 ffff82f60155c750 ffff83013ff27d38 ffff83013fef0000
> (XEN)    0000000000000000 ffffc9000000c2b0 00000000000aae3a ffff83013ff27f28
> (XEN)    ffff83013ff27d38 ffff82c48015f2f8 ffff83013ff27e38 ffff82c480163a4f
> (XEN)    ffff83013fef0018 00007ff03fef0000 0000000000000000 ffff82c480264db0
> (XEN)    ffff82c480264db8 ffff83013ff27f28 ffff83013ff27f28 ffff83013fef0218
> (XEN)    ffff8300bf524000 ffff83013fef0000 ffff8300bf524000 ffff83013fef0000
> (XEN)    ffff83013fff3da8 0000000100000002 ffff830100000000 ffff82f60155c740
> (XEN)    800000008eadf063 ffff880000000001 ffff83013ff27de8 000000003fff3d90
> (XEN) Xen call trace:
> (XEN)    [<ffff82c4801150c5>] free_heap_pages+0x53a/0x555
> (XEN)    [<ffff82c4801153ee>] free_domheap_pages+0x30e/0x3cc
> (XEN)    [<ffff82c48015d4d0>] put_page+0x6c/0x73
> (XEN)    [<ffff82c48015f8d8>] put_page_from_l1e+0x19f/0x1b5
> (XEN)    [<ffff82c48015eaf4>] free_page_type+0x25c/0x7b0
> (XEN)    [<ffff82c48015f11c>] __put_page_type+0xd4/0x292
> (XEN)    [<ffff82c48015f2f8>] put_page_type+0xe/0x23
> (XEN)    [<ffff82c480163a4f>] do_mmuext_op+0x6ff/0x14b8
> (XEN)    [<ffff82c480114235>] do_multicall+0x285/0x410
> (XEN)    [<ffff82c4801f01bf>] syscall_enter+0xef/0x149
> (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) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-02-07 11:56 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06 22:56 Xen-unstable panic: FATAL PAGE FAULT Mark Hurenkamp
2010-02-07 11:56 ` Keir Fraser [this message]
2010-04-30 20:52   ` Bastian Blank
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26  4:49 MaoXiaoyun
2010-08-26  7:39 ` Keir Fraser
2010-08-26  8:59   ` MaoXiaoyun
2010-08-26  9:11     ` Keir Fraser
2010-08-30  8:47       ` MaoXiaoyun
2010-08-30  9:02         ` Keir Fraser
2010-08-30 13:03           ` MaoXiaoyun
2010-08-30 13:16             ` Keir Fraser
2010-08-31 13:49               ` MaoXiaoyun
2010-08-31 14:49                 ` Keir Fraser
2010-08-31 15:00                   ` Keir Fraser
2010-08-31 15:07                   ` Jan Beulich
2010-08-31 16:01                     ` Keir Fraser
2010-08-31 16:22                       ` Jan Beulich
2010-08-31 16:35                         ` Keir Fraser
2010-08-31 17:03                           ` Keir Fraser
2010-09-01  7:17                             ` MaoXiaoyun
2010-09-01  7:40                               ` Keir Fraser
2010-09-01  8:05                               ` Jan Beulich
2010-09-01  8:32                                 ` MaoXiaoyun
2010-09-01  8:02                             ` Jan Beulich
2010-09-01  8:49                               ` Keir Fraser
2010-09-01  9:01                                 ` Jan Beulich
2010-09-01  9:28                                   ` Keir Fraser
2010-09-01  9:48                                   ` MaoXiaoyun
2010-09-01 10:09                                     ` Jan Beulich
2010-09-01  9:06                                 ` MaoXiaoyun
2010-09-01  9:23                                 ` MaoXiaoyun
2010-09-01  9:58                                   ` Keir Fraser
2010-09-01 10:21                                     ` MaoXiaoyun
2010-09-01 10:25                                       ` Keir Fraser
2010-09-01 10:28                                         ` Keir Fraser
2010-09-01 10:34                                       ` Jan Beulich
2010-09-01 11:32                                     ` MaoXiaoyun
2010-09-01  7:54                           ` Jan Beulich
2010-09-01  3:17                   ` MaoXiaoyun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C7945AEA.95CD%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=mark.hurenkamp@xs4all.nl \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).