linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: orion5x: initrd fails to load due to reserved memory
Date: Sat, 25 Jun 2016 18:16:16 +0100	[thread overview]
Message-ID: <20160625171615.GC1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20160625162040.GA15367@jirafa.cyrius.com>

On Sat, Jun 25, 2016 at 09:20:40AM -0700, Martin Michlmayr wrote:
> I ported Debian to the HP Media Vault mv2120 (based on orion5x) many
> years ago.  Debian stable (jessie), based on 3.16 kernel, works fine.
> A user told me a few months ago that the version of Debian currently
> in development (based on 4.6) doesn't boot.
> 
> The boot loader loads the kernel to 0x400000 and the ramdisk 0x200000
> after that location, i.e. at 0x600000:

So you're giving the kernel zImage just 2MB here.  How large is the
4.6 zImage?  Does the zImage have a dtb appended?

> Booting the image (@ 0x400000) with RamDisk (@ 0x600000)...
> 
> Unfortunately, with 4.x, this leads to:
> 
> INITRD: 0x00600040+0x00727f12 overlaps in-use memory region - disabling initrd

Right, so the kernel worked out that something else overwrote the
initramfs.  If you boot with memblock=debug, and memblock should
dump out the memory and reserved regions.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2016-06-25 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-25 16:20 orion5x: initrd fails to load due to reserved memory Martin Michlmayr
2016-06-25 17:16 ` Russell King - ARM Linux [this message]
2016-06-25 19:46   ` Martin Michlmayr
2016-06-25 22:08     ` Russell King - ARM Linux

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=20160625171615.GC1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).