Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Forissier <jerome@forissier.org>
To: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Kernel v5.2+ on HiKey960?
Date: Tue, 3 Dec 2019 16:43:22 +0100	[thread overview]
Message-ID: <f58c2c0e-ec82-6675-84e6-ad63fd93c8ff@forissier.org> (raw)

Hi,

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:

1. "arm64: vdso: Substitute gettimeofday() with C implementation"
2. "arm64: vdso: Explicitly add build-id option"
3. "arm64: arch_timer: Ensure counter register reads occur with seqlock
    held"
4. "arm64: vdso: Remove stale files from old assembly implementation"

So the main thing appears to be the VDSO stuff, but if I do not also
revert the arch_timer commit I get a kernel panic:

[    4.657118] Run /init as init process
[    4.662380] Kernel panic - not syncing: Attempted to kill init!
               exitcode=0x00000004
[    4.670035] CPU: 7 PID: 1 Comm: init Not tainted 5.4.0-00003-
               g223b12c033fb #258
[    4.677338] Hardware name: HiKey960 (DT)
[    4.681253] Call trace:
[    4.683700]  dump_backtrace+0x0/0x148
[    4.687355]  show_stack+0x24/0x30
[    4.690664]  dump_stack+0xbc/0x100
[    4.694058]  panic+0x168/0x368
[    4.697105]  do_exit+0xa10/0xa28
[    4.700323]  do_group_exit+0x48/0xa8
[    4.703892]  get_signal+0xec/0x848
[    4.707287]  do_notify_resume+0x21c/0x480
[    4.711290]  work_pending+0x8/0x10
[    4.714689] SMP: stopping secondary CPUs
[    4.718607] Kernel Offset: disabled
[    4.722089] CPU features: 0x0002,21082004
[    4.726090] Memory Limit: none
[    4.729145] ---[ end Kernel panic - not syncing: Attempted to kill
               init! exitcode=0x00000004 ]---

Any idea what could be wrong with my setup?

Thanks,
-- 
Jerome

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-12-03 15:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 15:43 Jerome Forissier [this message]
2019-12-03 17:47 ` Kernel v5.2+ on HiKey960? 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
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=f58c2c0e-ec82-6675-84e6-ad63fd93c8ff@forissier.org \
    --to=jerome@forissier.org \
    --cc=linux-arm-kernel@lists.infradead.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