From: Graeme Russ <graeme.russ@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 embedded - Problem getting past 'move compressed kernel before decompression'
Date: Mon, 01 Mar 2010 22:56:12 +1100 [thread overview]
Message-ID: <4B8BAB5C.5030707@gmail.com> (raw)
In-Reply-To: <4B88A865.2080009@gmail.com>
Graeme Russ wrote:
> Graeme Russ wrote:
>> On Sun, Feb 21, 2010 at 4:53 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>>> On 02/20/2010 09:45 PM, H. Peter Anvin wrote:
>>>
> I borrowed __show_regs() from process_32.c and implemented crash dump and
> break dump handlers in u-boot. So now I can int3 and dump all registers.
>
>
> I don't understand what is going on with SS and ESP, but everything else is
> looking good up until:
> jmp *%eax
>
> At which point, eax appears to hold a reasonably value. But:
>
> boot > md 5379c4
> 005379c4: c11c0e7f b0c2ea61 2d43c068 f02e6fa0 ....a...h.C-.o..
> I would have expected a 0xcc at 0x005379c4.
>
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?
Regards,
Graeme
next prev parent reply other threads:[~2010-03-01 11:56 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 [this message]
2010-03-01 16:46 ` H. Peter Anvin
2010-03-01 19:41 ` Graeme Russ
2010-03-01 19:43 ` H. Peter Anvin
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=4B8BAB5C.5030707@gmail.com \
--to=graeme.russ@gmail.com \
--cc=hpa@zytor.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