From: "H. Peter Anvin" <hpa@zytor.com>
To: Graeme Russ <graeme.russ@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 embedded - Problem getting past 'move compressed kernel before decompression'
Date: Mon, 01 Mar 2010 11:43:12 -0800 [thread overview]
Message-ID: <4B8C18D0.2050208@zytor.com> (raw)
In-Reply-To: <4B8C184E.2000400@gmail.com>
On 03/01/2010 11:41 AM, Graeme Russ wrote:
> H. Peter Anvin wrote:
>> On 03/01/2010 03:56 AM, Graeme Russ wrote:
>>> I have done a little more digging. By adding an ascii string before
>>> relocated: label, I am able to determine that the int3 after the relocated:
>>> label exists in bzImage at offset 0x1C3FD7
>>>
>>> EAX holds (for the jump) 0x5379d0 (different bzImage of course). The
>>> contents of memory at this address is in bzImage at offset 0x1C09D7 - A
>>> difference of 0x3600 (seems too even to be random)
>>>
>>> I'm obviously doing something hideously wrong, but what?
>>>
>>
>> 0x3600 sounds like the size of the real-mode code in bzImage.
>>
>
> But what could I be doing to cause the miscalculation? From what I
> understand, everything looks to be calculated at build time
>
If I were to guess, you loaded the entire bzImage into high memory,
rather than just the PM portion thereof.
-hpa
next prev parent reply other threads:[~2010-03-01 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 2:03 x86 embedded - Problem getting past 'move compressed kernel before decompression' Graeme Russ
2010-02-21 5:45 ` H. Peter Anvin
2010-02-21 5:53 ` H. Peter Anvin
2010-02-21 9:11 ` Yuhong Bao
2010-02-21 22:51 ` Graeme Russ
2010-02-27 5:06 ` Graeme Russ
2010-03-01 11:56 ` Graeme Russ
2010-03-01 16:46 ` H. Peter Anvin
2010-03-01 19:41 ` Graeme Russ
2010-03-01 19:43 ` H. Peter Anvin [this message]
2010-03-01 19:59 ` Graeme Russ
2010-03-05 13:02 ` Graeme Russ
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=4B8C18D0.2050208@zytor.com \
--to=hpa@zytor.com \
--cc=graeme.russ@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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