From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: dom0 crash with unstable Date: Tue, 06 Oct 2009 09:31:44 -0700 Message-ID: <4ACB70F0.5020502@goop.org> References: <64bddf0e0909301105l18c6a3f6ie59af261b1532fe2@mail.gmail.com> <4AC3EE07.3010000@goop.org> <64bddf0e0910010635wc085961tf55000d4305da2bf@mail.gmail.com> <4AC518A1.8080905@goop.org> <64bddf0e0910060813v2f2d4149wf2898653719d6ba3@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <64bddf0e0910060813v2f2d4149wf2898653719d6ba3@mail.gmail.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: "Bryan D. Payne" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 10/06/09 08:13, Bryan D. Payne wrote: > Ok, so I tried setting dom0_mem to a variety of values less than 32GB. > I'm still getting a crash, but now it is more random. Basically, I'm > watching the boot process via a serial line, and instead of seeing the > dom0 crash output that I posted before, I'm simply seeing the output > stop, and the boot process hanging, in a different spot with each > boot. Removing the dom0_mem value beings me back to the behavior I > had before, where the dom0 crash output shows up reliably each time. > That's mysterious. My first thought is that this is a separate problem. Is it ever stable? What happens if you set dom0_mem to 4G or less? Is the console responsive when the kernel hangs? That is, can you type "Ctrl-A Ctrl-A Ctrl-A" to get Xen, then enter debug keys? '0' (zero) should dump the context for dom0 and give some clue about where it is dying. Thanks, J