From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>, Linux MM <linux-mm@kvack.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Pavel Emelyanov <xemul@openvz.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: Possible regression in next-20150120 due to "mm: account pmd page tables to the process"
Date: Thu, 22 Jan 2015 12:33:06 +0900 [thread overview]
Message-ID: <20150122033306.GN31170@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWyXaxobndjYDwYwqE=XJCBH_7C9TFBZYr7UpYk-rUa4A@mail.gmail.com>
On Wed, Jan 21, 2015 at 10:37:20AM +0100, Geert Uytterhoeven wrote:
> Hi Kirill, Simon,
>
> On Wed, Jan 21, 2015 at 10:29 AM, Kirill A. Shutemov
> <kirill.shutemov@linux.intel.com> wrote:
> > Simon Horman wrote:
> >> Hi,
> >>
> >> I have observed what appears to be a regression caused
> >> by b316feb3c37ff19cd ("mm: account pmd page tables to the process").
> >>
> >> The problem that I am seeing is that when booting the kzm9g board, which is
> >> based on the Renesas r8a73a4 ARM SoC, using its defconfig the following the
>
> Renesas sh73a0 ARM SoC, FWIW...
>
> >> tail boot log below is output repeatedly and the boot does not appear to
> >> proceed any further.
> >>
> >> I have observed this problem using next-20150120 and observed
> >> that it does not occur when the patch mentioned above is reverted.
> >>
> >> I have also observed what appears to be the same problem when
> >> booting the following boards using their defconfigs. And perhaps
> >> more to the point the problem appears to affect booting all
> >> boards based on Renesas ARM SoCs for which there is working support
> >> to boot them by initialising them using C (as opposed to device tree).
> >>
> >> * armadillo800eva, based on the r8a7740 SoC
> >> * mackerel, based on the sh7372
> >
> > This should be fixed by this:
> >
> > http://marc.info/?l=linux-next&m=142176280218627&w=2
> >
> > Please, test.
>
> Thanks!
>
> Confirmed the issue, and confirmed the fix (on sh73a0/kzm9g-legacy).
>
> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks, I have also tested the armadillo800eva and mackerel.
Tested-by: Simon Horman <horms+renesas@verge.net.au>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-01-22 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 2:30 Possible regression in next-20150120 due to "mm: account pmd page tables to the process" Simon Horman
2015-01-21 9:29 ` Kirill A. Shutemov
2015-01-21 9:37 ` Geert Uytterhoeven
2015-01-22 3:33 ` Simon Horman [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=20150122033306.GN31170@verge.net.au \
--to=horms@verge.net.au \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gorcunov@openvz.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=xemul@openvz.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).