From: Kaushik Barde <kbarde@huawei.com>
To: 'Jeremy Fitzhardinge' <jeremy@goop.org>,
'Qiangmin Lin' <linqiangmin@huawei.com>
Cc: olaf@aepfle.de, xen-devel@lists.xensource.com,
'fanliang' <fanliang@huawei.com>
Subject: RE: Domain0 crash on Bad L1 flags 800000
Date: Tue, 14 Dec 2010 13:20:36 -0800 [thread overview]
Message-ID: <00b201cb9bd4$c0cb6bc0$42624340$@com> (raw)
In-Reply-To: <4D07D54E.5040105@goop.org>
Maybe kernel compiled with PAE (and HIGHMEM64) options, Try recompiling
kernel without and see.
-Kaushik
-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jeremy
Fitzhardinge
Sent: Tuesday, December 14, 2010 12:37 PM
To: Qiangmin Lin
Cc: olaf@aepfle.de; xen-devel@lists.xensource.com; fanliang
Subject: Re: [Xen-devel] Domain0 crash on Bad L1 flags 800000
On 12/08/2010 06:53 PM, Qiangmin Lin wrote:
> Hi all, My dom0 kernel is 2.6.32.12-xen and Xen 3.4.2.
> I had closed "No Execute" in BIOS, but I see flags 800000 which mean
_PAGE_NX in crash information.
This looks like the same bug your colleague fanliang reported to me. Was
this after a long period of uptime? What was running at the time?
I'm curious why you're using that particular kernel, and why you're
running with NX disabled.
Thanks,
J
>
> (XEN) mm.c:720:d0 Bad L1 flags 800000
> (XEN) mm.c:4203:d0 ptwr_emulate: could not get_page_from_l1e()
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 0 (vcpu#2) crashed on cpu#2:
> (XEN) ----[ Xen-3.4.2 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 2
> (XEN) RIP: e033:[<ffffffffa0375fcc>]
> (XEN) RFLAGS: 0000000000010292 EM: 0 CONTEXT: pv guest
> (XEN) rax: ffffffffa0376120 rbx: ffff880075222000 rcx:
0000000000000001
> (XEN) rdx: ffff88000402b000 rsi: 0000000000000000 rdi:
ffff880075222048
> (XEN) rbp: ffff880075222000 rsp: ffff8800a5db5ff8 r8:
ffffe8ffffeb0588
> (XEN) r9: 0000000000000001 r10: 0000000000000000 r11:
ffffffffa0376120
> (XEN) r12: ffff880075222048 r13: ffff8800c8a69000 r14:
ffff880075222058
> (XEN) r15: 00007f44fd7802d0 cr0: 0000000080050033 cr4:
00000000000026f0
> (XEN) cr3: 00000008dbaf8000 cr2: ffff8800a5db5ff0
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffff8800a5db5ff8:
> (XEN) ffff8800c8a69000 ffff880075222000 ffff88002bcc6500
ffffffffa0376144
> (XEN) ffff8800c8a69000 ffff8800888f7380 ffff8800c8a690f8
ffffffffa0377e3c
> (XEN) 0000000000000000 0000000000000000 0000000000000000
0000000000000000
> (XEN) ffff8800c8a69000 ffff880075222000 ffff88002bcc6500
ffff8800c8a69000
> (XEN) ffff880075222058 ffffffffa0376161 ffff8800c8a69000
ffff8800888f7380
> (XEN) ffff8800c8a690f8 ffffffffa0377e3c 0000000000000000
0000000000000000
> (XEN) 0000000000000000 0000000000000000 ffff8800c8a69000
ffff880075222000
> (XEN) ffff88002bcc6500 ffff8800c8a69000 ffff880075222058
ffffffffa0376161
> (XEN) ffff8800c8a69000 ffff8800888f7380 ffff8800c8a690f8
ffffffffa0377e3c
> (XEN) 0000000000000000 0000000000000000 0000000000000000
0000000000000000
> (XEN) ffff8800c8a69000 ffff880075222000 ffff88002bcc6500
ffff8800c8a69000
> (XEN) ffff880075222058 ffffffffa0376161 ffff8800c8a69000
ffff8800888f7380
> (XEN) ffff8800c8a690f8 ffffffffa0377e3c 0000000000000000
0000000000000000
> (XEN) 0000000000000000 0000000000000000 ffff8800c8a69000
ffff880075222000
> (XEN) ffff88002bcc6500 ffff8800c8a69000 ffff880075222058
ffffffffa0376161
> (XEN) ffff8800c8a69000 ffff8800888f7380 ffff8800c8a690f8
ffffffffa0377e3c
> (XEN) 0000000000000000 0000000000000000 0000000000000000
0000000000000000
> (XEN) ffff8800c8a69000 ffff880075222000 ffff88002bcc6500
ffff8800c8a69000
> (XEN) ffff880075222058 ffffffffa0376161 ffff8800c8a69000
ffff8800888f7380
> (XEN) ffff8800c8a690f8 ffffffffa0377e3c 0000000000000000
0000000000000000
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> [1182692.327659] BUG: unable to handle kernel
> please help me
> L
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-12-14 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 2:53 Domain0 crash on Bad L1 flags 800000 Qiangmin Lin
2010-12-14 20:36 ` Jeremy Fitzhardinge
2010-12-14 21:20 ` Kaushik Barde [this message]
2010-12-14 21:57 ` Jeremy Fitzhardinge
2010-12-14 22:03 ` Kaushik Barde
2010-12-14 22:19 ` Jeremy Fitzhardinge
2010-12-14 22:40 ` Kaushik Barde
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='00b201cb9bd4$c0cb6bc0$42624340$@com' \
--to=kbarde@huawei.com \
--cc=fanliang@huawei.com \
--cc=jeremy@goop.org \
--cc=linqiangmin@huawei.com \
--cc=olaf@aepfle.de \
--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).