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
Subject: Re: pending 4.14-rc boot failures on arm64
Date: Fri, 22 Dec 2017 10:06:09 +0100 [thread overview]
Message-ID: <20171222090609.GA22981@kroah.com> (raw)
In-Reply-To: <CA+G9fYvuhnzo-o+Py3Vm=-=CU2SY0gqWejsW=92e-mJhQZ_-Aw@mail.gmail.com>
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
Any hint as to what the name of that commit is? The tree is rebased a
lot, that commit is long gone :(
> Linux version 4.14.9-rc1-00160-gb610c43 (naresh@linaro) (gcc version
> 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 -
> Linaro GCC 4.9-
> 2014.09)) #1 SMP PREEMPT Fri Dec 22 14:21:46 IST 2017
>
> Ref:
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1527427.html#nav
> https://bugs.linaro.org/show_bug.cgi?id=3404
What does this mean?
confused,
greg k-h
next prev parent reply other threads:[~2017-12-22 9:06 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 [this message]
2017-12-22 10:20 ` Naresh Kamboju
2017-12-22 12:39 ` Naresh Kamboju
2017-12-22 15:03 ` Greg Kroah-Hartman
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=20171222090609.GA22981@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.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.