From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: Xeno-unstable crashing at boot Date: Tue, 17 May 2005 11:29:21 +0100 Message-ID: <3d8eece205051703296725f8f5@mail.gmail.com> References: <4289B722.6090205@hp.com> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4289B722.6090205@hp.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mike Wray Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 5/17/05, Mike Wray wrote: > > "make clean; make debug=3Dy dist" should do it. > > > > > >>Can you suggest what a good place 'earlier in the failure > >>path' might be? > > > > I expect you'll get an error message from Xen before the BUG in domain > > crash. See where the error message comes from, and then add the > > show_guest_stack to the appropriate path. >=20 > A debug build gave the following crash. > It's different, a page fault, but there's no previous error message > that lets me see where to put the show_guest_stack. 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=3Dserial" 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! christian