xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mike Wray <mike.wray@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com, Christian.Limpach@cl.cam.ac.uk
Subject: Re: Xeno-unstable crashing at boot
Date: Tue, 17 May 2005 19:23:00 +0100	[thread overview]
Message-ID: <428A3684.9050508@hp.com> (raw)
In-Reply-To: <4d971950d2aa365b19698ccae800a504@cl.cam.ac.uk>

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

  parent reply	other threads:[~2005-05-17 18:23 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
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         ` Mike Wray [this message]
2005-05-17 19:49           ` Xeno-unstable crashing at boot 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=428A3684.9050508@hp.com \
    --to=mike.wray@hp.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).