Kernel panic in ls1028ardb

Eddy1 — Fri, 09 Jul 2021 07:44:13 GMT

Hi：

plug in SSD on J20, and then wake up and find that kernel panic.

log:

[root@LS1028ARDB ~] # echo 0 > /sys/class/rtc/rtc1/wakealarm && echo +5 >/sys/class/rtc/rtc1/wakealarm && echo mem > /sys/power/state
[ 30.326219] 001: PM: suspend entry (deep)
[ 30.557491] 001: Filesystems sync: 0.231 seconds
[ 30.565063] 001: Freezing user space processes ...
[ 30.566305] 000: (elapsed 0.001 seconds) done.
[ 30.566310] 000: OOM killer disabled.
[ 30.566313] 000: Freezing remaining freezable tasks ... (elapsed 0.095 seconds) done.
[ 30.661957] 000: printk: Suspending console(s) (use no_console_suspend to debug)
** 19 printk messages dropped **
[ 32.516950] 000: fsl_enetc 0000:00:00.0 eno0: Link is Down
[ 32.520391] 001: PM: resume devices took 0.004 seconds
[ 32.520435] 001: fsl_enetc 0000:00:00.2 eno2: Link is Up - 1Gbps/Full - flow control off
[root@LS[ 32.526325] 001: OOM killer enabled.
1028ARDB 32.540086] 000: PM: suspend exit
01;34m~] # [ 32.550050] 001: Kernel panic - not syncing: Asynchronous SError Interrupt
[ 32.558321] 001: CPU: 1 PID: 141 Comm: kworker/u4:2 Not tainted 5.4.3-rt1 #1

[ 32.565391] 001: Hardware name: LS1028A RDB Board (DT)
[
[ 32.570718] 001: Workqueue: nvme-reset-wq nvme_reset_work

[ 32.576386] 001:

[ 32.578569] 001: Call trace:

[ 32.581710] 001: dump_backtrace+0x0/0x140
3
[ 32.586073] 001: show_stack+0x14/0x20
2
[ 32.590086] 001: dump_stack+0xb4/0x100
.
[ 32.594188] 001: panic+0x15c/0x320
5
[ 32.597939] 001: nmi_panic+0x8c/0x90
2
[ 32.601865] 001: arm64_serror_panic+0x78/0x84
6
[ 32.606576] 001: do_serror+0x7c/0x130
3
[ 32.610590] 001: el1_error+0x84/0xf8
2
[ 32.614517] 001: nvme_reset_work+0x15c/0x1444
9
[ 32.619228] 001: process_one_work+0x198/0x320
]
[ 32.623940] 001: worker_thread+0x48/0x420

[ 32.628302] 001: kthread+0xf4/0x120
0
[ 32.632141] 001: ret_from_fork+0x10/0x18
01
[ 32.636429] 001: ------------[ cut here ]------------
:
[ 32.641824] 001: WARNING: CPU: 1 PID: 141 at kernel/locking/rtmutex.c:2142 __rt_mutex_trylock+0x1c/0xe0

[ 32.651506] 001: Modules linked in:
R
[ 32.655258] 001: flexcan
e
[ 32.658137] 001: can_dev
s
[ 32.661017] 001: pn5xx_i2c
t
[ 32.664071] 001: snd_soc_sgtl5000
a
[ 32.667736] 001: lm90
r
[ 32.670354] 001: ina2xx
t
[ 32.673147] 001: mali_dp
i
[ 32.676027] 001:
n
[ 32.678209] 001: CPU: 1 PID: 141 Comm: kworker/u4:2 Not tainted 5.4.3-rt1 #1
g
[ 32.685537] 001: Hardware name: LS1028A RDB Board (DT)

[ 32.690948] 001: Workqueue: nvme-reset-wq nvme_reset_work
t
[ 32.696616] 001:
a
[ 32.698798] 001: pstate: 000001c5 (nzcv dAIF -PAN -UAO)
s
[ 32.704294] 001: pc : __rt_mutex_trylock+0x1c/0xe0
k
[ 32.709354] 001: lr : _mutex_trylock+0xc/0x20
s
[ 32.713979] 001: sp : ffff8000108db840

