Re: Kernel v5.2+ on HiKey960?

From: Will Deacon <will@kernel.org>
To: Jerome Forissier <jerome@forissier.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	maz@kernel.org
Subject: Re: Kernel v5.2+ on HiKey960?
Date: Wed, 4 Dec 2019 17:57:27 +0000	[thread overview]
Message-ID: <20191204175726.GA28736@willie-the-truck> (raw)
In-Reply-To: <226a53f8-9404-1aa0-ed44-22e2157e4521@forissier.org>

On Wed, Dec 04, 2019 at 03:58:57PM +0100, Jerome Forissier wrote:
> On 12/4/19 3:28 PM, Catalin Marinas wrote:
> > 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.
> > 
> 
> Fails indeed (panic): https://pastebin.com/F0jpktii

Interesting. I followed your instructions and my board boots fine even
after applying that patch, but then I see the following on shutdown:

[   83.022955] WARNING: CPU: 0 PID: 1995 at kernel/time/tick-broadcast.c:647 tick_handle_oneshot_broadcast+0x1c8/0x1e8
[   83.033392] Modules linked in:
[   83.036447] CPU: 0 PID: 1995 Comm: init Tainted: G S                5.1.0-253105-g2b41f6584d59 #3
[   83.045319] Hardware name: HiKey960 (DT)
[   83.049238] pstate: 00000085 (nzcv daIf -PAN -UAO)
[   83.054026] pc : tick_handle_oneshot_broadcast+0x1c8/0x1e8
[   83.059509] lr : tick_handle_oneshot_broadcast+0x15c/0x1e8
[   83.064990] sp : ffff000010003b40
[   83.068298] x29: ffff000010003b40 x28: ffff0000116de0e4 
[   83.073607] x27: ffff0000118e85c0 x26: ffff0000116d7a00 
[   83.078916] x25: 0000001342080d5f x24: ffff00001198e2f0 
[   83.084225] x23: ffff0000116ddf40 x22: ffff00001198e2c0 
[   83.089533] x21: 0000000000000000 x20: 7fffffffffffffff 
[   83.094842] x19: ffff00001198e280 x18: 0000000000000010 
[   83.100151] x17: 0000000000000000 x16: 0000000000000000 
[   83.105459] x15: 0000000000000000 x14: 0000000000000000 
[   83.110768] x13: ffff000010e544d0 x12: ffff000010e544c8 
[   83.116077] x11: 0720072007200720 x10: 0000000000000040 
[   83.121384] x9 : ffff000011705bd0 x8 : ffff000011705bc8 
[   83.126693] x7 : ffff8000bf0002a0 x6 : 0000000000000004 
[   83.132002] x5 : 0000000000000000 x4 : 0000000000000001 
[   83.137310] x3 : 0000000000000000 x2 : 0000000000000100 
[   83.142619] x1 : ffff0000116ddf40 x0 : 0000000000000000 
[   83.147929] Call trace:
[   83.150372]  tick_handle_oneshot_broadcast+0x1c8/0x1e8
[   83.155512]  sp804_timer_interrupt+0x3c/0x50
[   83.159782]  __handle_irq_event_percpu+0x78/0x2c8
[   83.164482]  handle_irq_event_percpu+0x40/0x98
[   83.168922]  handle_irq_event+0x50/0x80
[   83.172755]  handle_fasteoi_irq+0xc0/0x178
[   83.176847]  generic_handle_irq+0x34/0x50
[   83.180852]  __handle_domain_irq+0x6c/0xc0
[   83.184947]  gic_handle_irq+0x58/0xa8
[   83.188605]  el1_irq+0xb8/0x180
[   83.191740]  __do_softirq+0xa8/0x3a0
[   83.195314]  irq_exit+0xc0/0xd0
[   83.198450]  __handle_domain_irq+0x70/0xc0
[   83.202541]  gic_handle_irq+0x58/0xa8
[   83.206198]  el1_irq+0xb8/0x180
[   83.209339]  _raw_spin_unlock_irq+0x28/0x60
[   83.213520]  do_exit+0xf0/0xa28
[   83.216661]  __se_sys_reboot+0x16c/0x248
[   83.220581]  __arm64_sys_reboot+0x24/0x30
[   83.224590]  el0_svc_common.constprop.0+0x88/0xf8
[   83.229290]  el0_svc_handler+0x34/0x90
[   83.233035]  el0_svc+0x8/0xc
[   83.235909] ---[ end trace 70f495d614c1efd2 ]---

which is unexpected.

Will

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