From: Catalin Marinas <catalin.marinas@arm.com>
To: Jerome Forissier <jerome@forissier.org>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>,
Will Deacon <will@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kernel v5.2+ on HiKey960?
Date: Wed, 4 Dec 2019 14:28:24 +0000 [thread overview]
Message-ID: <20191204142824.GB26730@arrakis.emea.arm.com> (raw)
In-Reply-To: <1c5e497f-4be0-e1f3-4d6d-fed9470d0406@forissier.org>
On Wed, Dec 04, 2019 at 02:15:48PM +0100, Jerome Forissier wrote:
> On 12/4/19 11:18 AM, Catalin Marinas wrote:
> > On Tue, Dec 03, 2019 at 04:43:22PM +0100, Jerome Forissier wrote:
> >> Has anyone successfully run kernel v5.2 or later on a HiKey960 board?
> >>
> >> For some reason, anything past v5.1 doesn't work for me and I could not
> >> figure out why. The symptom is it never gets to the login prompt. The
> >> root FS is a Buildroot-generated one, and prior to reaching the kernel
> >> the board runs TF-A, OP-TEE, UEFI (edk2) and Grub.
> >>
> >> I tried replacing /init with a shell, in which case I can type a command
> >> but whatever it is (even a simple "ls"), the command hangs on exit and I
> >> never get back to the prompt.
> >>
> >> Then I started bisecting, that was quite painful but I found several
> >> problematic commits. I ended up reverting the following (in this order)
> >> to be able to boot v5.4:
[...]
> 75a19a0202db is the first bad commit. Its parent: commit 2f1d4e24d91b
> ("firmware: arm_sdei: Prohibit probing in '_sdei_handler'") boots fine
> [2]. Since reverting 75a19a0202db in v5.2 does not work, I suspect we're
> dealing with multiple problems. As I said, the set of reverts above is
> the best I could figure out, and believe me I spent several days trying
> to troubleshoot this :-/ (that being said, I know nothing about the VDSO
> or the arch timer so I could not try anything meaningful other than
> reverting some commits).
Thanks. There could as well be multiple issues. Since commit
75a19a0202db is cc stable, could you please apply it on top of 5.1 and
see if it fails? I don't have a HiKey960 at hand to try this.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-04 14:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 15:43 Kernel v5.2+ on HiKey960? Jerome Forissier
2019-12-03 17:47 ` Marc Zyngier
2019-12-04 9:01 ` Jerome Forissier
2019-12-04 10:18 ` Marc Zyngier
2019-12-04 12:22 ` Jerome Forissier
2019-12-04 12:49 ` Vincenzo Frascino
2019-12-04 13:28 ` Jerome Forissier
2019-12-04 10:18 ` Catalin Marinas
2019-12-04 12:55 ` Vincenzo Frascino
2019-12-04 14:03 ` Jerome Forissier
2019-12-05 12:04 ` Vincenzo Frascino
2019-12-05 14:48 ` Jerome Forissier
2019-12-05 14:59 ` Vincenzo Frascino
2019-12-04 13:15 ` Jerome Forissier
2019-12-04 14:28 ` Catalin Marinas [this message]
2019-12-04 14:58 ` Jerome Forissier
2019-12-04 17:57 ` Will Deacon
2019-12-05 7:26 ` Jerome Forissier
2019-12-05 8:57 ` Will Deacon
2019-12-05 14:54 ` Jerome Forissier
2019-12-06 16:09 ` Will Deacon
2019-12-10 16:20 ` Jerome Forissier
2019-12-10 16:26 ` Vincenzo Frascino
2019-12-11 8:57 ` Jerome Forissier
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=20191204142824.GB26730@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=jerome@forissier.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vincenzo.frascino@arm.com \
--cc=will@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 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).