All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Byrne <john.l.byrne@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xen-unstable on HP dc7800 simply reboots
Date: Tue, 23 Oct 2007 16:03:01 -0700	[thread overview]
Message-ID: <471E7DA5.1060603@hp.com> (raw)
In-Reply-To: <471E485A.2030707@hp.com>

John Byrne wrote:
> Keir Fraser wrote:
>> On 23/10/07 17:49, "John Byrne" <john.l.byrne@hp.com> wrote:
>>
>>> Does anyone know what is wrong or can tell me how to go about debugging
>>> this? The dmesg output from booting the Ubuntu 2.6.22-14-server kernel
>>> is attach in the hope that it will provide some useful information.
>>
>> I suggest binary-chopping to find the offending changeset. Some early
>> boot-time stuff went in over the past few days, so for example try 
>> reverting
>> to 16130 and see if that has the same problem. Go back another 30, or
>> forward 15, changesets depending on whether that works or not. I suspect
>> this issue is quite new, so it shouldn't take too long to narrow down.
> 
> Actually, it a few months old. xen-unstable 15236 is the last changeset 
> that Xen doesn't immediately reboot.
> 

Littering the early boot code with putc() and comparing the code's 
behavior on a machine that actually boots, I've found that the call to 
get_memory_map from trampoline.S is the root of all evil. If that is 
called, then the trampoline fails to make it back to protected mode from 
real mode. I am still working to identify the specific problem.

John

  reply	other threads:[~2007-10-23 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 16:49 xen-unstable on HP dc7800 simply reboots John Byrne
2007-10-23 18:07 ` Keir Fraser
2007-10-23 19:15   ` John Byrne
2007-10-23 23:03     ` John Byrne [this message]
2007-10-24  7:12       ` Keir Fraser
2007-10-24  8:03         ` Keir Fraser
2007-10-24 16:15           ` John Byrne
2007-10-25  2:13             ` [PATCH] " John Byrne
2007-10-25  7:49               ` Keir Fraser

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=471E7DA5.1060603@hp.com \
    --to=john.l.byrne@hp.com \
    --cc=Keir.Fraser@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 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.