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: Wed, 24 Oct 2007 09:15:34 -0700 [thread overview]
Message-ID: <471F6FA6.4080105@hp.com> (raw)
In-Reply-To: <C344BAE7.F684%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 24/10/07 08:12, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:
>
>>> 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.
>> So if you remove that call, so Xen falls back to using the GRUB-supplied
>> memory map, then Xen boots okay? Is tghat tru on current tip of xen-unstable
>> too?
>
> Thinking some more my guess is that any BIOS call is causing you to crash,
> so removing just teh call to get_memory_map will be insufficient on tip --
> you'll have to remove calls to set video mode and get edd information too.
> Perhaps the IDT is either corrupted or not actually at address 0x0, like
> it's supposed to be? What happens if you remove the 'lidt' instruction from
> arch/x86/boot/trampoline.S?
Once I identified the problem revision, I went back to the tip to try to
debug it. (Sorry for any ambiguity.) Taking out get_memory_map is
sufficient; get_edd and video don't seem to cause any problems.
Removing the lidt changes nothing. Adding a "ret" after the .Lmem88 in
mem.S confirms that the problem is in the e820 call. I'm currently
trying to see if the descriptor table is getting corrupted during the
BIOS calls.
John
next prev parent reply other threads:[~2007-10-24 16:15 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
2007-10-24 7:12 ` Keir Fraser
2007-10-24 8:03 ` Keir Fraser
2007-10-24 16:15 ` John Byrne [this message]
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=471F6FA6.4080105@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.