Kernel Errors

[HungryBear00]

Hi,

I just installed the 6.8.12-9-pve kernel and my node is going to an unknown/offline state with these errors:

Mar 26 09:37:03 pve2 kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-...D } 4386942 jiffies s: 60105 root: 0x1/.
Mar 26 09:37:03 pve2 kernel: rcu: blocking rcu_node structures (internal RCU debug):
Mar 26 09:37:03 pve2 kernel: Sending NMI from CPU 6 to CPUs 0:
Mar 26 09:37:03 pve2 kernel: NMI backtrace for cpu 0
Mar 26 09:37:03 pve2 kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: P W O 6.8.12-9-pve #1
Mar 26 09:37:03 pve2 kernel: Hardware name: AZW SER/SER, BIOS SER5H508 12/12/2023
Mar 26 09:37:03 pve2 kernel: RIP: 0010:update_sd_lb_stats.constprop.0+0x160/0xae0
Mar 26 09:37:03 pve2 kernel: Code: 41 83 c4 01 48 8b 85 60 ff ff ff 8b 15 c9 73 42 02 49 63 cc 48 8b bd 48 ff ff ff 48 8b 70 38 e8 f6 84 68 00 3b 05 b0 73 42 02 <89> 85 68 ff ff ff 49 89 c4 0f 83 dc 01 00 00 4d 63 f4 4c 8b bd 58
Mar 26 09:37:03 pve2 kernel: RSP: 0018:ffffb348c0003b78 EFLAGS: 00000287
Mar 26 09:37:03 pve2 kernel: RAX: 0000000000000000 RBX: ffffb348c0003d08 RCX: 0000000000000000
Mar 26 09:37:03 pve2 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Mar 26 09:37:03 pve2 kernel: RBP: ffffb348c0003c70 R08: 0000000000000000 R09: 0000000000000000
Mar 26 09:37:03 pve2 kernel: R10: ffffb348c0003c80 R11: ffff9f8c003d4ac0 R12: 0000000000000000
Mar 26 09:37:03 pve2 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffffb348c0003e08
Mar 26 09:37:03 pve2 kernel: FS: 0000000000000000(0000) GS:ffff9f9a30a00000(0000) knlGS:0000000000000000
Mar 26 09:37:03 pve2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 26 09:37:03 pve2 kernel: CR2: 000002694468cf50 CR3: 00000004d4036000 CR4: 0000000000350ef0
Mar 26 09:37:03 pve2 kernel: Call Trace:
Mar 26 09:37:03 pve2 kernel: <NMI>
Mar 26 09:37:03 pve2 kernel: ? show_regs+0x6d/0x80
Mar 26 09:37:03 pve2 kernel: ? nmi_cpu_backtrace+0xb5/0x120
Mar 26 09:37:03 pve2 kernel: ? sched_clock_noinstr+0x9/0x10
Mar 26 09:37:03 pve2 kernel: ? nmi_cpu_backtrace_handler+0x11/0x20
Mar 26 09:37:03 pve2 kernel: ? nmi_handle+0x60/0x160
Mar 26 09:37:03 pve2 kernel: ? default_do_nmi+0x47/0x130
Mar 26 09:37:03 pve2 kernel: ? exc_nmi+0x1c2/0x290
Mar 26 09:37:03 pve2 kernel: ? end_repeat_nmi+0xf/0x60
Mar 26 09:37:03 pve2 kernel: ? update_sd_lb_stats.constprop.0+0x160/0xae0
Mar 26 09:37:03 pve2 kernel: ? update_sd_lb_stats.constprop.0+0x160/0xae0
Mar 26 09:37:03 pve2 kernel: ? update_sd_lb_stats.constprop.0+0x160/0xae0
Mar 26 09:37:03 pve2 kernel: </NMI>
Mar 26 09:37:03 pve2 kernel: <IRQ>
Mar 26 09:37:03 pve2 kernel: ? __update_load_avg_cfs_rq+0x238/0x2d0
Mar 26 09:37:03 pve2 kernel: find_busiest_group+0x4d/0x500
Mar 26 09:37:03 pve2 kernel: load_balance+0x16a/0xfd0
Mar 26 09:37:03 pve2 kernel: ? srso_return_thunk+0x5/0x5f
Mar 26 09:37:03 pve2 kernel: ? wake_up_process+0x15/0x30
Mar 26 09:37:03 pve2 kernel: ? kick_pool+0x7e/0x110
Mar 26 09:37:03 pve2 kernel: rebalance_domains+0x295/0x3b0
Mar 26 09:37:03 pve2 kernel: ? srso_return_thunk+0x5/0x5f
Mar 26 09:37:03 pve2 kernel: run_rebalance_domains+0x5c/0x80
Mar 26 09:37:03 pve2 kernel: handle_softirqs+0xd8/0x300
Mar 26 09:37:03 pve2 kernel: __irq_exit_rcu+0xd9/0x100
Mar 26 09:37:03 pve2 kernel: irq_exit_rcu+0xe/0x20
Mar 26 09:37:03 pve2 kernel: sysvec_apic_timer_interrupt+0x92/0xd0
Mar 26 09:37:03 pve2 kernel: </IRQ>
Mar 26 09:37:03 pve2 kernel: <TASK>
Mar 26 09:37:03 pve2 kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20
Mar 26 09:37:03 pve2 kernel: RIP: 0010:cpuidle_enter_state+0xce/0x470
Mar 26 09:37:03 pve2 kernel: Code: e4 01 ff e8 f4 ee ff ff 8b 53 04 49 89 c6 0f 1f 44 00 00 31 ff e8 f2 d2 00 ff 80 7d d7 00 0f 85 e7 01 00 00 fb 0f 1f 44 00 00 <45> 85 ff 0f 88 83 01 00 00 49 63 d7 4c 89 f1 48 8d 04 52 48 8d 04
Mar 26 09:37:03 pve2 kernel: RSP: 0018:ffffffffbd603db8 EFLAGS: 00000246
Mar 26 09:37:03 pve2 kernel: RAX: 0000000000000000 RBX: ffff9f8c00948000 RCX: 0000000000000000
Mar 26 09:37:03 pve2 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Mar 26 09:37:03 pve2 kernel: RBP: ffffffffbd603df0 R08: 0000000000000000 R09: 0000000000000000
Mar 26 09:37:03 pve2 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000003
Mar 26 09:37:03 pve2 kernel: R13: ffffffffbd87eb60 R14: 00008844bf0b53c1 R15: 0000000000000003
Mar 26 09:37:03 pve2 kernel: ? cpuidle_enter_state+0xbe/0x470
Mar 26 09:37:03 pve2 kernel: cpuidle_enter+0x2e/0x50
Mar 26 09:37:03 pve2 kernel: call_cpuidle+0x23/0x60
Mar 26 09:37:03 pve2 kernel: do_idle+0x207/0x260
Mar 26 09:37:03 pve2 kernel: cpu_startup_entry+0x2a/0x30
Mar 26 09:37:03 pve2 kernel: rest_init+0xd0/0xd0
Mar 26 09:37:03 pve2 kernel: arch_call_rest_init+0xe/0x30
Mar 26 09:37:03 pve2 kernel: start_kernel+0x729/0xb00
Mar 26 09:37:03 pve2 kernel: x86_64_start_reservations+0x18/0x30
Mar 26 09:37:03 pve2 kernel: x86_64_start_kernel+0xbf/0x110
Mar 26 09:37:03 pve2 kernel: secondary_startup_64_no_verify+0x184/0x18b
Mar 26 09:37:03 pve2 kernel: </TASK>

