From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: HANG at bootup on 3.10 kernel at memset in early_alloc_aligned with CMA
Date: Mon, 12 Oct 2015 18:08:19 +0100 [thread overview]
Message-ID: <20151012170818.GA3659@leverpostej> (raw)
In-Reply-To: <1773685879.894081444667895180.JavaMail.weblogic@epmlwas09a>
On Mon, Oct 12, 2015 at 04:38:15PM +0000, VIKAS SAJJAN C wrote:
> Hi,
Hi,
> we are recently migrating to 3.10 kernel on a 32bit SoC, I see that
> while boot up, the kernel HANGS in function early_alloc_aligned() at
> memset(ptr, 0, sz);
>
> we are reserving memory using CMA
>
>
> we have 4 banks :
>
> bank 1 : 0x200000000, size 0x10000000
>
> bank 2 : 0x300000000, size 0x10000000
>
> bank 3 : 0x400000000, size 0x10000000
>
> bank 4 : 0x500000000, size 0x0f500000
As this isn't 2M-aligned, this certainly could be the same issue.
> arm_lowmem_limit is set to 0x4f000000 and mapping is created for
> section: 20000000 ~ 4f000000
>
> I came across your patch "ARM: 8356/1: mm: handle non-pmd-aligned end
> of RAM"
>
> Was wondering whether patch is back ported to 3.10 stable branch, if
> so can you point me to the patch?
To the best of my knowledge, it was not. If you haven't seen it in the
v3.10.x commit logs, it presumably wasn't.
> if not, can you let us know the changes needed for 3.10 kernel.
I do not know. Have you tried backporting the patch?
I believe that you will also need to backport commit 3de1f52a3ae82326
("ARM: 8394/1: update memblock limit after mapping lowmem"). See [1,2].
Thanks,
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/353496.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/353602.html
prev parent reply other threads:[~2015-10-12 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 16:38 HANG at bootup on 3.10 kernel at memset in early_alloc_aligned with CMA VIKAS SAJJAN C
2015-10-12 17:08 ` Mark Rutland [this message]
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=20151012170818.GA3659@leverpostej \
--to=mark.rutland@arm.com \
--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 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.