From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 2.6.32.27 dom0 + latest xen staging boot failure
Date: Tue, 25 Jan 2011 09:39:50 -0500 [thread overview]
Message-ID: <20110125143950.GA7238@dumpdata.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D5301943055D7@orsmsx505.amr.corp.intel.com>
On Mon, Jan 24, 2011 at 06:26:49PM -0800, Kay, Allen M wrote:
> I'm encountering following boot failure with the latest pvops 2.6.32.27 dom0 and xen staging tree on my system. Attached file contains the full serial console log.
>
> Has anyone seen it?
What does the 0xffffffff8100cd18 translate to in your System.map of your Linux kernel?
>
> ....
>
> init_memory_mapping: 0000000000000000-000000009b000000
> init_memory_mapping: 0000000100000000-000000023a6f4000
> (XEN) mm.c:802:d0 Bad L1 flags 400000
> (XEN) mm.c:1204:d0 Failure in alloc_l1_table: entry 365
> (XEN) mm.c:2142:d0 Error while validating mfn 1c3eb4 (pfn 1454c) for type 100000
> 0000000000: caf=8000000000000003 taf=1000000000000001
> (XEN) mm.c:2965:d0 Error while pinning mfn 1c3eb4
> (XEN) traps.c:451:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-4.1.0-rc2-pre x86_64 debug=y Tainted: C ]----
> (XEN) CPU: 0
> (XEN) RIP: e033:[<ffffffff8100cd18>]
> (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest
> (XEN) rax: 00000000ffffffea rbx: ffff88001454c000 rcx: ffffffff8261f000
> (XEN) rdx: 00000000deadbeef rsi: 00000000deadbeef rdi: 00000000deadbeef
> (XEN) rbp: ffffffff816c1bf8 rsp: ffffffff816c1b98 r8: 00003ffffffff000
> (XEN) r9: ffff880000000000 r10: 00000000deadbeef r11: 0000000000000000
> (XEN) r12: ffffffffff400b10 r13: 0000000000000162 r14: ffffffffff440000
> (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026f0
> (XEN) cr3: 00000001c1001000 cr2: 0000000000000000
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffffffff816c1b98:
> (XEN) ffffffff8261f000 0000000000000000 ffffffff8100cd18 000000010000e030
> (XEN) 0000000000010082 ffffffff816c1bd8 000000000000e02b ffffffff8100cd14
> (XEN) ffffffff00000000 00000000001c3eb4 ffffffff81702c18 ffff88001454c000
> (XEN) ffffffff816c1c18 ffffffff81980f27 ffffffff816c1c38 000000000001454c
> (XEN) ffffffff816c1c38 ffffffff81036cd6 ffffffffff400b10 000000016c400000
> (XEN) ffffffff816c1cd8 ffffffff819ba427 00000001c3350067 8000000000000163
> (XEN) 0000000100000001 ffffffffff400000 000000008100cb50 80000000000001e3
> (XEN) 8000000000000163 000000023a6f4000 000000016c600000 0000000000000000
> (XEN) ffffffff816c1ca8 000000001454c000 ffffffff816c1cd8 ffff880001002028
> (XEN) ffffffffff400000 0000000140000000 0000000140000000 000000023a6f4000
> (XEN) ffffffff816c1d68 ffffffff819ba65d ffffffff8100c407 8000000000000163
> (XEN) ffff880001002000 0000000000000000 0000000000000000 0000000000000004
> (XEN) 00000001816c1d68 0000000000000000 0000000000000000 00000000143e9000
> (XEN) ffffffff8108a086 000000023a6f4000 ffffffff81001880 ffff88023a6f4000
> (XEN) 000000023a6f4000 ffff88023a6f4000 ffffffff816c1dc8 ffffffff819ba7b8
> (XEN) ffff880100000000 0000000000000000 ffffffff816c1d98 000000009b000000
> (XEN) ffffffff816c1dc8 ffffffff816c1e20 0000000000000001 0000000000000001
> (XEN) 000000023a6f4000 0000000000000000 ffffffff816c1eb8 ffffffff81465e66
> (XEN) 0000000000000000 0000000000000000 0000050100000000 ffffffff816c1e88
> (XEN) 0000000000000000 0000000100000000 0000000100000000 000000023a6f4000
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-01-25 14:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 2:26 2.6.32.27 dom0 + latest xen staging boot failure Kay, Allen M
2011-01-25 14:39 ` Konrad Rzeszutek Wilk [this message]
2011-01-25 18:49 ` Kay, Allen M
2011-01-25 19:07 ` Konrad Rzeszutek Wilk
2011-01-25 19:24 ` Kay, Allen M
2011-01-25 20:10 ` Konrad Rzeszutek Wilk
2011-01-25 21:26 ` Kay, Allen M
2011-01-26 2:41 ` Kay, Allen M
2011-01-26 16:14 ` Konrad Rzeszutek Wilk
2011-01-26 18:46 ` Kay, Allen M
2011-01-26 21:28 ` Konrad Rzeszutek Wilk
2011-01-26 21:53 ` Kay, Allen M
2011-01-27 1:16 ` Kay, Allen M
2011-01-27 11:59 ` Stefano Stabellini
2011-01-27 18:51 ` Kay, Allen M
2011-01-28 15:28 ` Konrad Rzeszutek Wilk
2011-01-28 15:47 ` Konrad Rzeszutek Wilk
2011-02-11 1:03 ` Kay, Allen M
2011-02-11 2:56 ` Jeremy Fitzhardinge
2011-02-11 3:07 ` Kay, Allen M
2011-02-11 17:06 ` Jeremy Fitzhardinge
2011-02-11 19:00 ` Kay, Allen M
2011-02-11 19:11 ` Kay, Allen M
2011-02-11 22:55 ` Jeremy Fitzhardinge
2011-02-15 4:28 ` Kay, Allen M
2011-02-15 14:58 ` Stefano Stabellini
2011-02-16 3:08 ` Kay, Allen M
2011-02-16 17:19 ` Stefano Stabellini
2011-02-11 14:51 ` Stefano Stabellini
2011-02-11 22:10 ` Kay, Allen M
2011-01-27 14:45 ` Konrad Rzeszutek Wilk
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=20110125143950.GA7238@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=allen.m.kay@intel.com \
--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.