From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wray Subject: Re: Xeno-unstable crashing at boot Date: Tue, 17 May 2005 19:23:00 +0100 Message-ID: <428A3684.9050508@hp.com> References: <4289B722.6090205@hp.com> <3d8eece205051703296725f8f5@mail.gmail.com> <4289DB07.9010204@hp.com> <4d971950d2aa365b19698ccae800a504@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4d971950d2aa365b19698ccae800a504@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Ian Pratt , xen-devel@lists.xensource.com, Christian.Limpach@cl.cam.ac.uk List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > On 17 May 2005, at 12:52, Mike Wray wrote: > >>> The guest stack is now always printed when dom0 fails, which is why >>> you get a more relevant error message. >>> Could you please add "earlyprintk=serial" to the linux command line >>> options (CONFIG_EARLY_PRINTK should be enabled in your kernel config >>> file by default -- if not, please enable it) and add a call do >>> dump_stack() at the beginning of acpi_table_compute_checksum in >>> linux-2.6.11-xen-sparse/drivers/acpi/tables.c. Thanks! >> >> >> OK, I did that and planted a few dump_stack() calls in the acpi code: > > > I've just checked in a fix -- the Xen-specific acpi_map_table() function > was both unnecessary and broken. Hopefully latest unstable will boot on > your test machine. > Just updated and rebuilt - still crashing. Mike