From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: [BUG] double fault for sale ;)
Date: Tue, 30 May 2006 18:49:45 +0200 [thread overview]
Message-ID: <447C77A9.3010502@suse.de> (raw)
In-Reply-To: <E1Fl5UV-00021i-00@mta1.cl.cam.ac.uk>
> Gerd,
>
> Can you please let me know whether the attached patch fixes the
> crash for you? I suspect a bug in your modified builder triggered a
> broken error path in Xen -- so this patch will hopefully turn the Xen
> crash into a failure of your modified builder. :-)
Yep, its fixed, now the newly created domain crashes, probably during
kernels initial page table setup (pfn 0 looks like that), which likely
is a builder bug.
I get this now:
(XEN) DOM1: (file=mm.c, line=1528) Bad type (saw 33030001 != exp
e0000000) for mfn c72 (pfn 0)
(XEN) DOM1: (file=mm.c, line=505) Error getting mfn c72 (pfn 0) from L1
entry 00c72063 for dom1
(XEN) DOM1: (file=mm.c, line=3054) ptwr: Could not revalidate l1 page
(XEN) domain_crash called from mm.c:3055
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: e019:[<c0101347>]
(XEN) EFLAGS: 00000286 CONTEXT: guest
[ ... ]
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-05-30 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 15:00 [BUG] double fault for sale ;) Gerd Hoffmann
2006-05-29 15:06 ` Keir Fraser
2006-05-29 16:03 ` Gerd Hoffmann
2006-05-29 16:11 ` Keir Fraser
2006-05-30 14:02 ` Gerd Hoffmann
2006-05-30 14:08 ` Keir Fraser
2006-05-30 14:46 ` Keir Fraser
2006-05-30 16:49 ` Gerd Hoffmann [this message]
2006-05-29 15:16 ` Jan Beulich
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=447C77A9.3010502@suse.de \
--to=kraxel@suse.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.