0.62rc and 0.63 snapshot kernel crash R5S

[hle5128]

Expected Behavior

Expect to run normal

Current Behavior

Crashed after restarting: kern.err kernel

Possible Solution

has no problem 0.61

Steps to Reproduce the Problem

1. running on r5s
2. fresh installation
3. after entering vps booth up and crashed

Context (Environment)

[openmptcprouter v0.63-snapshot-6.6 r0+28431-92e020b50f]
and
0.62rc1

Specifications

• OpenMPTCProuter version: 0.62rc1 and v0.63-snapshot-6.6 r0+28431-92e020b50f
• OpenMPTCProuter VPS version: failed to run vps 0.62rc1 so run (wget -O - https://www.openmptcprouter.com/server-test/debian-x86_64.sh | KERNEL="6.12" sh)
• OpenMPTCProuter VPS provider: buyvm
• OpenMPTCProuter platform: r5s
• Country: IP

https://pastebin.com/xEFzGgaQ

[hle5128]

Fri Mar 28 18:17:59 2025 user.notice firewall.omr-server: Firewall reload, set server part firewall reloading
Fri Mar 28 18:18:34 2025 daemon.err /usr/bin/ss-redir[12140]: remote recv: Socket not connected
Fri Mar 28 18:19:10 2025 kern.err kernel: [  305.191733] rcu: INFO: rcu_sched self-detected stall on CPU
Fri Mar 28 18:19:10 2025 kern.err kernel: [  305.192255] rcu: 	3-....: (5999 ticks this GP) idle=9654/1/0x4000000000000000 softirq=117173/117173 fqs=2806
Fri Mar 28 18:19:10 2025 kern.err kernel: [  305.193127] rcu: 	(t=6000 jiffies g=37149 q=870612 ncpus=4)
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.193621] CPU: 3 PID: 31 Comm: kworker/3:0 Tainted: G           O       6.6.73 #0
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.194293] Hardware name: FriendlyElec NanoPi R5S (DT)
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.194754] Workqueue: events mptcp_worker
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.195130] pstate: 40400009 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.195740] pc : __bpf_prog_enter+0x1c/0x5c
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.196114] lr : __bpf_prog_enter+0x18/0x5c
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.196482] sp : ffff800081a5bb60
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.196773] x29: ffff800081a5bb60 x28: 0000000000000001 x27: 00000000000000b0
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.197402] x26: 0000000000000000 x25: ffff00000bd81740 x24: ffff00000bd81de0
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.198029] x23: 0000000000000001 x22: 0000000000000001 x21: ffff000010bb7500
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.198656] x20: ffff000010bb7500 x19: ffff800081a5bb80 x18: 0000000000000000
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.199282] x17: ffff80006d540000 x16: ffff800081890000 x15: 006aaa91632f1fda
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.199908] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000001
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.200534] x11: 7f7f7f7f7f7f7f7f x10: ffff80008019bfc0 x9 : ffff800081ee1068
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.201161] x8 : ffff800081a5bc40 x7 : 0000000000000000 x6 : ffff0000ee7e6040
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.201788] x5 : ffff000008bab1c0 x4 : 0000000000000008 x3 : 0000000000000001
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.202414] x2 : 0000000000000001 x1 : ffff0000006a2940 x0 : ffff0000006a2940
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.203040] Call trace:
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.203257]  __bpf_prog_enter+0x1c/0x5c
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.203596]  0xffff800081ee104c
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.203878]  mptcp_sched_get_send+0xe4/0x138
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.204259]  __mptcp_push_pending+0x50/0x218
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.204638]  __mptcp_close_ssk+0x2bc/0x464
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.205001]  mptcp_close_ssk+0x64/0x90
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.205332]  mptcp_worker+0x298/0x4b4
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.205658]  process_one_work+0x168/0x39c
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.206017]  worker_thread+0x2b0/0x490
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.206349]  kthread+0xe0/0xe4
Fri Mar 28 18:19:10 2025 kern.warn kernel: [  305.206623]  ret_from_fork+0x10/0x20```

[Ysurac]

Do you run another MPTCP scheduler than default ?

[hle5128]

I tested the default as well rrOn Mar 28, 2025, at 2:59 PM, Ycarus (Yannick Chabanois) ***@***.***> wrote: Do you run another MPTCP scheduler than default ?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> Ysurac left a comment (Ysurac/openmptcprouter#3880) Do you run another MPTCP scheduler than default ? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Ysurac]

Here the log is with a MPTCP Scheduler ? Can you give the kernel error with default scheduler ?

[hle5128]

It looks like when we plug in 2nd eth, then it crashes after. If we remove the 2nd ETH cable and reboot, the crash stops, but no, I didnt change the motco scheduler. It was the default when it crashed On Mar 28, 2025, at 4:00 PM, Ycarus (Yannick Chabanois) ***@***.***> wrote: Here the log is with a MPTCP Scheduler ? Can you give the kernel error with default scheduler ?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> Ysurac left a comment (Ysurac/openmptcprouter#3880) Here the log is with a MPTCP Scheduler ? Can you give the kernel error with default scheduler ? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Ysurac]

Because the crash log was speaking about bpf and MPTCP. But if it's a problem with ethernet can be related to the driver. I will check this part.