From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: dom0 crash with unstable Date: Tue, 06 Oct 2009 10:54:42 -0700 Message-ID: <4ACB8462.1040102@goop.org> References: <64bddf0e0909301105l18c6a3f6ie59af261b1532fe2@mail.gmail.com> <4AC3EE07.3010000@goop.org> <64bddf0e0910010635wc085961tf55000d4305da2bf@mail.gmail.com> <4AC518A1.8080905@goop.org> <64bddf0e0910060813v2f2d4149wf2898653719d6ba3@mail.gmail.com> <4ACB70F0.5020502@goop.org> <64bddf0e0910061023t58828929i99da6a63155e82c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <64bddf0e0910061023t58828929i99da6a63155e82c@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 10:23, Bryan D. Payne wrote: >> Is it ever stable? What happens if you set dom0_mem to 4G or less? >> > It still crashes, even with 2G of dom0 memory. > What console output do you get? >> 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. >> > Yes, this seems to work. Typing 0 dumped info for each of the cores > (i.e., 15 vcpu states). I've attached the output. > Could you map the RIP values to a symbol with gdb? From a quick look, it seems that most or all of the cpus are at the same place. No, vcpu 8 is doing something else at least. What happens if you boot dom0 with fewer cpus? Do you have CONFIG_PARAVIRT_SPINLOCKS enabled? J