From: Scott Garron <xen-devel@sce.pridelands.org>
To: xen-devel@lists.xensource.com
Subject: BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39
Date: Mon, 25 Apr 2011 20:04:20 -0400 [thread overview]
Message-ID: <4DB60C04.6050802@sce.pridelands.org> (raw)
It appears that a bug that I had reported back in August
(
http://lists.xensource.com/archives/html/xen-devel/2010-08/msg01798.html
) seems to have been fixed in a recent update (
http://lists.xensource.com/archives/html/xen-devel/2011-04/msg00742.html
) ... at least it looks like the same bug to me. I've been trying, over
the past few days, to move to using a newer version with the fix applied
on a test machine and once I get it working, would like to update my
production server. It would be nice to be able to get back to doing
backups again. :)
I don't know whether or not the fix for that bug worked, though,
because I can't seem to get any combination of a newer hypervisor and
Jeremy's xen.git xen/stable-2.6.32.x branch to boot at all. I can get
the kernel to boot without Xen, but not with it.
Here a snippet of serial output near the crash:
[ 0.310132] xen_balloon: Initialising balloon driver with page order 0.
[ 0.313482] last_pfn = 0x1d9ff0 max_arch_pfn = 0x400000000
[ 0.316665] BUG: unable to handle kernel paging request at
ffffea0003800028
[ 0.316665] IP: [<ffffffff819a8aea>] balloon_init+0x20b/0x25e
[ 0.316665] PGD c402067 PUD c403067 PMD 0
[ 0.316665] Oops: 0002 [#1] SMP
Full serial output, lspci -vvv, .config, dmidecode, and grub2 conf can
be retrieved here:
http://www.pridelands.org/~simba/xen-debug/
git log:
commit 057b171345d94c785d7e8bb21302c5d1a23ea048
Merge: 6dfaa17 145fff1
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Fri Apr 22 13:46:05 2011 -0700
git branch:
xen/next-2.6.32
* xen/stable-2.6.32.x
hg log:
changeset: 23246:eb4505f8dd97
tag: tip
user: Tim Deegan <Tim.Deegan@citrix.com>
date: Wed Apr 20 12:02:51 2011 +0100
summary: xen/x86: re-enable xsave by default now that it supports
live migration.
I've tried booting with no dom0_mem option just to see if that made
any difference. I also tried using the stable tarball of xen-4.1.0, the
current xen-4.1-testing.hg, as well as xen-unstable.hg. All yield
exactly the same results. Any ideas?
--
Scott Garron
next reply other threads:[~2011-04-26 0:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:04 Scott Garron [this message]
2011-04-26 3:15 ` BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39 Konrad Rzeszutek Wilk
2011-04-26 5:03 ` Scott Garron
2011-04-27 20:09 ` Konrad Rzeszutek Wilk
2011-04-27 23:45 ` Scott Garron
[not found] ` <20110428183019.GA9852@dumpdata.com4DBA1EA4.5010004@sce.pridelands.org>
2011-04-28 18:30 ` Konrad Rzeszutek Wilk
2011-04-29 0:15 ` Scott Garron
2011-04-29 2:12 ` Scott Garron
2011-04-29 14:43 ` Dan Magenheimer
2011-04-29 16:56 ` Scott Garron
2011-04-29 19:38 ` Dan Magenheimer
2011-04-29 23:08 ` Scott Garron
2011-05-04 15:58 ` Konrad Rzeszutek Wilk
2011-05-04 19:19 ` Scott Garron
2011-05-04 19:35 ` Konrad Rzeszutek Wilk
2011-05-04 20:17 ` Scott Garron
2011-05-04 20:23 ` Konrad Rzeszutek Wilk
2011-05-04 21:55 ` Scott Garron
2011-05-04 22:16 ` Konrad Rzeszutek Wilk
2011-05-04 23:23 ` Scott Garron
2011-05-05 18:34 ` Konrad Rzeszutek Wilk
2011-05-05 20:48 ` Scott Garron
2011-05-05 21:06 ` Konrad Rzeszutek Wilk
2011-06-06 18:00 ` Scott Garron
2011-06-06 19:17 ` Pasi Kärkkäinen
2011-06-06 21:33 ` Scott Garron
2011-06-07 19:19 ` Konrad Rzeszutek Wilk
2011-06-08 18:25 ` Scott Garron
2011-06-08 19:29 ` Konrad Rzeszutek Wilk
2011-06-09 20:04 ` Scott Garron
2011-06-10 12:59 ` Konrad Rzeszutek Wilk
2011-06-10 16:51 ` Scott Garron
2011-06-13 22:03 ` Konrad Rzeszutek Wilk
2011-06-13 23:20 ` Scott Garron
2011-06-14 13:55 ` BUG: unable to handle kernel NULL pointer dereference at IP: [<ffffffff8105ae4c>] process_one_work+ Konrad Rzeszutek Wilk
2011-06-14 21:55 ` Scott Garron
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=4DB60C04.6050802@sce.pridelands.org \
--to=xen-devel@sce.pridelands.org \
--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).