From: "Christopher S. Aker" <caker@theshore.net>
To: xen devel <xen-devel@lists.xensource.com>
Subject: Xen 3.2.1-rc1: FATAL PAGE FAULT
Date: Thu, 03 Apr 2008 00:34:54 -0400 [thread overview]
Message-ID: <47F45E6E.9000502@theshore.net> (raw)
Xen: 3.2.1-rc1 (I can get the exact changeset if needed)
domU: 2.6.16.33 PAE
(XEN) ----[ Xen-3.2.1-rc1 x86_64 debug=y Not tainted ]----
(XEN) CPU: 3
(XEN) RIP: e008:[<ffff828c8013dee4>] put_page_type+0x17/0x107
(XEN) RFLAGS: 0000000000210282 CONTEXT: hypervisor
(XEN) rax: 00001c9f2d2abca8 rbx: ffff9f232d2abca8 rcx: 0000000080000000
(XEN) rdx: 000000b72dedde51 rsi: 00000000002f25fd rdi: ffff9f232d2abca8
(XEN) rbp: ffff8300cee0fcb8 rsp: ffff8300cee0fc98 r8: 0000000000000000
(XEN) r9: 00000000deadbeef r10: ffff828c801c5bf0 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: ffff9f232d2abca8 r14: ffff8300cfc84100
(XEN) r15: ffff8300cfc84118 cr0: 000000008005003b cr4: 00000000000026b0
(XEN) cr3: 000000062ffd7000 cr2: ffff9f232d2abcc0
(XEN) ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0000 cs: e008
(XEN) Xen stack trace from rsp=ffff8300cee0fc98:
(XEN) ffff8300cee0fcd8 ffff9f232d2abca8 0000000000000000
00000000002f25fd
(XEN) ffff8300cee0fcd8 ffff828c8013b409 ffff8300cfc850f8
ffff8302f25fd000
(XEN) ffff8300cee0fd08 ffff828c8013c06d ffff8300cfc84100
ffff8284075def88
(XEN) 0000000068000001 ffff8300cfc850f8 ffff8300cee0fd38
ffff828c8013de5a
(XEN) 0000000060000001 0000000068000000 ffff8284075def88
ffff8300cfc850f8
(XEN) ffff8300cee0fd68 ffff828c8013df63 ffff8284075def88
ffff8284075def88
(XEN) ffff8284075def88 ffff8300cfc84100 ffff8300cee0fdb8
ffff828c80131680
(XEN) 0000000088000000 0000000080000000 ffff8300cee0ff28
ffff8300cfc84100
(XEN) ffff8300cfc84100 00000000b31fc868 0000000000000000
0000000000000000
(XEN) ffff8300cee0fdd8 ffff828c80131a94 ffff8300cfc84100
0000000000000000
(XEN) ffff8300cee0fe08 ffff828c80105638 ffff8300cee0fe18
ffff828c80114d70
(XEN) 00000000b31fc868 fffffffffffffff3 ffff8300cee0ff08
ffff828c8010479f
(XEN) ffff8300cee0fe48 ffff8300cee34130 0000000000000003
0001b932a9ddc50a
(XEN) 0000000000200282 0000000000000000 0000000500000002
083ca594b7b50067
(XEN) 0832ab4c011fc898 b7dadc50b7b5d68c b7a733e400000001
00000001b79fccdc
(XEN) 080facafb31fc8c8 081361e008313e98 080797e7b76c1934
00000000b76c1950
(XEN) b7da802c00000060 b761db6c00000000 0805946cb31fc8e8
b7da802cb761db6c
(XEN) b7dab6a000000000 00000002b5d5451c a5dba1eea5dba1ee
0000001f00000000
(XEN) ffff8300cee0fee8 ffff8300cee34100 0000000000000000
0000000000000000
(XEN) 0000000000000000 0000000000000000 00007cff311f00b7
ffff828c801bdd50
(XEN) Xen call trace:
(XEN) [<ffff828c8013dee4>] put_page_type+0x17/0x107
(XEN) [<ffff828c8013b409>] put_page_from_l3e+0x3f/0x4e
(XEN) [<ffff828c8013c06d>] free_l3_table+0x78/0xc4
(XEN) [<ffff828c8013de5a>] free_page_type+0x1d4/0x247
(XEN) [<ffff828c8013df63>] put_page_type+0x96/0x107
(XEN) [<ffff828c80131680>] relinquish_memory+0xce/0x262
(XEN) [<ffff828c80131a94>] domain_relinquish_resources+0xd1/0x1b0
(XEN) [<ffff828c80105638>] domain_kill+0x77/0x164
(XEN) [<ffff828c8010479f>] do_domctl+0x4dd/0xc1e
(XEN) [<ffff828c801bdd50>] compat_tracing_off+0xb/0x64
(XEN)
(XEN) Pagetable walk from ffff9f232d2abcc0:
(XEN) L4[0x13e] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 3:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: ffff9f232d2abcc0
(XEN) ****************************************
next reply other threads:[~2008-04-03 4:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 4:34 Christopher S. Aker [this message]
2008-04-03 14:04 ` Xen 3.2.1-rc1: FATAL PAGE FAULT Christopher S. Aker
2008-04-03 15:55 ` Keir Fraser
2008-04-22 18:19 ` Xen 3.2.1-rc5: " Christopher S. Aker
2008-04-22 18:46 ` Keir Fraser
2008-04-22 19:39 ` Christopher S. Aker
2008-04-22 20:21 ` Keir Fraser
2008-04-28 14:02 ` Christopher S. Aker
2008-04-28 14:44 ` Keir Fraser
2008-04-28 15:00 ` Christopher S. Aker
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=47F45E6E.9000502@theshore.net \
--to=caker@theshore.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.