From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>,
Horms <horms@verge.net.au>
Subject: Re: Re: [PATCH] Xen Guest Kexec
Date: Tue, 07 Mar 2006 15:43:21 +0100 [thread overview]
Message-ID: <440D9C09.1060502@suse.de> (raw)
In-Reply-To: <2ee1c54430552a056565f00098be0a0a@cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
> The assertion is spurious. I've tightened up the assertion condition in
> changeset 9157:51c59d5d7... "Tighten up the assertion conditions in the
> GUEST_MODE() macro.".
Looks like I'm triggering lots of funny bugs, see log below ...
Current plan is to get kexec work first with
features=auto_translated_physmap due to some non-trivial issues with
handling the p2m map. That attempt killed Xen too ;)
cheers,
Gerd
--
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.
http://www.suse.de/~kraxel/just-married.jpeg
[-- Attachment #2: oops --]
[-- Type: text/plain, Size: 2762 bytes --]
(XEN) get_mfn_from_gpfn_foreign(d->id=3, gpfn=65786) => 0 l2e=00000000
(XEN) get_mfn_from_gpfn_foreign(d->id=3, gpfn=30312) => 0 l2e=00000000
(XEN) ----[ Xen-3.0.0 Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: e008:[<ff17ad4f>] __shadow_get_l2e+0x77/0x80
(XEN) EFLAGS: 00010246 CONTEXT: hypervisor
(XEN) eax: fe7f9000 ebx: ffbf5ed0 ecx: ffbb1080 edx: fe7f9000
(XEN) esi: 033b6fd4 edi: 00000000 ebp: ffbf5df0 esp: ffbf5dd8
(XEN) cr0: 8005003b cr3: 001b6000
(XEN) ds: e010 es: e010 fs: e010 gs: e021 ss: e010 cs: e008
(XEN) Xen stack trace from esp=ffbf5dd8:
(XEN) 00000000 ffbb0104 00000000 19a16063 00000000 00000001 ffbf5eb0 ff17ce17
(XEN) ffbb1080 0000b000 ffbf5e2c 000003ff e0000029 e0000029 ffbe4080 20000000
(XEN) e0000028 ffbf5fb4 ffbf5e40 00000286 fc67f270 ffbe4080 00000092 ffbaf0f0
(XEN) 00000400 00019047 fec56000 fec58000 fec57000 00000001 00000000 00000000
(XEN) 00000400 00000000 00000000 00000000 000003ff 00000000 000003ff ff13cafd
(XEN) fec56000 fec58000 fec57000 00000001 00000001 00000020 fc67f270 ffbe4080
(XEN) 00000001 00000055 ffbf5eb0 ff17d798 00000001 ffbf5ed0 ffbf5ef0 ff17d6e7
(XEN) ffbe4080 20000000 000191de 00000002 ffbf5f08 00000020 00000000 1aa1a061
(XEN) 1aa1a063 00000000 00000001 fec55008 ff1bd080 ff1179ef ffbf5f20 ff135bea
(XEN) ffbe4080 ffbb1108 ffbf5f20 ff128bd5 00000000 ffffffff ffbf5f60 00000001
(XEN) 00000000 00000001 ffbf5f30 ff13a915 ffbe4080 ffbe431c ffbf5f60 ff105732
(XEN) ffbe4080 ffbe4318 00000000 00000001 ff1be05c ffbf2900 ffbe4080 00000000
(XEN) 00000001 00000001 ffbf5f90 ff11b5fd 00000006 ff1be480 00000001 ff1be480
(XEN) ffbf5f98 ff105545 ffbe4080 00000006 00000040 00000001 ffbf5fb0 ff12681a
(XEN) ffbf5fa8 ff105583 ffbe4080 00000000 00000000 00000001 ffbf5ea8 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 000d0000 0000420d
(XEN) 0000e019 00000246 033b6fd4 0000e021 0000e021 0000e021 0000e021 0000e021
(XEN) 00000001 ffbf6080
(XEN) Xen call trace:
(XEN) [<ff17ad4f>] __shadow_get_l2e+0x77/0x80
(XEN) [<ff17ce17>] resync_all+0x3bd/0x852
(XEN) [<ff17d6e7>] __shadow_sync_all+0x1c9/0x251
(XEN) [<ff135bea>] shadow_sync_all+0x90/0x195
(XEN) [<ff13a915>] cleanup_writable_pagetable+0x42/0x86
(XEN) [<ff105732>] domain_shutdown_finalise+0x1ad/0x277
(XEN) [<ff11b5fd>] do_softirq+0xa1/0xb8
(XEN) [<ff12681a>] idle_loop+0x5b/0x5d
(XEN)
(XEN) Pagetable walk from fe7f9000:
(XEN) L2 = 00000000 55555555
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) CPU1 FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: fe7f9000
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-03-07 14:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 22:49 Re: [PATCH] Xen Guest Kexec Ian Pratt
2006-02-27 7:10 ` Keir Fraser
2006-02-27 15:34 ` Gerd Hoffmann
2006-02-27 16:19 ` Keir Fraser
2006-03-01 12:09 ` Gerd Hoffmann
2006-03-01 14:10 ` Gerd Hoffmann
2006-03-01 15:03 ` Keir Fraser
2006-03-01 17:35 ` Keir Fraser
2006-03-02 9:16 ` Gerd Hoffmann
2006-03-02 9:43 ` Keir Fraser
2006-03-02 11:34 ` Gerd Hoffmann
2006-03-02 11:55 ` Keir Fraser
2006-03-02 16:36 ` Gerd Hoffmann
2006-03-02 16:48 ` Keir Fraser
2006-03-03 8:39 ` Gerd Hoffmann
2006-03-03 9:14 ` Keir Fraser
2006-03-03 9:35 ` Keir Fraser
2006-03-03 11:19 ` Gerd Hoffmann
2006-03-06 14:15 ` Gerd Hoffmann
2006-03-06 16:04 ` Michael Vrable
2006-03-07 13:06 ` Gerd Hoffmann
2006-03-07 13:42 ` Keir Fraser
2006-03-07 14:43 ` Gerd Hoffmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-07 17:16 Mark Williamson
2006-02-23 10:52 ` Horms
2006-02-23 11:22 ` Gerd Hoffmann
2006-02-23 11:32 ` Mark Williamson
2006-02-23 13:03 ` Gerd Hoffmann
2006-02-23 14:49 ` Mark Williamson
2006-02-24 14:35 ` Gerd Hoffmann
2006-02-27 14:29 ` Mark Williamson
2006-02-27 15:39 ` Gerd Hoffmann
2006-02-23 11:36 ` Mark Williamson
2006-02-27 3:32 ` Horms
2006-02-27 14:58 ` Mark Williamson
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=440D9C09.1060502@suse.de \
--to=kraxel@suse.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=horms@verge.net.au \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mark.williamson@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.