From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: initrd problem
Date: Wed, 30 Jan 2019 12:20:38 +0300 [thread overview]
Message-ID: <1548840038.556794175@f490.i.mail.ru> (raw)
In-Reply-To: <20190130091441.b6tnhtk5ppob7qju@pengutronix.de>
>> >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.
>> Memory should be enough (256 Mb). I think the problem is that the memory is
>> divided into two banks of 128 Mb each.
>>
>> Just look for a next line:
>> __request_region: 0x923a3000:0x95e02fff outside parent resource 0x98000000:0x9fffffff
>>
>> Maybe we need some kind of option to merge nearby banks?
>
>If I'm not mistaken the banks are not really nearby. You should have two
>banks, one from 0x90000000 to 0x97ffffff and one from 0xa0000000 to
>0xa7ffffff.
>I don't know where the resource 0x98000000:0x9fffffff comes from. Could
>you paste the output of the iomem command? Are you using the code from
>arch/arm/mach-imx/esdctl.c or are you bypassing it?
It is not an error. CCMX51 not using ESDCTL.
The first bank is minimal size 128M. The second is a chain to first, its size
depends on module variant.
barebox@Mega-Milas Informer i.MX51:/ iomem
0x00000000 - 0xffffffff (size 0x00000000) iomem
0x1ffe0000 - 0x1fffffff (size 0x00020000) 1ffe0000.iram@1ffe0000
0x40000000 - 0x5fffffff (size 0x20000000) 40000000.ipu@40000000
0x70004000 - 0x70007fff (size 0x00004000) 70004000.esdhc@70004000
0x70008000 - 0x7000bfff (size 0x00004000) 70008000.esdhc@70008000
0x7000c000 - 0x7000ffff (size 0x00004000) 7000c000.serial@7000c000
0x70010000 - 0x70013fff (size 0x00004000) 70010000.spi@70010000
0x73f80000 - 0x73f801ff (size 0x00000200) 73f80000.usb@73f80000
0x73f80200 - 0x73f803ff (size 0x00000200) 73f80200.usb@73f80200
0x73f80800 - 0x73f809ff (size 0x00000200) 73f80800.usbmisc@73f80800
0x73f84000 - 0x73f87fff (size 0x00004000) 73f84000.gpio@73f84000
0x73f88000 - 0x73f8bfff (size 0x00004000) 73f88000.gpio@73f88000
0x73f8c000 - 0x73f8ffff (size 0x00004000) 73f8c000.gpio@73f8c000
0x73f90000 - 0x73f93fff (size 0x00004000) 73f90000.gpio@73f90000
0x73f98000 - 0x73f9bfff (size 0x00004000) 73f98000.wdog@73f98000
0x73fa0000 - 0x73fa3fff (size 0x00004000) 73fa0000.timer@73fa0000
0x73fa8000 - 0x73fabfff (size 0x00004000) 73fa8000.iomuxc@73fa8000
0x73fb4000 - 0x73fb7fff (size 0x00004000) 73fb4000.pwm@73fb4000
0x73fb8000 - 0x73fbbfff (size 0x00004000) 73fb8000.pwm@73fb8000
0x73fbc000 - 0x73fbffff (size 0x00004000) 73fbc000.serial@73fbc000
0x73fc0000 - 0x73fc3fff (size 0x00004000) 73fc0000.serial@73fc0000
0x73fd0000 - 0x73fd3fff (size 0x00004000) 73fd0000.src@73fd0000
0x73fd4000 - 0x73fd7fff (size 0x00004000) 73fd4000.ccm@73fd4000
0x83f98000 - 0x83f9bfff (size 0x00004000) 83f98000.iim@83f98000
0x83fac000 - 0x83faffff (size 0x00004000) 83fac000.spi@83fac000
0x83fc4000 - 0x83fc7fff (size 0x00004000) 83fc4000.i2c@83fc4000
0x83fd9000 - 0x83fd9fff (size 0x00001000) imx51-esdctl0
0x83fda000 - 0x83fdafff (size 0x00001000) 83fda000.weim@83fda000
0x83fdb000 - 0x83fdbfff (size 0x00001000) 83fdb000.nand@83fdb000
0x90000000 - 0x97ffffff (size 0x08000000) ram0
0x95df8d40 - 0x97df8d3f (size 0x02000000) malloc space
0x97df8d40 - 0x97dfffde (size 0x0000729f) board data
0x97e00000 - 0x97e6e537 (size 0x0006e538) barebox
0x97e6e538 - 0x97e86727 (size 0x000181f0) barebox data
0x97e86728 - 0x97e897ff (size 0x000030d8) bss
0x97fe4000 - 0x97fe7fff (size 0x00004000) ttb
0x97fe8000 - 0x97feffff (size 0x00008000) stack
0x98000000 - 0x9fffffff (size 0x08000000) ram1
0xcfff0000 - 0xcfffffff (size 0x00010000) 83fdb000.nand@83fdb000
---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-01-30 9:20 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
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 [this message]
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=1548840038.556794175@f490.i.mail.ru \
--to=shc_work@mail.ru \
--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