From: "Jan Beulich" <jbeulich@novell.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: [BUG] double fault for sale ;)
Date: Mon, 29 May 2006 17:16:23 +0200 [thread overview]
Message-ID: <447B2C67.76E4.0078.0@novell.com> (raw)
In-Reply-To: <447B0C8D.2060005@suse.de>
Looks suspiciously like a stack overflow (comparing esp and ebp) - did you perhaps add (for debugging) some large stack
objects somewhere? Unfortunately the code isn't clever enough to provide a stack trace in such a situation... Jan
>>> Gerd Hoffmann <kraxel@suse.de> 29.05.06 17:00 >>>
Hi folks,
I'm busy rewriting the domain builder code a bit, to restruct the code
and make it better usable for other tasks than directly booting a
domain. While testing these bits I trapped into that one:
(XEN) CPU: 1
(XEN) EIP: e008:[<ff137512>] get_page_type+0x12/0x63d
(XEN) EFLAGS: 00010296
(XEN) CR3: 00000000
(XEN) eax: 33030001 ebx: ff1c1080 ecx: ff1d4080 edx: ff1d4080
(XEN) esi: 0000001a edi: ffbf5fac ebp: ffbf502c esp: ffbf4f84
(XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010
(XEN) ************************************
(XEN) CPU1 DOUBLE FAULT -- system shutdown
(XEN) System needs manual reset.
(XEN) ************************************
I think even Domain-0 shouldn't be able to crash xen like this, no?
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2006-05-29 15:16 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
2006-05-29 15:16 ` Jan Beulich [this message]
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=447B2C67.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=kraxel@suse.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 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.