Can someone help me?

Thank you

 

[dakralex]

Hi!

Are there any BIOS firmware upgrades available for your mainboard? Have you modified any BIOS settings on the machine?

 

[HungryBear00]

Hi!

Are there any BIOS firmware upgrades available for your mainboard? Have you modified any BIOS settings on the machine?

Hi, as of now I have the stock BIOS that came with the mini pc (Beelink SER5 Pro) without modifications.
I’ll check on the vendor site if there is something useful to check and update BIOS if available.

Thank you for the suggestion

 

[HungryBear00]

Hi,

I updated the BIOS on my mini pc but the problem is still here, any other suggestion?

 

[readyspace]

Hi @HungryBear00 , as there isnt a way to verify if it is a hardware issue. Have you tried using the latest kernel 6.14?

 

[HungryBear00]

Hi i did not tried it, how do i upgrade to the 6.14? Thank you

 

[readyspace]

Hi @HungryBear00 , here are more information you can refer to relating to kernel upgrade

Thread 'Opt-in Linux 6.14 Kernel for Proxmox VE 8 available on test & no-subscription'

Wednesday at 21:20

We recently uploaded a 6.14 kernel into our repositories. The current 6.8 kernel will stay the default on the Proxmox VE 8 series, the newly introduced 6.14 kernel is an option.
The 6.14 based kernel may be useful for some (especially newer) setups, for example if there is improved hardware support that has not yet been backported to 6.8.
This follows our tradition of upgrading the Proxmox VE kernel to match the current Ubuntu version until we reach an (Ubuntu) LTS release, like the 6.8 kernel is, and then provide newer kernels as opt-in. The 6.14 kernel is based on the Ubuntu 25.04 Plucky...

• t.lamprecht
• kernel 6.14 linux 6.14 opt-in kernel
• Replies: 45
• Forum: Proxmox VE: Installation and configuration

• 

 

[HungryBear00]

Thank you! I will check it out and will see in some days if the issue is still present