[ 32.717993] 001: x29: ffff8000108db840
.
[ 32.722094] 001: x28: ffff00207a058e80
.
[ 32.726195] 001:
.
[ 32.728377] 001: x27: ffff002079eb4000

[ 32.732478] 001: x26: ffff002079eb40b0
d
[ 32.736579] 001:
o
[ 32.738762] 001: x25: ffff002079eb40b0
n
[ 32.742863] 001: x24: ffffb3c23dda8c20
e
[ 32.746963] 001:
.
[ 32.749145] 001: x23: ffffb3c23dda8000

[ 32.753246] 001: x22: ffffb3c23ddd73e8

[ 32.757346] 001:
[ 32.759354] 001: x21: ffffb3c23ddd7000
[ 32.763196] 001: x20: 0000000000000000

[ 32.767037] 001:
[
[ 32.769134] 001: x19: ffff00207a058e80

[ 32.773235] 001: x18: ffffffffffffffff

[ 32.777336] 001:

[ 32.779518] 001: x17: 0000000000000000
3
[ 32.783620] 001: x16: 0000000000000000
2
[ 32.787721] 001:
.
[ 32.789903] 001: x15: ffffb3c2bddb0e46
5
[ 32.794003] 001: x14: ffffb3c23ddb0e49
4
[ 32.798104] 001:
9
[ 32.800286] 001: x13: ffffb3c23dbc8a38
8
[ 32.804387] 001: x12: ffff8000108db870
3
[ 32.808488] 001:
5
[ 32.810670] 001: x11: ffffb3c23db4e4c8
]
[ 32.814772] 001: x10: ffffb3c23db4e4e0

[ 32.818873] 001:
0
[ 32.821055] 001: x9 : 0000000000000001
0
[ 32.825156] 001: x8 : 00000000000b4100
1
[ 32.829257] 001:
:
[ 32.831440] 001: x7 : ffffb3c23ddb0e28

[ 32.835540] 001: x6 : 0000000000000002
n
[ 32.839641] 001:
v
[ 32.841823] 001: x5 : 0000000000000001
m
[ 32.845924] 001: x4 : ffff00207a0598b0
e
[ 32.850025] 001:

[ 32.852207] 001: x3 : 0000000000000002
0
[ 32.856308] 001: x2 : ffff00207a058e80
0
[ 32.860409] 001:
0
[ 32.862591] 001: x1 : 0000000000110001
1
[ 32.866693] 001: x0 : ffffb3c23ddd73f8
:
[ 32.870792] 001:
0
[ 32.872975] 001: Call trace:
1
[ 32.876117] 001: __rt_mutex_trylock+0x1c/0xe0
:
[ 32.880827] 001: _mutex_trylock+0xc/0x20
0
[ 32.885102] 001: __crash_kexec+0x34/0x120
0
[ 32.889465] 001: panic+0x168/0x320
.
[ 32.893217] 001: nmi_panic+0x8c/0x90
0
[ 32.897143] 001: arm64_serror_panic+0x78/0x84
:
[ 32.901855] 001: do_serror+0x7c/0x130

[ 32.905868] 001: el1_error+0x84/0xf8
R
[ 32.909794] 001: nvme_reset_work+0x15c/0x1444
e
[ 32.914506] 001: process_one_work+0x198/0x320
f
[ 32.919217] 001: worker_thread+0x48/0x420
u
[ 32.923579] 001: kthread+0xf4/0x120
s
[ 32.927419] 001: ret_from_fork+0x10/0x18
e
[ 32.931694] 001: ---[ end trace 0000000000000002 ]---
d
[ 32.937017] 001: SMP: stopping secondary CPUs

[ 32.941642] 001: Kernel Offset: 0x33c22ba00000 from 0xffff800010000000

[ 32.948442] 001: PHYS_OFFSET: 0xffffcd3900000000

[ 32.953242] 001: CPU features: 0x0002,21806008

[ 32.957870] 001: Memory Limit: none

[ 32.961540] 001: ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]--- Could you give me the suggestion?

Re: Kernel panic in ls1028ardb

Eddy1 — Mon, 12 Jul 2021 03:11:03 GMT

Hi:

The problem has been solved by reset.

LayerscapeのトピックRe: Kernel panic in ls1028ardb

Kernel panic in ls1028ardb

Re: Kernel panic in ls1028ardb