From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvops0 kernel 2.6.32.21 does not boot Date: Wed, 22 Sep 2010 10:23:02 -0700 Message-ID: <4C9A3B76.9030705@goop.org> References: <4C8E2AC5.8090602@hfp.de> <4C8EA02F.5070402@goop.org> <4C90A2ED.2060805@hfp.de> <4C9103A9.9050606@goop.org> <4C9112D1.902@hfp.de> <4C912D31.5020209@goop.org> <4C91ECBD.6030105@hfp.de> <4C9A2C16.80709@hfp.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C9A2C16.80709@hfp.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andreas Kinzler Cc: jeremy.fitzhardinge@citrix.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 09/22/2010 09:17 AM, Andreas Kinzler wrote: > Hello Jeremy, > >> On 15.09.2010 22:31, Jeremy Fitzhardinge wrote: >>> On 09/15/2010 11:39 AM, Andreas Kinzler wrote: >>>> On 15.09.2010 19:34, Jeremy Fitzhardinge wrote: >>>>>>>> current git stable 2.6.32.x (2968b25) crashes on boot with the >>>>>>>> attached debug output. The same config file works perfectly on >>>>>>>> 2.6.32.18 (e6b9b2c). >>>>>>> Thanks for the report. I've pushed an update to xen/stable-2.6.32.x >>>>>>> which should fix this. >>>>>> Sorry, still does not boot. I attached the serial console log and >>>>>> manually created a traceback from the stack hex dump. >>>>> Does adding "mem=1g" to the kernel command line help? >>>> No (log attached). But the stacktrace changed back to the first >>>> "version": >>>> >>>> get_phys_to_machine >>>> pte_pfn_to_mfn >>>> xen_make_pgd >>>> __raw_callee_save_xen_make_pgd >>>> vmemmap_pgd_populate >>>> vmemmap_populate >>>> sparse_mem_map_populate >>>> sparse_init >>> What's your kernel config? >> Still the one from the original post >> (http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html). >> > > Are you still checking this? Any news? > Haven't forgotten about it, but I was waiting for some inspiration to strike. Could you try some earlier versions and try to isolate when the problem appeared? Thanks, J