From: Tomasz Figa <t.figa@samsung.com>
To: devicetree-discuss@lists.ozlabs.org
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, nico@linaro.org,
bones@secretlab.ca, linux@arm.linux.org.uk,
thomas.abraham@linaro.org, kgene.kim@samsung.com
Subject: Early kernel hang with big DTB appended
Date: Thu, 03 Jan 2013 16:55 +0100 [thread overview]
Message-ID: <7811936.npteFbuYu2@amdc1227> (raw)
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. With fullest possible low level UART
debugging (and printk patched to use printascii) I'm receiving following
output:
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0xa00
Linux version 3.8.0-rc1-00073-gdf6efca-dirty (t.figa@amdc1227) (gcc
version 4.5.2 (Gentoo 4.5.2 p1.2, pie-0.4.5) ) #2 SMP PREEMPT Thu Jan 3
15:37:35 CET 2013
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
I tested on two Exynos-based boards (exynos4210-trats and one internal
exynos4412-based board) and same happens on both.
Do you have any ideas?
Best regards,
--
Tomasz Figa
Samsung Poland R&D Center
SW Solution Development, Linux Platform
next reply other threads:[~2013-01-03 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 15:55 Tomasz Figa [this message]
2013-01-03 18:40 ` Early kernel hang with big DTB appended Bryan Evenson
2013-01-04 10:26 ` Tomasz Figa
2013-01-04 2:48 ` Nicolas Pitre
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-11 16:45 ` Early kernel hang with big DTB appended Sascha Hauer
2013-01-14 22:13 ` Nicolas Pitre
2013-01-15 10:53 ` Sascha Hauer
2013-01-15 11:26 ` Tomasz Figa
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=7811936.npteFbuYu2@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=nico@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 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).