mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: ARM bootm regression
Date: Mon, 19 Oct 2020 11:05:38 +0200	[thread overview]
Message-ID: <20201019090538.GQ13710@pengutronix.de> (raw)
In-Reply-To: <1602838156.455713761@f185.i.mail.ru>

Hi Alexander,

On Fri, Oct 16, 2020 at 11:49:16AM +0300, Alexander Shiyan wrote:
> Hello.
> 
> Found a regression in arm/lib32/bootm.c after a patch
> "ARM: bootm: make sure we place the kernel in free memory".
> 
> The initial memory size for the board is set to 8 MB (before reading the real value from DT),
> so the stack, malloc_space, etc. are placed in the initial 8M space.
> Then get_kernel_addresses() gets the real SDRAM area (for my board it is 64M),
> but decreases this size by the first children size (malloc_space),
> so mem_end is incorrect in this case.
> 
> barebox 2020.05.0-00393-gf5e96a296-dirty #80 Thu Oct 15 13:08:54 MSK 2020
> Board: Mega-Milas Informer EP7312
> cfi_flash 90000000.nor@0,0.of: found cfi flash at 0x90000000, size 32 MiB
> i2c-gpio i2c0.of: using pins 16 (SDA) and 35 (SCL)
> Hit any to stop autoboot:    1
> Booting entry 'nor'
> Loading ARM Linux zImage '/dev/nor0.kernel'

The problem might be that you have the kernel in a raw flash partition.
I think we have problems where we somewhere use the partition size where
we should really use the zImage size. The zImage size must be taken from
the zImage header while we just make a stat() on the file which happens
to be the whole partition for you.

Could you try and bootm the same zImage from ramfs?

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
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

  reply	other threads:[~2020-10-19  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16  8:49 Alexander Shiyan
2020-10-19  9:05 ` Sascha Hauer [this message]
2020-10-19  9:38   ` Alexander Shiyan
2020-10-21 14:44 ` Sascha Hauer
2020-10-22  6:13   ` Alexander Shiyan
2020-10-22  7:26     ` Sascha Hauer

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=20201019090538.GQ13710@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