From: mark.rutland@arm•com (Mark Rutland)
To: linux-arm-kernel@lists•infradead.org
Subject: Oops at boot after commit 965278dcb8ab... when using split memory region
Date: Wed, 1 Jul 2015 19:06:19 +0100 [thread overview]
Message-ID: <20150701180618.GI2310@leverpostej> (raw)
In-Reply-To: <20150701154007.GH2310@leverpostej>
On Wed, Jul 01, 2015 at 04:40:07PM +0100, Mark Rutland wrote:
> On Wed, Jul 01, 2015 at 03:53:54PM +0100, Russell King - ARM Linux wrote:
> > On Wed, Jul 01, 2015 at 03:46:12PM +0100, Mark Rutland wrote:
> > > On Wed, Jul 01, 2015 at 03:15:33PM +0100, jean-philippe francois wrote:
> > > > Hi,
> > >
> > > Hi,
> > >
> > > > commit 965278dcb8ab0b1f666cc47937933c4be4aea48d, (ARM: 8356/1: mm:
> > > > handle non-pmd-aligned end of RAM) causes my dm3730 based board to
> > > > oops at boot when using a split memory description.
> > > > The kernel command line parameter is :
> > > > mem=55M at 0x80000000 mem=128M at 0x88000000
> > > >
> > > > If the same board is booted without the mem argument, it boots to userspace.
> > >
> > > Thanks for the report.
> > >
> > > Javier reported a similar issue [1], which was somehow fixed by Laura's
> > > patch to update the memblock limit [2,3].
> > >
> > > I don't yet understand why, but if that works for you it would be an
> > > interesting data point.
> > >
> > > > Below is the bootlog.
> > >
> > > Interesting. That blows up a lot later than I'd expect. I'll see if I
> > > can reproduce the issue locally.
> >
> > Yes, I think we need to understand what's going on here, and what's
> > causing these failures, rather than blindly applying a patch which
> > seems to solve the problem.
>
> Certainly. I did not mean to imply otherwise.
>
> Using a similar command line I can reproduce the issue on TC2, getting a
> hang when freeing unused kernel memory. I'm digging into that now.
If I pass mem=56316K at 0${MY_MEM_BASE} (i.e. 55M - 4K), I get hangs with
and without commit 965278dcb8ab. It looks like we have a latent bug when
a bank is insufficiently aligned, and my patch increased that necessary
alignment from 1M to 2M.
I don't yet have a full explanation, and I'm still investigating, but as
far as I can tell the logic in sanity_check_meminfo is sound.
Thanks,
Mark.
next prev parent reply other threads:[~2015-07-01 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 14:15 Oops at boot after commit 965278dcb8ab... when using split memory region jean-philippe francois
2015-07-01 14:46 ` Mark Rutland
2015-07-01 14:53 ` Russell King - ARM Linux
2015-07-01 15:40 ` Mark Rutland
2015-07-01 18:06 ` Mark Rutland [this message]
2015-07-01 18:57 ` Russell King - ARM Linux
2015-07-02 0:41 ` Laura Abbott
2015-07-03 17:23 ` Mark Rutland
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=20150701180618.GI2310@leverpostej \
--to=mark.rutland@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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