From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Garron 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 Message-ID: <4DF12747.2090900@sce.pridelands.org> References: <20110504221627.GA8422@dumpdata.com> <4DC1DFE9.3080604@sce.pridelands.org> <20110505183408.GA10142@dumpdata.com> <4DC30D24.7040005@sce.pridelands.org> <20110505210629.GB18972@dumpdata.com> <4DED15B3.7080701@sce.pridelands.org> <20110606191725.GZ32595@reaktio.net> <4DED478E.5070607@sce.pridelands.org> <20110607191949.GB2075@dumpdata.com> <4DEFBE7F.5060909@sce.pridelands.org> <20110608192916.GA4909@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110608192916.GA4909@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Jeremy Fitzhardinge List-Id: xen-devel@lists.xenproject.org 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