From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: 3.10-rc1 does not boot anymore on OpenBlocks AX3
Date: Sat, 18 May 2013 19:26:33 +0200 [thread overview]
Message-ID: <20130518172633.GD1936@1wt.eu> (raw)
In-Reply-To: <20130518172212.GA21837@localhost>
Hi Gregory & Ezequeil,
On Sat, May 18, 2013 at 02:22:13PM -0300, Ezequiel Garcia wrote:
> Hi Willy,
>
> On Sat, May 18, 2013 at 07:01:58PM +0200, Willy Tarreau wrote:
> >
> > Uncompressing Linux... done, booting the kernel.
> > Booting Linux on physical CPU 0x0
> > Linux version 3.10.0-rc-mvebu (willy at pcw) (gcc version 4.7.3 20130205 (prerelease) (crosstool-NG 1.18.0) ) #6 SMP Sat May 18 17:40:55 CEST 2013
> > CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c53c7d
> > CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
> > Machine: Marvell Armada 370/XP (Device Tree), model: PlatHome OpenBlocks AX3-4 board
> > bootconsole [earlycon0] enabled
> > INITRD: 0x07000040+0x00a5c000 is not a memory region - disabling initrd
> > Memory policy: ECC disabled, Data cache writealloc
> > Kernel panic - not syncing: ERROR: Failed to allocate 0x1000 bytes below 0x0.
>
> This is a known issue.
> Please try again with this patch:
>
> [PATCH] ARM: zImage: Convert 32bits memory size and address from ATAG to
> 64bits DTB
>
> which has been posted on LAKML on May 14th.
Thanks to you both for your simultaneous response :-)
I did notice this patch a few days ago but did not understant it could be
related to this issue. Back to patching and testing then :-)
Thanks!
Willy
next prev parent reply other threads:[~2013-05-18 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 17:01 ARM: 3.10-rc1 does not boot anymore on OpenBlocks AX3 Willy Tarreau
2013-05-18 17:21 ` Gregory CLEMENT
2013-05-18 17:22 ` Ezequiel Garcia
2013-05-18 17:26 ` Willy Tarreau [this message]
2013-05-18 17:28 ` Ezequiel Garcia
2013-05-18 17:48 ` Willy Tarreau
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=20130518172633.GD1936@1wt.eu \
--to=w@1wt.eu \
--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).