From: Philippe Leduc <ledphilippe@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: bootm crash - bad uimage?
Date: Tue, 23 Feb 2016 13:00:22 +0100 [thread overview]
Message-ID: <CABQt-Um-ENNbt_MbbF4NP42jmufsmgxV6pVvEsTFjw0O=++=ow@mail.gmail.com> (raw)
In-Reply-To: <20160223080530.GZ3939@pengutronix.de>
This commit doesn't seem to fix the problem (in fact it was already
applied when I saw the crash).
Note: I am using mkimage to create bootable image of a real-time OS
(PikeOS). There is no initrd or dtc at this step for now: I guess it
is like loading an old Linux kernel without userspace.
I do not want to bother you with a specific use case if this is the
root of the problem.
Best regards,
Philippe LEDUC
ledphilippe@gmail.com
2016-02-23 9:05 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
> Hi Philippe,
>
> On Mon, Feb 22, 2016 at 04:31:18PM +0100, Philippe Leduc wrote:
>> Hello,
>>
>> Since the commit 0a37e22d638acf1b2c7c6e6ab83b6a3272b0a11c, I can't
>> boot my image anymore.
>> It seems that os_part is a null pointer and simple_strtoul crash on it
>> (in bootm_load_os). I workaround the problem by forcing the value to 0
>> if os_part if null, but I guess that it is a bad solution.
>> Is this a due to a bad usage of the mkimage utility?
>
> Probably not. Is this fixed by this commit?
>
> commit 1a180cd3b6e5c067c68f3e09f7e15e5b18af9761
> Author: Lucas Stach <l.stach@pengutronix.de>
> Date: Fri Feb 12 17:58:23 2016 +0100
>
> bootm: parse initrd and oftree into correct struct members
>
> The code parsing the oftree and initrd file names is clearly wrong,
> leading to bootm not loading oftree or initrd files any more.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-02-23 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:31 Philippe Leduc
2016-02-23 8:05 ` Sascha Hauer
2016-02-23 12:00 ` Philippe Leduc [this message]
2016-02-25 9:30 ` Holger Schurig
2016-02-25 9:50 ` Philippe Leduc
2016-02-26 9:22 ` Philippe Leduc
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='CABQt-Um-ENNbt_MbbF4NP42jmufsmgxV6pVvEsTFjw0O=++=ow@mail.gmail.com' \
--to=ledphilippe@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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