From: chris@basementcode.com (Christopher Harvey)
To: kernelnewbies@lists.kernelnewbies.org
Subject: checking atags for boot parameters
Date: Tue, 21 Jun 2011 13:24:10 -0500 [thread overview]
Message-ID: <1a6c14aa701560fd0dcda32478cebe5b@basementcode.com> (raw)
In-Reply-To: <BANLkTik6iAG6P2fmTjZDAengOXJGVYs9RA@mail.gmail.com>
On Wed, 22 Jun 2011 00:14:50 +0700, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> Hi Christ... :)
It's Chris.
>
> On Tue, Jun 21, 2011 at 21:20, Christopher Harvey
> <chris@basementcode.com> wrote:
>> ?I'm suspicious that the bootloader I'm using isn't passing atags to
>> the
>> ?kernel properly.
>
> which bootloader?
uboot
>
>> ?I'm getting a prefetch exception right after the "uncompressing
>> ?linux....done" message, does it make sense that this could happen
>> ?because mem=128M isn't getting passed properly?
>
> uhm, fairly unlikely for me.... must be something else... could you
> tell us which arch it is and which kernel version (along with patches
> from certain tree, if any) that yield that error message?
It's not an error message, but with difficulty I was able to trace some
of the code and it ends up in a prefetch exception handler. I am not
able to find out from where however, and the line stepping is a bit
sketchy. No major patches to the kernel, and it runs in QEMU without
error. Adding uboot to QEMU then booting the same kernel yields the
problems.
It would be nice to find out what physical address the kernel is
uncompressed to as well, I'm as of yet unable to properly trace after
decompression.
-C
next prev parent reply other threads:[~2011-06-21 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 14:20 checking atags for boot parameters Christopher Harvey
2011-06-21 17:14 ` Mulyadi Santosa
2011-06-21 18:24 ` Christopher Harvey [this message]
2011-06-30 23:53 ` Gavin Guo
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=1a6c14aa701560fd0dcda32478cebe5b@basementcode.com \
--to=chris@basementcode.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).