From: Tomasz Figa <t.figa@samsung.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, bones@secretlab.ca,
linux@arm.linux.org.uk, thomas.abraham@linaro.org,
kgene.kim@samsung.com
Subject: Re: Early kernel hang with big DTB appended
Date: Fri, 04 Jan 2013 11:18:56 +0100 [thread overview]
Message-ID: <35730055.SShm3zF9mO@amdc1227> (raw)
In-Reply-To: <alpine.LFD.2.02.1301032144490.1263@xanadu.home>
Hi Nicolas,
Thanks for your reply.
On Thursday 03 of January 2013 21:48:05 Nicolas Pitre wrote:
> On Thu, 3 Jan 2013, Tomasz Figa wrote:
> > Hi,
> >
> > I'm observing strange behavior when booting 3.8-rc1 and -rc2 with
> > appended DTB. The kernel hangs very early when the DTB is bigger than
> > some threshold somewhere around 24 KiB.
>
> What is the address where you load your zImage?
We are using uImages built with same parameters as those used in simple
'make uImage', just with a DTB appended to zImage before running mkimage
on it.
By default the load address is set to 0x40008000, where 0x40000000 is DRAM
base.
> What if you load it, say, at an offset of 16MB from the start of RAM?
> Not that this is a fix, but at least that would help isolate the issue.
Yes, it indeed helps. I tried with shifting the load address by 16 MiB to
0x41008000 (by adjusting mkimage parameters) and it now boots fine.
Best regards,
--
Tomasz Figa
Samsung Poland R&D Center
SW Solution Development, Linux Platform
WARNING: multiple messages have this Message-ID (diff)
From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: Early kernel hang with big DTB appended
Date: Fri, 04 Jan 2013 11:18:56 +0100 [thread overview]
Message-ID: <35730055.SShm3zF9mO@amdc1227> (raw)
In-Reply-To: <alpine.LFD.2.02.1301032144490.1263@xanadu.home>
Hi Nicolas,
Thanks for your reply.
On Thursday 03 of January 2013 21:48:05 Nicolas Pitre wrote:
> On Thu, 3 Jan 2013, Tomasz Figa wrote:
> > Hi,
> >
> > I'm observing strange behavior when booting 3.8-rc1 and -rc2 with
> > appended DTB. The kernel hangs very early when the DTB is bigger than
> > some threshold somewhere around 24 KiB.
>
> What is the address where you load your zImage?
We are using uImages built with same parameters as those used in simple
'make uImage', just with a DTB appended to zImage before running mkimage
on it.
By default the load address is set to 0x40008000, where 0x40000000 is DRAM
base.
> What if you load it, say, at an offset of 16MB from the start of RAM?
> Not that this is a fix, but at least that would help isolate the issue.
Yes, it indeed helps. I tried with shifting the load address by 16 MiB to
0x41008000 (by adjusting mkimage parameters) and it now boots fine.
Best regards,
--
Tomasz Figa
Samsung Poland R&D Center
SW Solution Development, Linux Platform
next prev parent reply other threads:[~2013-01-04 10:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 15:55 Early kernel hang with big DTB appended Tomasz Figa
2013-01-03 15:55 ` Tomasz Figa
2013-01-03 18:40 ` Bryan Evenson
2013-01-03 18:40 ` Bryan Evenson
2013-01-04 10:26 ` Tomasz Figa
2013-01-04 10:26 ` Tomasz Figa
2013-01-04 2:48 ` Nicolas Pitre
2013-01-04 2:48 ` Nicolas Pitre
2013-01-04 10:18 ` Tomasz Figa [this message]
2013-01-04 10:18 ` Tomasz Figa
2013-01-14 8:45 ` $(make uImage) is stupid [Was: Re: Early kernel hang with big DTB appended] Uwe Kleine-König
2013-01-14 8:45 ` Uwe Kleine-König
2013-01-11 16:45 ` Early kernel hang with big DTB appended Sascha Hauer
2013-01-11 16:45 ` Sascha Hauer
2013-01-14 22:13 ` Nicolas Pitre
2013-01-14 22:13 ` Nicolas Pitre
2013-01-15 10:53 ` Sascha Hauer
2013-01-15 10:53 ` Sascha Hauer
2013-01-15 11:26 ` Tomasz Figa
2013-01-15 11:26 ` Tomasz Figa
2013-01-15 18:12 ` Nicolas Pitre
2013-01-15 18:12 ` Nicolas Pitre
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=35730055.SShm3zF9mO@amdc1227 \
--to=t.figa@samsung.com \
--cc=bones@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=thomas.abraham@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.