From: Scott Garron <xen-devel@sce.pridelands.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
xen-devel@lists.xensource.com,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39
Date: Thu, 09 Jun 2011 16:04:23 -0400 [thread overview]
Message-ID: <4DF12747.2090900@sce.pridelands.org> (raw)
In-Reply-To: <20110608192916.GA4909@dumpdata.com>
On 06/08/2011 03:29 PM, Konrad Rzeszutek Wilk wrote:
> Can you do (while not having acpi=off) and using 'apic=debug' on you
> Linux line:
>
> 1). Run Ctrl-A couple of times and hit the '*' and send the output. I
> am really curious to see what the IOAPIC thinks about the
> interrupts.
>
> 2). Increase the dom0_mem= to say 1G?
Ok, I've done these 2 things and the output is at:
http://pridelands.org/~simba/xen/hailstorm-fullserial20110609-02.txt
After changing dom0_mem to 1G instead of 512M, the machine hangs at
"Switching to clocksource xen" instead of "Trying to unpack rootfs image
as initramfs..."
As an added step, I also recompiled the latest Mercurial pull of
xen-unstable.hg and am running with that instead of the one I had from a
month or so ago. I'm not sure if that is what is making it not end up
with a Kernel OOPS/BUG message or if it is the apic=debug option.
acpi=off is definitely not on the command line, now, though, and
it's not giving the OOPS that it was before. It's just hanging/freezing.
> 3). Try the attached patch (not compile tested)
I did not see an attachment on your last e-mail.
--
Scott Garron
next prev parent reply other threads:[~2011-06-09 20:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:04 BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39 Scott Garron
2011-04-26 3:15 ` 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 [this message]
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=4DF12747.2090900@sce.pridelands.org \
--to=xen-devel@sce.pridelands.org \
--cc=dan.magenheimer@oracle.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--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.