Random reboots on ODROID-N2+

[Stefan Agner]

Hi,

We are currently testing a new release using Linux 5.10.33. I've
received since several reports of random reboots every couple of days.
Unfortunately the log (journald) doesn't show anything, just a hard cut
at some point.

After running serial console on several instances, I was able to catch
this stack trace:

[202983.988153] SError Interrupt on CPU3, code 0xbf000000 -- SError
[202983.988155] CPU: 3 PID: 3463 Comm: mdns-repeater Not tainted 5.10.33
#1
[202983.988156] Hardware name: Hardkernel ODROID-N2Plus (DT)
[202983.988157] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
[202983.988158] pc : udp_send_skb.isra.0+0x178/0x390
[202983.988159] lr : udp_send_skb.isra.0+0x130/0x390
[202983.988160] sp : ffff8000132a3ae0
[202983.988160] x29: ffff8000132a3ae0 x28: ffff8000132a3bf0
[202983.988164] x27: 00000000fb0000e0 x26: ffff8000132a3d58
[202983.988165] x25: 0000000000000073 x24: ffff000007963e24
[202983.988167] x23: ffff8000132a3bf0 x22: ffff000005a72a80
[202983.988169] x21: 0000000000000011 x20: 0000000000000073
[202983.988170] x19: ffff000001a92c00 x18: 0000000000000001
[202983.988172] x17: 0000000000000000 x16: 0000000000000000
[202983.988173] x15: ffff8000132a3460 x14: 00000000ac1e2001
[202983.988175] x13: ffff0000079181a0 x12: 0000000000000028
[202983.988176] x11: ffff8000d3407000 x10: ffff800010ea8af0
[202983.988178] x9 : 000000000000001b x8 : ffff000007963e00
[202983.988179] x7 : ffff000000000000 x6 : 0000046a76b5fe28
[202983.988181] x5 : 0000000000941cc2 x4 : 0000000000000000
[202983.988182] x3 : 0000000000000001 x2 : ffff8000d3407000
[202983.988184] x1 : ffff00002f6e0000 x0 : 0000000100000001
[202983.988186] Kernel panic - not syncing: Asynchronous SError
Interrupt
[202983.988187] CPU: 3 PID: 3463 Comm: mdns-repeater Not tainted 5.10.33
#1
[202983.988187] Hardware name: Hardkernel ODROID-N2Plus (DT)
[202983.988188] Call trace:
[202983.988188]  dump_backtrace+0x0/0x1a0
[202983.988189]  show_stack+0x18/0x70
[202983.988190]  dump_stack+0xd0/0x12c
[202983.988190]  panic+0x170/0x338
[202983.988191]  nmi_panic+0x8c/0x90
[202983.988191]  arm64_serror_panic+0x78/0x84
[202983.988192]  do_serror+0x38/0xa0
[202983.988193]  el1_error+0x88/0x108
[202983.988193]  udp_send_skb.isra.0+0x178/0x390
[202983.988194]  udp_sendmsg+0x7c8/0x9c0
[202983.988194]  inet_sendmsg+0x44/0x70
[202983.988195]  sock_sendmsg+0x4c/0x60
[202983.988196]  __sys_sendto+0xd0/0x140
[202983.988196]  __arm64_sys_sendto+0x28/0x40
[202983.988197]  el0_svc_common.constprop.0+0x78/0x1a0
[202983.988197]  do_el0_svc+0x24/0x90
[202983.988198]  el0_svc+0x14/0x20
[202983.988199]  el0_sync_handler+0xb0/0xc0
[202983.988199]  el0_sync+0x178/0x180
[202983.988211] SMP: stopping secondary CPUs
[202983.988212] Kernel Offset: disabled
[202983.988212] CPU features: 0x0240002,61082004
[202983.988213] Memory Limit: none

Anyone observed such an issue? I am pretty sure that this is a new issue
as we have many installations using Linux 5.9.16 running stable on the
same hardware,.

Now that I can tell that it is network related I'll try to increase
network load to see if I can find a quicker way to reproduce this.

--
Stefan