starred/pve-manager-electrified
1
0
Fork 0
mirror of https://github.com/bogeeee/pve-manager-electrified.git synced 2026-04-26 04:35:49 +03:00
Code Issues 3 Projects Releases Packages Wiki Activity

[GH-ISSUE #2] Bug: Kernel Trace - pve-firewall #1

New issue
Open
opened 2026-03-01 15:35:59 +03:00 by kerem · 1 comment
kerem commented 2026-03-01 15:35:59 +03:00
Owner
Copy link

Originally created by @gyptazy on GitHub (Apr 21, 2025).
Original GitHub issue: https://github.com/bogeeee/pve-manager-electrified/issues/2

Installing PVE-Electrified on a freshly installed Proxmox 8.4 cluster results after rebooting into:

Apr 21 09:29:23 virt01 kernel: INFO: task pve-firewall:896 blocked for more than 122 seconds.
Apr 21 09:29:23 virt01 kernel:       Tainted: P           O       6.8.12-4-pve #1
Apr 21 09:29:23 virt01 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 21 09:29:23 virt01 kernel: task:pve-firewall    state:D stack:0     pid:896   tgid:896   ppid:1      flags:0x00004002
Apr 21 09:29:23 virt01 kernel: Call Trace:
Apr 21 09:29:23 virt01 kernel:  <TASK>
Apr 21 09:29:23 virt01 kernel:  __schedule+0x401/0x15e0
Apr 21 09:29:23 virt01 kernel:  ? xa_load+0x87/0xf0
Apr 21 09:29:23 virt01 kernel:  schedule+0x33/0x110
Apr 21 09:29:23 virt01 kernel:  schedule_preempt_disabled+0x15/0x30
Apr 21 09:29:23 virt01 kernel:  rwsem_down_read_slowpath+0x284/0x4d0
Apr 21 09:29:23 virt01 kernel:  down_read+0x48/0xc0
Apr 21 09:29:23 virt01 kernel:  path_openat+0xaeb/0x1190
Apr 21 09:29:23 virt01 kernel:  ? kfree+0x25e/0x2f0
Apr 21 09:29:23 virt01 kernel:  do_filp_open+0xaf/0x170
Apr 21 09:29:23 virt01 kernel:  do_sys_openat2+0xb3/0xe0
Apr 21 09:29:23 virt01 kernel:  __x64_sys_openat+0x6c/0xa0
Apr 21 09:29:23 virt01 kernel:  x64_sys_call+0x189a/0x24b0
Apr 21 09:29:23 virt01 kernel:  do_syscall_64+0x81/0x170
Apr 21 09:29:23 virt01 kernel:  ? do_filp_open+0xaf/0x170
Apr 21 09:29:23 virt01 kernel:  ? __rseq_handle_notify_resume+0xa5/0x4d0
Apr 21 09:29:23 virt01 kernel:  ? putname+0x5b/0x80
Apr 21 09:29:23 virt01 kernel:  ? restore_fpregs_from_fpstate+0x3d/0xd0
Apr 21 09:29:23 virt01 kernel:  ? switch_fpu_return+0x55/0xf0
Apr 21 09:29:23 virt01 kernel:  ? syscall_exit_to_user_mode+0x86/0x260
Apr 21 09:29:23 virt01 kernel:  ? do_syscall_64+0x8d/0x170
Apr 21 09:29:23 virt01 kernel:  ? do_user_addr_fault+0x337/0x660
Apr 21 09:29:23 virt01 kernel:  ? irqentry_exit_to_user_mode+0x7b/0x260
Apr 21 09:29:23 virt01 kernel:  ? irqentry_exit+0x43/0x50
Apr 21 09:29:23 virt01 kernel:  ? exc_page_fault+0x94/0x1b0
Apr 21 09:29:23 virt01 kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Apr 21 09:29:23 virt01 kernel: RIP: 0033:0x75ca0c0c7fc1
Apr 21 09:29:23 virt01 kernel: RSP: 002b:00007ffc76ece590 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
Apr 21 09:29:23 virt01 kernel: RAX: ffffffffffffffda RBX: 0000000000080000 RCX: 000075ca0c0c7fc1
Apr 21 09:29:23 virt01 kernel: RDX: 0000000000080000 RSI: 00007ffc76ece670 RDI: 00000000ffffff9c
Apr 21 09:29:23 virt01 kernel: RBP: 00007ffc76ece670 R08: 8080808080808080 R09: 0101010101010100
Apr 21 09:29:23 virt01 kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00000000000001b6
Apr 21 09:29:23 virt01 kernel: R13: 0000000000000000 R14: 00007ffc76ece670 R15: 0000000000080000
Apr 21 09:29:23 virt01 kernel:  </TASK>
Apr 21 09:29:23 virt01 kernel: INFO: task pvecm:928 blocked for more than 122 seconds.
Apr 21 09:29:23 virt01 kernel:       Tainted: P           O       6.8.12-4-pve #1
Apr 21 09:29:23 virt01 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 21 09:29:23 virt01 kernel: task:pvecm           state:D stack:0     pid:928   tgid:928   ppid:1      flags:0x00004006
Apr 21 09:29:23 virt01 kernel: Call Trace:
Apr 21 09:29:23 virt01 kernel:  <TASK>
Apr 21 09:29:23 virt01 kernel:  __schedule+0x401/0x15e0
Apr 21 09:29:23 virt01 kernel:  ? autoremove_wake_function+0x12/0x50
Apr 21 09:29:23 virt01 kernel:  schedule+0x33/0x110
Apr 21 09:29:23 virt01 kernel:  request_wait_answer+0x1be/0x2a0
Apr 21 09:29:23 virt01 kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Apr 21 09:29:23 virt01 kernel:  fuse_simple_request+0x19d/0x2d0
Apr 21 09:29:23 virt01 kernel:  fuse_create_open+0x243/0x570
Apr 21 09:29:23 virt01 kernel:  fuse_atomic_open+0x14a/0x1b0
Apr 21 09:29:23 virt01 kernel:  path_openat+0x723/0x1190
Apr 21 09:29:23 virt01 kernel:  do_filp_open+0xaf/0x170
Apr 21 09:29:23 virt01 kernel:  do_sys_openat2+0xb3/0xe0
Apr 21 09:29:23 virt01 kernel:  __x64_sys_openat+0x6c/0xa0
Apr 21 09:29:23 virt01 kernel:  x64_sys_call+0x189a/0x24b0
Apr 21 09:29:23 virt01 kernel:  do_syscall_64+0x81/0x170
Apr 21 09:29:23 virt01 kernel:  ? do_syscall_64+0x8d/0x170
Apr 21 09:29:23 virt01 kernel:  ? __mod_memcg_lruvec_state+0x87/0x140
Apr 21 09:29:23 virt01 kernel:  ? __mod_lruvec_state+0x36/0x50
Apr 21 09:29:23 virt01 kernel:  ? __lruvec_stat_mod_folio+0x70/0xc0
Apr 21 09:29:23 virt01 kernel:  ? set_ptes.constprop.0+0x2b/0xb0
Apr 21 09:29:23 virt01 kernel:  ? _raw_spin_unlock+0xe/0x40
Apr 21 09:29:23 virt01 kernel:  ? do_wp_page+0x508/0xb80
Apr 21 09:29:23 virt01 kernel:  ? __handle_mm_fault+0xbc6/0xf20
Apr 21 09:29:23 virt01 kernel:  ? __count_memcg_events+0x6f/0xe0
Apr 21 09:29:23 virt01 kernel:  ? count_memcg_events.constprop.0+0x2a/0x50
Apr 21 09:29:23 virt01 kernel:  ? handle_mm_fault+0xad/0x380
Apr 21 09:29:23 virt01 kernel:  ? do_user_addr_fault+0x337/0x660
Apr 21 09:29:23 virt01 kernel:  ? irqentry_exit_to_user_mode+0x7b/0x260
Apr 21 09:29:23 virt01 kernel:  ? irqentry_exit+0x43/0x50
Apr 21 09:29:23 virt01 kernel:  ? exc_page_fault+0x94/0x1b0
Apr 21 09:29:23 virt01 kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Apr 21 09:29:23 virt01 kernel: RIP: 0033:0x799e1d5ccfc1
Apr 21 09:29:23 virt01 kernel: RSP: 002b:00007ffd57ae9120 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
Apr 21 09:29:23 virt01 kernel: RAX: ffffffffffffffda RBX: 00000000000800c1 RCX: 0000799e1d5ccfc1
Apr 21 09:29:23 virt01 kernel: RDX: 00000000000800c1 RSI: 000056a1e4b18900 RDI: 00000000ffffff9c
Apr 21 09:29:23 virt01 kernel: RBP: 000056a1e4b18900 R08: 00007ffd57ae9390 R09: 00000000ffffffff
Apr 21 09:29:23 virt01 kernel: R10: 0000000000000180 R11: 0000000000000202 R12: 0000000000000000
Apr 21 09:29:23 virt01 kernel: R13: 0000000000000000 R14: 000056a1e4b18900 R15: 000056a1e21649d0
Apr 21 09:29:23 virt01 kernel:  </TASK>
Apr 21 09:30:02 virt01 systemd[1]: pveproxy.service: State 'final-sigterm' timed out. Killing.
Apr 21 09:30:02 virt01 systemd[1]: pveproxy.service: Killing process 928 (pvecm) with signal SIGKILL.

This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #2 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @gyptazy (replace 20 with the amount, and @gyptazy with the user to tip).

📖 If you want to learn more, check out our documentation.
Originally created by @gyptazy on GitHub (Apr 21, 2025). Original GitHub issue: https://github.com/bogeeee/pve-manager-electrified/issues/2 Installing PVE-Electrified on a freshly installed Proxmox 8.4 cluster results after rebooting into: ``` Apr 21 09:29:23 virt01 kernel: INFO: task pve-firewall:896 blocked for more than 122 seconds. Apr 21 09:29:23 virt01 kernel: Tainted: P O 6.8.12-4-pve #1 Apr 21 09:29:23 virt01 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 21 09:29:23 virt01 kernel: task:pve-firewall state:D stack:0 pid:896 tgid:896 ppid:1 flags:0x00004002 Apr 21 09:29:23 virt01 kernel: Call Trace: Apr 21 09:29:23 virt01 kernel: <TASK> Apr 21 09:29:23 virt01 kernel: __schedule+0x401/0x15e0 Apr 21 09:29:23 virt01 kernel: ? xa_load+0x87/0xf0 Apr 21 09:29:23 virt01 kernel: schedule+0x33/0x110 Apr 21 09:29:23 virt01 kernel: schedule_preempt_disabled+0x15/0x30 Apr 21 09:29:23 virt01 kernel: rwsem_down_read_slowpath+0x284/0x4d0 Apr 21 09:29:23 virt01 kernel: down_read+0x48/0xc0 Apr 21 09:29:23 virt01 kernel: path_openat+0xaeb/0x1190 Apr 21 09:29:23 virt01 kernel: ? kfree+0x25e/0x2f0 Apr 21 09:29:23 virt01 kernel: do_filp_open+0xaf/0x170 Apr 21 09:29:23 virt01 kernel: do_sys_openat2+0xb3/0xe0 Apr 21 09:29:23 virt01 kernel: __x64_sys_openat+0x6c/0xa0 Apr 21 09:29:23 virt01 kernel: x64_sys_call+0x189a/0x24b0 Apr 21 09:29:23 virt01 kernel: do_syscall_64+0x81/0x170 Apr 21 09:29:23 virt01 kernel: ? do_filp_open+0xaf/0x170 Apr 21 09:29:23 virt01 kernel: ? __rseq_handle_notify_resume+0xa5/0x4d0 Apr 21 09:29:23 virt01 kernel: ? putname+0x5b/0x80 Apr 21 09:29:23 virt01 kernel: ? restore_fpregs_from_fpstate+0x3d/0xd0 Apr 21 09:29:23 virt01 kernel: ? switch_fpu_return+0x55/0xf0 Apr 21 09:29:23 virt01 kernel: ? syscall_exit_to_user_mode+0x86/0x260 Apr 21 09:29:23 virt01 kernel: ? do_syscall_64+0x8d/0x170 Apr 21 09:29:23 virt01 kernel: ? do_user_addr_fault+0x337/0x660 Apr 21 09:29:23 virt01 kernel: ? irqentry_exit_to_user_mode+0x7b/0x260 Apr 21 09:29:23 virt01 kernel: ? irqentry_exit+0x43/0x50 Apr 21 09:29:23 virt01 kernel: ? exc_page_fault+0x94/0x1b0 Apr 21 09:29:23 virt01 kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80 Apr 21 09:29:23 virt01 kernel: RIP: 0033:0x75ca0c0c7fc1 Apr 21 09:29:23 virt01 kernel: RSP: 002b:00007ffc76ece590 EFLAGS: 00000202 ORIG_RAX: 0000000000000101 Apr 21 09:29:23 virt01 kernel: RAX: ffffffffffffffda RBX: 0000000000080000 RCX: 000075ca0c0c7fc1 Apr 21 09:29:23 virt01 kernel: RDX: 0000000000080000 RSI: 00007ffc76ece670 RDI: 00000000ffffff9c Apr 21 09:29:23 virt01 kernel: RBP: 00007ffc76ece670 R08: 8080808080808080 R09: 0101010101010100 Apr 21 09:29:23 virt01 kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00000000000001b6 Apr 21 09:29:23 virt01 kernel: R13: 0000000000000000 R14: 00007ffc76ece670 R15: 0000000000080000 Apr 21 09:29:23 virt01 kernel: </TASK> Apr 21 09:29:23 virt01 kernel: INFO: task pvecm:928 blocked for more than 122 seconds. Apr 21 09:29:23 virt01 kernel: Tainted: P O 6.8.12-4-pve #1 Apr 21 09:29:23 virt01 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 21 09:29:23 virt01 kernel: task:pvecm state:D stack:0 pid:928 tgid:928 ppid:1 flags:0x00004006 Apr 21 09:29:23 virt01 kernel: Call Trace: Apr 21 09:29:23 virt01 kernel: <TASK> Apr 21 09:29:23 virt01 kernel: __schedule+0x401/0x15e0 Apr 21 09:29:23 virt01 kernel: ? autoremove_wake_function+0x12/0x50 Apr 21 09:29:23 virt01 kernel: schedule+0x33/0x110 Apr 21 09:29:23 virt01 kernel: request_wait_answer+0x1be/0x2a0 Apr 21 09:29:23 virt01 kernel: ? __pfx_autoremove_wake_function+0x10/0x10 Apr 21 09:29:23 virt01 kernel: fuse_simple_request+0x19d/0x2d0 Apr 21 09:29:23 virt01 kernel: fuse_create_open+0x243/0x570 Apr 21 09:29:23 virt01 kernel: fuse_atomic_open+0x14a/0x1b0 Apr 21 09:29:23 virt01 kernel: path_openat+0x723/0x1190 Apr 21 09:29:23 virt01 kernel: do_filp_open+0xaf/0x170 Apr 21 09:29:23 virt01 kernel: do_sys_openat2+0xb3/0xe0 Apr 21 09:29:23 virt01 kernel: __x64_sys_openat+0x6c/0xa0 Apr 21 09:29:23 virt01 kernel: x64_sys_call+0x189a/0x24b0 Apr 21 09:29:23 virt01 kernel: do_syscall_64+0x81/0x170 Apr 21 09:29:23 virt01 kernel: ? do_syscall_64+0x8d/0x170 Apr 21 09:29:23 virt01 kernel: ? __mod_memcg_lruvec_state+0x87/0x140 Apr 21 09:29:23 virt01 kernel: ? __mod_lruvec_state+0x36/0x50 Apr 21 09:29:23 virt01 kernel: ? __lruvec_stat_mod_folio+0x70/0xc0 Apr 21 09:29:23 virt01 kernel: ? set_ptes.constprop.0+0x2b/0xb0 Apr 21 09:29:23 virt01 kernel: ? _raw_spin_unlock+0xe/0x40 Apr 21 09:29:23 virt01 kernel: ? do_wp_page+0x508/0xb80 Apr 21 09:29:23 virt01 kernel: ? __handle_mm_fault+0xbc6/0xf20 Apr 21 09:29:23 virt01 kernel: ? __count_memcg_events+0x6f/0xe0 Apr 21 09:29:23 virt01 kernel: ? count_memcg_events.constprop.0+0x2a/0x50 Apr 21 09:29:23 virt01 kernel: ? handle_mm_fault+0xad/0x380 Apr 21 09:29:23 virt01 kernel: ? do_user_addr_fault+0x337/0x660 Apr 21 09:29:23 virt01 kernel: ? irqentry_exit_to_user_mode+0x7b/0x260 Apr 21 09:29:23 virt01 kernel: ? irqentry_exit+0x43/0x50 Apr 21 09:29:23 virt01 kernel: ? exc_page_fault+0x94/0x1b0 Apr 21 09:29:23 virt01 kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80 Apr 21 09:29:23 virt01 kernel: RIP: 0033:0x799e1d5ccfc1 Apr 21 09:29:23 virt01 kernel: RSP: 002b:00007ffd57ae9120 EFLAGS: 00000202 ORIG_RAX: 0000000000000101 Apr 21 09:29:23 virt01 kernel: RAX: ffffffffffffffda RBX: 00000000000800c1 RCX: 0000799e1d5ccfc1 Apr 21 09:29:23 virt01 kernel: RDX: 00000000000800c1 RSI: 000056a1e4b18900 RDI: 00000000ffffff9c Apr 21 09:29:23 virt01 kernel: RBP: 000056a1e4b18900 R08: 00007ffd57ae9390 R09: 00000000ffffffff Apr 21 09:29:23 virt01 kernel: R10: 0000000000000180 R11: 0000000000000202 R12: 0000000000000000 Apr 21 09:29:23 virt01 kernel: R13: 0000000000000000 R14: 000056a1e4b18900 R15: 000056a1e21649d0 Apr 21 09:29:23 virt01 kernel: </TASK> Apr 21 09:30:02 virt01 systemd[1]: pveproxy.service: State 'final-sigterm' timed out. Killing. Apr 21 09:30:02 virt01 systemd[1]: pveproxy.service: Killing process 928 (pvecm) with signal SIGKILL. ``` <br/> <hr/> <details><summary>This repo is using Opire - what does it mean? 👇</summary><br/>💵 Everyone can add rewards for this issue commenting <code>/reward 100</code> (replace <code>100</code> with the amount).<br/>🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment <code>/try</code> to let everyone know!<br/>🙌 And when they open the PR, they can comment <code>/claim #2</code> either in the PR description or in a PR's comment.<br/><br/>🪙 Also, everyone can tip any user commenting <code>/tip 20 @gyptazy</code> (replace <code>20</code> with the amount, and <code>@gyptazy</code> with the user to tip).<br/><br/>📖 If you want to learn more, check out our <a href="https://docs.opire.dev">documentation</a>.</details>
kerem commented 2026-03-01 15:36:00 +03:00
Author
Owner
Copy link

@bogeeee commented on GitHub (Apr 22, 2025):

Can't reconstruct it for now, since i don't have a super fresh 8.4 at hand. Seems to work and not produce that log on a manually upgraded PVE 8.4.
I have no clue, how the modification might affect the firewall and pvecm at the moment. Do you have more info? Is the manager still running? What's the pve-firewall.service status? Which services are not working?

<!-- gh-comment-id:2819855022 --> @bogeeee commented on GitHub (Apr 22, 2025): Can't reconstruct it for now, since i don't have a super fresh 8.4 at hand. Seems to work and not produce that log on a manually upgraded PVE 8.4. I have no clue, how the modification might affect the firewall and pvecm at the moment. Do you have more info? Is the manager still running? What's the pve-firewall.service status? Which services are not working?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

No labels
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pve-manager-electrified#1
No description provided.