From: Gerd Hoffmann <kraxel@suse.de>
To: Xen devel list <xen-devel@lists.xensource.com>
Subject: xen unstable crashes
Date: Tue, 18 Jul 2006 11:56:48 +0200 [thread overview]
Message-ID: <44BCB060.4020409@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
Hi,
$subject says all. This is an unpatched unstable tree (10711) and an
attempt to boot the suse linux 10.1 xen kernel (kernel-xen-2.6.16.13-4)
with an ttylinux initrd and features=auto_translated_physmap.
Trying to boot other kernels in shadow-translated mode doesn't work
either, but they at least don't take down xen, only the guest crashes.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
[-- Attachment #2: crash --]
[-- Type: text/plain, Size: 1682 bytes --]
(XEN) (file=extable.c, line=77) Pre-exception: ff105607 -> 00000000
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: e008:[<ff105607>] evtchn_set_pending+0x17/0x110
(XEN) EFLAGS: 00210096 CONTEXT: hypervisor
(XEN) eax: 00000000 ebx: ffbebd80 ecx: 0000000b edx: ff1d8a00
(XEN) esi: 00000000 edi: 00000013 ebp: 000000b0 esp: ff19df28
(XEN) cr0: 8005003b cr3: 3e990000
(XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from esp=ff19df28:
(XEN) ff1a5200 ffbfbd80 ffbfe280 01c9c380 ffbebd80 00000001 00000013 ff12012f
(XEN) 00000000 0000000b ff112163 f8fbe080 00000000 00000000 ff1b5800 ff19dfb4
(XEN) ff19dfb4 ffbfe280 ffbfe280 ff11cab1 ff19df7c ff19dfb4 ffbed280 00000000
(XEN) ff19dfb4 ffbfe280 ffbfe280 00000000 00b00000 ff119e75 0000e008 00200246
(XEN) c05ae000 c05aff84 00000000 00000001 00000000 00000000 00000001 c05ae000
(XEN) c05aff84 00000000 000d0000 c01013a7 00000061 00200246 c05aff74 00000069
(XEN) 0000007b 0000007b 00000000 00000000 00000000 ffbfe280
(XEN) Xen call trace:
(XEN) [<ff105607>] evtchn_set_pending+0x17/0x110
(XEN) [<ff12012f>] do_IRQ+0xaf/0x1d0
(XEN) [<ff112163>] do_block+0x43/0xa0
(XEN) [<ff11cab1>] common_interrupt+0x41/0x50
(XEN) [<ff119e75>] idle_loop+0x15/0x50
(XEN)
(XEN) Faulting linear address: 0000000c
(XEN) Pagetable walk from 0000000c:
(XEN) L2 = 325ca067 0001bbca
(XEN) L1 = 00000000 ffffffff
(XEN) ************************************
(XEN) CPU0 FATAL TRAP 14 (page fault), ERROR_CODE 0000, IN INTERRUPT CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2006-07-18 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 9:56 Gerd Hoffmann [this message]
2006-07-18 10:14 ` xen unstable crashes Keir Fraser
2006-07-18 10:37 ` Gerd Hoffmann
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=44BCB060.4020409@suse.de \
--to=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.