From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: initrd problem
Date: Wed, 30 Jan 2019 07:08:00 +0100 [thread overview]
Message-ID: <20190130060800.kjizme7u36nwvflz@pengutronix.de> (raw)
In-Reply-To: <1548322649.666663534@f388.i.mail.ru>
Hi Alexander,
Sorry for the delay. Has this been resolved in the meantime?
On Thu, Jan 24, 2019 at 12:37:29PM +0300, Alexander Shiyan wrote:
> I decided to change the size of the UBI volume for the root file system to 60 MB.
> Now I get a weird OOM error. Turning on debug information shows a conflict,
> but I do not quite understand where to look for the problem.
> Where is the starting point to try to solve this problem?
>
>
> malloc space: 0x95df8d40 -> 0x97df8d3f (size 32 MiB)
>
> Loading ARM Linux zImage '/dev/nand0.system.ubi.kernel'
> __request_region ok: 0x92000000:0x922a244f
The Kernel documentation recommends putting the Kernel 32MiB into SDRAM
to avoid relocation. This is what we see here.
> __request_region: 0x923a3000:0x95e02fff conflicts with 0x95df8d40:0x97df8d3f
Now we try allocate space for the initrd above it which is 60MiB. This
conflicts with the malloc space.
So yes, you're out of memory.
Sascha
--
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:[~2019-01-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 9:37 Alexander Shiyan
2019-01-30 6:08 ` Sascha Hauer [this message]
2019-01-30 8:03 ` Alexander Shiyan
2019-01-30 8:19 ` Alexander Shiyan
2019-01-30 9:14 ` Sascha Hauer
2019-01-30 9:20 ` Alexander Shiyan
2019-01-30 9:35 ` Sascha Hauer
2019-01-31 9:03 ` Alexander Shiyan
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=20190130060800.kjizme7u36nwvflz@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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