Re: [PATCH 5.4 00/57] 5.4.70-rc1 review
From: Naresh Kamboju
Date: Tue Oct 06 2020 - 04:25:44 EST
On Tue, 6 Oct 2020 at 11:24, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote:
>
> On Mon, 5 Oct 2020 at 20:59, Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > This is the start of the stable review cycle for the 5.4.70 release.
> > There are 57 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed, 07 Oct 2020 14:20:55 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.70-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
>
> Results from Linaro’s test farm.
> No regressions on arm64, arm, x86_64, and i386.
>
> Tested-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx>
NOTE:
While running LTP containers test suite,
I noticed this kernel panic on arm64 Juno-r2 devices.
Not easily reproducible and not seen on any other arm64 devices.
steps to reproduce:
---------------------------
# boot stable rc 5.4.70 kernel on juno-r2 machine
# cd /opt/ltp
# ./runltp -f containers
Crash log,
---------------
pidns13 0 TINFO : cinit2: writing some data in pipe
pidns13 0 TINFO : cinit1: setup handler for async I/O on pipe
pidns13 1 TPASS : cinit1: si_fd is 6, si_code is 1
[ 122.275627] Internal error: synchronous external abort: 96000210
[#1] PREEMPT SMP
[ 122.283139] Modules linked in: tda998x drm_kms_helper drm crct10dif_ce fuse
[ 122.290130] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.70-rc1 #1
[ 122.296406] Hardware name: ARM Juno development board (r2) (DT)
[ 122.302337] pstate: 80000085 (Nzcv daIf -PAN -UAO)
[ 122.307144] pc : sil24_interrupt+0x28/0x5f0
[ 122.311337] lr : __handle_irq_event_percpu+0x78/0x2c0
[ 122.316395] sp : ffff800010003db0
[ 122.319712] x29: ffff800010003db0 x28: ffff800011f73d80
[ 122.325034] x27: ffff800011962018 x26: ffff000954a82000
[ 122.330357] x25: ffff800011962018 x24: ffff800011f6a158
[ 122.335679] x23: ffff800010003ef4 x22: ffff000975740000
[ 122.341001] x21: 0000000000000033 x20: ffff80001233d044
[ 122.346324] x19: ffff000975742500 x18: 0000000000000000
[ 122.351646] x17: 0000000000000000 x16: 0000000000000000
[ 122.356967] x15: 0000000000000000 x14: 003d090000000000
[ 122.362290] x13: 00003d0900000000 x12: 0000000000000000
[ 122.367612] x11: 00003d0900000000 x10: 0000000000000040
[ 122.372934] x9 : ffff800011f89b68 x8 : ffff800011f89b60
[ 122.378256] x7 : ffff000975800408 x6 : 0000000000000000
[ 122.383578] x5 : ffff000975800248 x4 : ffff80096d5ba000
[ 122.388900] x3 : ffff800010003f30 x2 : ffff80001093a078
[ 122.394222] x1 : ffff000975740000 x0 : ffff00097574df80
[ 122.399545] Call trace:
[ 122.401995] sil24_interrupt+0x28/0x5f0
[ 122.405838] __handle_irq_event_percpu+0x78/0x2c0
[ 122.410550] handle_irq_event_percpu+0x3c/0x98
[ 122.415002] handle_irq_event+0x4c/0xe8
[ 122.418844] handle_fasteoi_irq+0xbc/0x168
[ 122.422947] generic_handle_irq+0x34/0x50
[ 122.426963] __handle_domain_irq+0x6c/0xc0
[ 122.431066] gic_handle_irq+0x58/0xb0
[ 122.434733] el1_irq+0xbc/0x180
[ 122.437880] cpuidle_enter_state+0xb8/0x528
[ 122.442070] cpuidle_enter+0x3c/0x50
[ 122.445652] call_cpuidle+0x40/0x78
[ 122.449146] do_idle+0x1f0/0x2a0
[ 122.452379] cpu_startup_entry+0x2c/0x88
[ 122.456311] rest_init+0xdc/0xe8
[ 122.459545] arch_call_rest_init+0x14/0x1c
[ 122.463647] start_kernel+0x484/0x4b8
[ 122.467321] Code: d503201f f9400ac0 f9400014 91011294 (b9400294)
[ 122.473437] ---[ end trace 68b3da9e48a77548 ]---
[ 122.478062] Kernel panic - not syncing: Fatal exception in interrupt
[ 122.484429] SMP: stopping secondary CPUs
[ 122.488569] Kernel Offset: disabled
[ 122.492062] CPU features: 0x0002,24006004
[ 122.496074] Memory Limit: none
[ 122.499141] ---[ end Kernel panic - not syncing: Fatal exception in
interrupt ]---
Reported-by: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
Full test log,
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.4.y/build/v5.4.69-58-g7b199c4db17f/testrun/3273934/suite/linux-log-parser/test/check-kernel-panic-1818664/log
- Naresh