From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: pending 4.14-rc boot failures on arm64
Date: Fri, 22 Dec 2017 16:03:12 +0100 [thread overview]
Message-ID: <20171222150312.GB28720@kroah.com> (raw)
In-Reply-To: <CA+G9fYvadCtQnVbEHLWg2uWBn1PoJm30=G-gZHc016pjs44HrQ@mail.gmail.com>
On Fri, Dec 22, 2017 at 06:09:00PM +0530, Naresh Kamboju wrote:
> On 22 December 2017 at 15:50, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > On 22 December 2017 at 14:36, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> >> On Fri, Dec 22, 2017 at 02:29:55PM +0530, Naresh Kamboju wrote:
> >>> On 22 December 2017 at 12:41, Greg Kroah-Hartman
> >>> <gregkh@linuxfoundation.org> wrote:
> >>> > On Thu, Dec 21, 2017 at 04:35:30PM -0600, Dan Rue wrote:
> >>> >> Hi Greg,
> >>> >>
> >>> >> It looks like the pending v4.14.8-159-gc2a94d1a609 fails to boot on all
> >>> >> arm64 boards. hikey and juno are failing for us, and I see similar arm64
> >>> >> boot failures reported by kernelci.
> >>> >>
> >>> >> Still investigating root cause.
> >>> >
> >>> > Any help in bisecting to find the problem here would be great...
> >>>
> >>> Booting now on arm64 Hikey board. After reverting 83e3c48729d.
> >>>
> >>> git revert 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
>
> Reverting above commit 83e3c48 (mm/sparsemem: Allocate mem_section at)
> might not be the right way to fix this problem.
No it isn't :)
> Instead cherry pick this commit 629a359bd to fix ARM64 boot crash problem.
> (mm/sparsemem: Fix ARM64 boot crash when CONFIG_SPARSEMEM_EXTREME=y)
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> branch: linux-4.14.y
>
> git cherry-pick 629a359bdb0e0652a8227b4ff3125431995fec6e
I've taken this patch and added it to the queue, thanks.
greg k-h
prev parent reply other threads:[~2017-12-22 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:35 pending 4.14-rc boot failures on arm64 Dan Rue
2017-12-22 7:11 ` Greg Kroah-Hartman
2017-12-22 8:59 ` Naresh Kamboju
2017-12-22 9:06 ` Greg Kroah-Hartman
2017-12-22 10:20 ` Naresh Kamboju
2017-12-22 12:39 ` Naresh Kamboju
2017-12-22 15:03 ` Greg Kroah-Hartman [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=20171222150312.GB28720@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@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).