From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Kinzler Subject: Re: pvops0 kernel 2.6.32.21 does not boot Date: Fri, 01 Oct 2010 12:53:29 +0200 Message-ID: <4CA5BDA9.60603@hfp.de> 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> <4C9A3B76.9030705@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C9A3B76.9030705@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: jeremy.fitzhardinge@citrix.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 22.09.2010 19:23, 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": >> 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? Actually I found something very strange. Even the vanilla kernels from kernel.org stopped working as a domU with the transition of 2.6.32.21 to 2.6.32.22. No output, no log, no nothing, just eating CPU time. Are there any debug options how to debug domUs that don't output anything? I am actually starting to wonder if the problems are related to kernels at all. I tried Xen 3.4.4 with the same result. Perhaps the whole problem is a binutils/gcc problem. What is your version of binutils / gcc / glibc? Regards Andreas