From: Christian Limpach <christian.limpach@gmail.com>
To: Mike Wray <mike.wray@hp.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: Xeno-unstable crashing at boot
Date: Tue, 17 May 2005 11:29:21 +0100 [thread overview]
Message-ID: <3d8eece205051703296725f8f5@mail.gmail.com> (raw)
In-Reply-To: <4289B722.6090205@hp.com>
On 5/17/05, Mike Wray <mike.wray@hp.com> wrote:
> > "make clean; make debug=y 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.
>
> 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=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!
christian
next prev parent reply other threads:[~2005-05-17 10:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 19:55 Xeno-unstable crashing at boot Ian Pratt
2005-05-17 9:19 ` Mike Wray
2005-05-17 10:29 ` Christian Limpach [this message]
2005-05-17 11:52 ` Mike Wray
2005-05-17 13:26 ` Keir Fraser
2005-05-17 16:01 ` memory mapping Grzegorz Milos
2005-05-17 16:09 ` Grzegorz Milos
2005-05-17 18:23 ` Xeno-unstable crashing at boot Mike Wray
2005-05-17 19:49 ` Keir Fraser
2005-05-19 10:42 ` Mike Wray
2005-05-19 14:18 ` Keir Fraser
2005-05-19 16:22 ` Mike Wray
-- strict thread matches above, loose matches on Subject: below --
2005-05-20 16:58 Nakajima, Jun
2005-05-20 21:42 ` Christian Limpach
2005-05-19 16:43 Ian Pratt
2005-05-20 16:24 ` Mike Wray
2005-05-20 17:16 ` Anthony Liguori
2005-05-16 13:27 Ian Pratt
2005-05-16 13:29 ` Steven Hand
2005-05-16 13:33 ` Mark Williamson
2005-05-16 18:18 ` Mike Wray
2005-05-13 19:42 Ian Pratt
2005-05-13 20:20 ` Kip Macy
2005-05-16 12:57 ` Mike Wray
2005-05-13 18:43 Ian Pratt
2005-05-13 18:55 ` Mike Wray
2005-05-13 18:26 Mike Wray
2005-05-13 18:46 ` David F Barrera
2005-05-13 18:48 ` Anthony Liguori
2005-05-13 18:56 ` Mike Wray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d8eece205051703296725f8f5@mail.gmail.com \
--to=christian.limpach@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mike.wray@hp.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.