nvidia-powerd caused kernel panic

nemutai · 2025-05-08 06:50:50

So nvidia-powerd will cause kernel panic randomly. It may happen when I run reboot or shutdown (which means kernel panic doesn't always happen). When it causes a kernel panic, I can always see it trying to dereference NULL pointer

The two kernel panics I remember the most happened during kernel updates and filesystem package updates, the kernel panic happened when I finished executing the updates and rebooted. Not sure if kernel panic is directly related to those updates.

Anyway, here's the output of the journalctl command:

❯ journalctl -b -1 --no-pager | grep -A30 "BUG: kernel NULL pointer dereference"
May 08 13:48:15 my-labtop kernel: BUG: kernel NULL pointer dereference, address: 0000000000000110
May 08 13:48:15 my-labtop kernel: #PF: supervisor read access in kernel mode
May 08 13:48:15 my-labtop kernel: #PF: error_code(0x0000) - not-present page
May 08 13:48:15 my-labtop kernel: PGD 10263d067 P4D 10263d067 PUD 124d3f067 PMD 0
May 08 13:48:15 my-labtop kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
May 08 13:48:15 my-labtop kernel: CPU: 1 UID: 0 PID: 828 Comm: nvidia-powerd Tainted: P           OE      6.14.5-zen1-1-zen #1 389202a9011d1a67c3333db7042d0d89e60984ef
May 08 13:48:15 my-labtop kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
May 08 13:48:15 my-labtop kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX507ZM_FX507ZM/FX507ZM, BIOS FX507ZM.315 06/17/2022
May 08 13:48:15 my-labtop kernel: RIP: 0010:_nv051470rm+0x5e/0x100 [nvidia]
May 08 13:48:15 my-labtop kernel: Code: 89 ef 4c 8b 60 08 e8 91 90 9d 00 48 89 c3 66 0f 1f 44 00 00 49 39 dc 74 3b 48 89 de 4c 89 ef 49 89 de e8 15 91 9d 00 48 89 c3 <49> 8b 86 10 01 00 00 83 78 20 01 75 dd b9 01 00 00 00 4c 89 f2 4c
May 08 13:48:15 my-labtop kernel: RSP: 0018:ffffac0e029cbb50 EFLAGS: 00010286
May 08 13:48:15 my-labtop kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000020
May 08 13:48:15 my-labtop kernel: RDX: 0000000000000001 RSI: ffff8bbce8e5dc94 RDI: 0000000000000001
May 08 13:48:15 my-labtop kernel: RBP: ffff8bbce8e5dca0 R08: 0000000000000020 R09: 0000000000000000
May 08 13:48:15 my-labtop kernel: R10: 0000000000000000 R11: 681c459f000369a3 R12: ffff8bbd037d3830
May 08 13:48:15 my-labtop kernel: R13: ffff8bbce2c080e0 R14: 0000000000000000 R15: ffff8bbce2c08018
May 08 13:48:15 my-labtop kernel: FS:  000079a5b5eb86c0(0000) GS:ffff8bc05fe80000(0000) knlGS:0000000000000000
May 08 13:48:15 my-labtop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 08 13:48:15 my-labtop kernel: CR2: 0000000000000110 CR3: 0000000139bd5006 CR4: 0000000000f72ef0
May 08 13:48:15 my-labtop kernel: PKRU: 55555554
May 08 13:48:15 my-labtop kernel: Call Trace:
May 08 13:48:15 my-labtop kernel:  <TASK>
May 08 13:48:15 my-labtop kernel:  _nv053334rm+0x2ca/0x730 [nvidia 5eae79b73ff823938b0e610232b71e3405ff3a7e]
May 08 13:48:15 my-labtop kernel:  _nv051340rm+0xca/0x130 [nvidia 5eae79b73ff823938b0e610232b71e3405ff3a7e]
May 08 13:48:15 my-labtop kernel:  _nv051341rm+0x41/0x70 [nvidia 5eae79b73ff823938b0e610232b71e3405ff3a7e]
May 08 13:48:15 my-labtop kernel:  _nv000620rm+0x4a/0x60 [nvidia 5eae79b73ff823938b0e610232b71e3405ff3a7e]
May 08 13:48:15 my-labtop kernel:  _nv000778rm+0x20f/0xe00 [nvidia 5eae79b73ff823938b0e610232b71e3405ff3a7e]
May 08 13:48:15 my-labtop kernel:  rm_ioctl+0x7f/0x400 [nvidia 5eae79b73ff823938b0e610232b71e3405ff3a7e]
May 08 13:48:15 my-labtop kernel:  nvidia_unlocked_ioctl+0x516/0xa50 [nvidia 5eae79b73ff823938b0e610232b71e3405ff3a7e]
May 08 13:48:15 my-labtop kernel:  __x64_sys_ioctl+0x94/0xc0
May 08 13:48:15 my-labtop kernel:  do_syscall_64+0x7b/0x190

My device is Asus TUF Gaming F15 FX507ZM, with 12700h and 3060 labtop, this is the output of uname -a :

Linux my-labtop 6.14.5-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sat, 03 May 2025 13:33:50 +0000 x86_64 GNU/Linux

Maybe I should stop using the zen kernel and switch to the stable kernel? Or even LTS? Either way, thanks in advance.

Last edited by nemutai (2025-05-08 10:13:16)

nemutai · 2025-05-08 07:00:18

And nvidia-dkms is the driver that i am using.

❯ sudo pacman -Qs nvidia-dkms
local/nvidia-dkms 570.144-3
    NVIDIA kernel modules - module sources

Though I won't use 3060 as graphics card, I still need it to deal with some AI things, so I can't just disable it.

Last edited by nemutai (2025-05-08 08:25:59)

V1del · 2025-05-08 18:58:16

Feels like a variation of the issues in https://gitlab.archlinux.org/archlinux/ … /issues/26

Do things stabilize when doing

sudo touch /etc/systemd/do-not-udevadm-trigger-on-update

, did the issue only happen after resuming from suspend and then doing an update followed by a shutdown?

Last edited by V1del (2025-05-08 18:59:29)

nemutai · 2025-05-09 05:21:42

V1del wrote:

Feels like a variation of the issues in https://gitlab.archlinux.org/archlinux/ … /issues/26
Do things stabilize when doing
sudo touch /etc/systemd/do-not-udevadm-trigger-on-update
, did the issue only happen after resuming from suspend and then doing an update followed by a shutdown?

I checked my logs and there were three documented kernel panics. I've run pacman -Syu all three times, and the system should have experienced suspend. Here's some more information.

The earliest was the one on May 4, on that day, I executed pacman -Syu at around 12:04, here is the log:

[2025-05-04T12:04:01+0800] [PACMAN] Running 'pacman -Syu'
[2025-05-04T12:04:01+0800] [PACMAN] synchronizing package lists
[2025-05-04T12:04:04+0800] [PACMAN] starting full system upgrade
[2025-05-04T12:04:14+0800] [ALPM] transaction started
[2025-05-04T12:04:14+0800] [ALPM] upgraded ca-certificates-mozilla (3.110-1 -> 3.111-1)
[2025-05-04T12:04:14+0800] [ALPM] upgraded libxkbcommon (1.9.0-1 -> 1.9.1-1)
[2025-05-04T12:04:14+0800] [ALPM] upgraded libxkbcommon-x11 (1.9.0-1 -> 1.9.1-1)
[2025-05-04T12:04:14+0800] [ALPM] upgraded libpng (1.6.47-1 -> 1.6.48-1)
[2025-05-04T12:04:14+0800] [ALPM] upgraded mesa (1:25.0.4-1 -> 1:25.0.5-1)
[2025-05-04T12:04:14+0800] [ALPM] upgraded pixman (0.44.2-1 -> 0.46.0-1)
[2025-05-04T12:04:15+0800] [ALPM] upgraded fcitx5-mozc (2.31.5712.102.g9dc8247-3 -> 2.31.5810.102.gb091429-1)
[2025-05-04T12:04:15+0800] [ALPM] upgraded gtk-update-icon-cache (1:4.18.4-1 -> 1:4.18.5-1)
[2025-05-04T12:04:15+0800] [ALPM] upgraded nss (3.110-1 -> 3.111-1)
[2025-05-04T12:04:15+0800] [ALPM] upgraded openucx (1.18.0-3 -> 1.18.1-1)
[2025-05-04T12:04:15+0800] [ALPM] upgraded smartmontools (7.4-2 -> 7.5-1)
[2025-05-04T12:04:15+0800] [ALPM] upgraded vim-runtime (9.1.1337-1 -> 9.1.1362-1)
[2025-05-04T12:04:15+0800] [ALPM] upgraded vim (9.1.1337-1 -> 9.1.1362-1)
[2025-05-04T12:04:15+0800] [ALPM] transaction completed
[2025-05-04T12:04:15+0800] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2025-05-04T12:04:15+0800] [ALPM] running '30-systemd-restart-marked.hook'...
[2025-05-04T12:04:15+0800] [ALPM] running '30-systemd-update.hook'...
[2025-05-04T12:04:15+0800] [ALPM] running '40-update-ca-trust.hook'...
[2025-05-04T12:04:16+0800] [ALPM] running 'gtk-update-icon-cache.hook'...
[2025-05-04T12:04:16+0800] [ALPM] running 'update-desktop-database.hook'...
[2025-05-04T12:04:29+0800] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-05-04T12:04:29+0800] [PACMAN] synchronizing package lists
[2025-05-04T20:10:56+0800] [PACMAN] Running 'pacman -Syu'
[2025-05-04T20:10:56+0800] [PACMAN] synchronizing package lists
[2025-05-04T20:11:01+0800] [PACMAN] starting full system upgrade
[2025-05-04T20:11:06+0800] [ALPM] transaction started
[2025-05-04T20:11:06+0800] [ALPM] upgraded python-setuptools (1:79.0.1-1 -> 1:80.0.0-1)
[2025-05-04T20:11:06+0800] [ALPM] transaction completed
[2025-05-04T20:11:06+0800] [ALPM] running '30-systemd-update.hook'...

The system then performed several suspends:

May 04 14:41:02 my-labtop kernel: Low-power S0 idle used by default for system suspend
May 04 15:03:20 my-labtop systemd-logind[714]: The system will suspend now!
May 04 15:03:20 my-labtop systemd[1]: Starting NVIDIA system suspend actions...
May 04 15:03:20 my-labtop suspend[7736]: nvidia-suspend.service
May 04 15:03:20 my-labtop logger[7736]: <13>May  4 15:03:20 suspend: nvidia-suspend.service
May 04 15:03:23 my-labtop systemd[1]: nvidia-suspend.service: Deactivated successfully.
May 04 15:03:23 my-labtop systemd[1]: Finished NVIDIA system suspend actions.
May 04 15:03:23 my-labtop systemd[1]: nvidia-suspend.service: Consumed 1.916s CPU time, 18.9M memory peak.
May 04 15:03:23 my-labtop systemd[1]: Starting System Suspend...
May 04 15:03:23 my-labtop systemd-sleep[7769]: in suspend-then-hibernate operations or setups with encrypted home directories.
May 04 15:03:23 my-labtop systemd-sleep[7769]: Performing sleep operation 'suspend'...
May 04 15:03:23 my-labtop kernel: PM: suspend entry (s2idle)
May 04 19:00:07 my-labtop kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 04 19:00:07 my-labtop kernel: PM: suspend exit
May 04 19:00:07 my-labtop systemd-sleep[7769]: System returned from sleep operation 'suspend'.
May 04 19:00:08 my-labtop systemd[1]: systemd-suspend.service: Deactivated successfully.
May 04 19:00:08 my-labtop systemd[1]: Finished System Suspend.
May 04 19:00:08 my-labtop systemd[1]: systemd-suspend.service: Consumed 1.028s CPU time, 3.6M memory peak.
May 04 19:00:08 my-labtop systemd[1]: Reached target Suspend.
May 04 19:00:08 my-labtop systemd[1]: Stopped target Suspend.
May 04 19:00:08 my-labtop systemd-logind[714]: Operation 'suspend' finished.
May 04 19:00:08 my-labtop suspend[7926]: nvidia-resume.service
May 04 19:00:08 my-labtop logger[7926]: <13>May  4 19:00:08 suspend: nvidia-resume.service
May 04 19:18:24 my-labtop systemd-logind[714]: The system will suspend now!
May 04 19:18:24 my-labtop systemd[1]: Starting NVIDIA system suspend actions...
May 04 19:18:24 my-labtop suspend[8943]: nvidia-suspend.service
May 04 19:18:24 my-labtop logger[8943]: <13>May  4 19:18:24 suspend: nvidia-suspend.service
May 04 19:18:27 my-labtop systemd[1]: nvidia-suspend.service: Deactivated successfully.
May 04 19:18:27 my-labtop systemd[1]: Finished NVIDIA system suspend actions.
May 04 19:18:27 my-labtop systemd[1]: nvidia-suspend.service: Consumed 1.923s CPU time, 18.7M memory peak.
May 04 19:18:27 my-labtop systemd[1]: Starting System Suspend...
May 04 19:18:27 my-labtop systemd-sleep[8971]: in suspend-then-hibernate operations or setups with encrypted home directories.
May 04 19:18:27 my-labtop systemd-sleep[8971]: Performing sleep operation 'suspend'...
May 04 19:18:27 my-labtop kernel: PM: suspend entry (s2idle)
May 04 19:21:49 my-labtop kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 04 19:21:49 my-labtop systemd-sleep[8971]: System returned from sleep operation 'suspend'.
May 04 19:21:49 my-labtop kernel: PM: suspend exit
May 04 19:21:50 my-labtop systemd[1]: systemd-suspend.service: Deactivated successfully.
May 04 19:21:50 my-labtop systemd[1]: Finished System Suspend.
May 04 19:21:50 my-labtop systemd[1]: Reached target Suspend.
May 04 19:21:50 my-labtop systemd-logind[714]: Operation 'suspend' finished.
May 04 19:21:50 my-labtop systemd[1]: Stopped target Suspend.
May 04 19:21:50 my-labtop suspend[9075]: nvidia-resume.service
May 04 19:21:50 my-labtop logger[9075]: <13>May  4 19:21:50 suspend: nvidia-resume.service

And finally the kernel panic, which happened at 19:59:43, I've intercepted part of the log:

May 04 19:59:43 my-labtop kernel: BUG: kernel NULL pointer dereference, address: 0000000000000110
May 04 19:59:43 my-labtop kernel: #PF: supervisor read access in kernel mode
May 04 19:59:43 my-labtop kernel: #PF: error_code(0x0000) - not-present page
May 04 19:59:43 my-labtop kernel: PGD 13a520067 P4D 13a520067 PUD 13d06d067 PMD 0 
May 04 19:59:43 my-labtop kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
May 04 19:59:43 my-labtop kernel: CPU: 11 UID: 0 PID: 903 Comm: nvidia-powerd Tainted: P           OE      6.14.4-zen1-2-zen #1 5ebf8709a7a4a4d9e2b75723b74cfc48d75c3151
May 04 19:59:43 my-labtop kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
May 04 19:59:43 my-labtop kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX507ZM_FX507ZM/FX507ZM, BIOS FX507ZM.315 06/17/2022
May 04 19:59:43 my-labtop kernel: RIP: 0010:_nv051470rm+0x5e/0x100 [nvidia]
May 04 19:59:43 my-labtop kernel: Code: 89 ef 4c 8b 60 08 e8 91 90 9d 00 48 89 c3 66 0f 1f 44 00 00 49 39 dc 74 3b 48 89 de 4c 89 ef 49 89 de e8 15 91 9d 00 48 89 c3 <49> 8b 86 10 01 00 00 83 78 20 01 75 dd b9 01 00 00 00 4c 89 f2 4c
May 04 19:59:43 my-labtop kernel: RSP: 0018:ffffba27c48ef9e0 EFLAGS: 00010286
May 04 19:59:43 my-labtop kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000020
May 04 19:59:43 my-labtop kernel: RDX: 0000000000000001 RSI: ffff955ab176ac94 RDI: 0000000000000001
May 04 19:59:43 my-labtop kernel: RBP: ffff955ab176aca0 R08: 0000000000000020 R09: 0000000000000000
May 04 19:59:43 my-labtop kernel: R10: 0000000000000000 R11: 681756af0006b8a2 R12: ffff955a920f8c30
May 04 19:59:43 my-labtop kernel: R13: ffff955a920f90e0 R14: 0000000000000000 R15: ffff955a920f9018
May 04 19:59:43 my-labtop kernel: FS:  0000778891390740(0000) GS:ffff955e20380000(0000) knlGS:0000000000000000
May 04 19:59:43 my-labtop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 04 19:59:43 my-labtop kernel: CR2: 0000000000000110 CR3: 000000012c930006 CR4: 0000000000f72ef0
May 04 19:59:43 my-labtop kernel: PKRU: 55555554
May 04 19:59:43 my-labtop kernel: Call Trace:
May 04 19:59:43 my-labtop kernel:  <TASK>
May 04 19:59:43 my-labtop kernel:  _nv053334rm+0x2ca/0x730 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  _nv051340rm+0xca/0x130 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  _nv051341rm+0x41/0x70 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  _nv000620rm+0x4a/0x60 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  _nv000778rm+0x20f/0xe00 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  rm_ioctl+0x7f/0x400 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  ? __mod_memcg_lruvec_state+0xb1/0x1c0
May 04 19:59:43 my-labtop kernel:  nvidia_unlocked_ioctl+0x516/0xa50 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  __x64_sys_ioctl+0x94/0xc0
May 04 19:59:43 my-labtop kernel:  do_syscall_64+0x7b/0x190
May 04 19:59:43 my-labtop kernel:  ? os_acquire_spinlock+0x12/0x30 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  ? _nv049926rm+0x10/0x20 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  ? _nv056403rm+0xde/0x1c0 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  ? rm_ioctl+0x8e/0x400 [nvidia bca86b69d1ee4fa87d154ba4cd07b4321ee86971]
May 04 19:59:43 my-labtop kernel:  ? syscall_exit_to_user_mode+0x1d6/0x210
May 04 19:59:43 my-labtop kernel:  ? kfree+0x2fd/0x3b0
May 04 19:59:43 my-labtop kernel:  ? __check_object_size+0x1ff/0x220
May 04 19:59:43 my-labtop kernel:  ? __rseq_handle_notify_resume+0x23e/0x510
May 04 19:59:43 my-labtop kernel:  ? switch_fpu_return+0x4e/0xd0
May 04 19:59:43 my-labtop kernel:  ? syscall_exit_to_user_mode+0x1d6/0x210
May 04 19:59:43 my-labtop kernel:  ? do_syscall_64+0x87/0x190
May 04 19:59:43 my-labtop kernel:  ? do_syscall_64+0x87/0x190
May 04 19:59:43 my-labtop kernel:  ? syscall_exit_to_user_mode+0x19f/0x210
May 04 19:59:43 my-labtop kernel:  ? do_syscall_64+0x87/0x190
May 04 19:59:43 my-labtop kernel:  ? do_syscall_64+0x87/0x190
May 04 19:59:43 my-labtop kernel:  ? irqentry_exit_to_user_mode+0x194/0x200
May 04 19:59:43 my-labtop kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e

The second kernel panic that happened on May 7, happened after I updated the kernel. But the timeline of this log is a bit messy because I installed windows on another hard disk of my computer and booted it multiple times on that day, it messed up the time, so I won't give the log for this one and will just narrate the parts I am sure of.
The kernel update happened on May 7 at 12:48:04 and the kernel panic happened on the same day at 13:13:27. About the suspend, I'm not sure it exists, sorry. If you ask me, I'd say there's a high probability it exists.

Anyway, the third time, that kernel panic on May 8, it happened yesterday (yesterday for me), here are logs.
First, at 12:17, I executed that update containing filesystem package.

[2025-05-08T00:47:45+0800] [PACMAN] Running 'pacman -Syu'
[2025-05-08T00:47:45+0800] [PACMAN] synchronizing package lists
[2025-05-08T00:47:51+0800] [PACMAN] starting full system upgrade
[2025-05-08T12:17:03+0800] [PACMAN] Running 'pacman -Syu'
[2025-05-08T12:17:03+0800] [PACMAN] synchronizing package lists
[2025-05-08T12:17:06+0800] [PACMAN] starting full system upgrade
[2025-05-08T12:17:11+0800] [ALPM] transaction started
[2025-05-08T12:17:11+0800] [ALPM] upgraded filesystem (2024.11.21-1 -> 2025.05.03-1)
[2025-05-08T12:17:11+0800] [ALPM] upgraded fluidsynth (2.4.5-3 -> 2.4.6-1)
[2025-05-08T12:17:11+0800] [ALPM] upgraded libxkbcommon (1.9.1-1 -> 1.9.2-1)
[2025-05-08T12:17:11+0800] [ALPM] upgraded libxkbcommon-x11 (1.9.1-1 -> 1.9.2-1)
[2025-05-08T12:17:11+0800] [ALPM] upgraded python-charset-normalizer (3.4.1-1 -> 3.4.2-1)
[2025-05-08T12:17:11+0800] [ALPM] upgraded python-setuptools (1:80.0.0-1 -> 1:80.3.1-1)
[2025-05-08T12:17:11+0800] [ALPM] transaction completed
[2025-05-08T12:17:11+0800] [ALPM] running '20-systemd-sysusers.hook'...
[2025-05-08T12:17:12+0800] [ALPM] running '30-systemd-daemon-reload-user.hook'...
[2025-05-08T12:17:12+0800] [ALPM] running '30-systemd-sysctl.hook'...
[2025-05-08T12:17:12+0800] [ALPM] running '30-systemd-tmpfiles.hook'...
[2025-05-08T12:17:12+0800] [ALPM] running '30-systemd-update.hook'...
[2025-05-08T14:01:04+0800] [PACMAN] Running 'pacman -S bc'
[2025-05-08T14:01:49+0800] [PACMAN] Running 'pacman -S bc'
[2025-05-08T14:01:55+0800] [ALPM] transaction started
[2025-05-08T14:01:55+0800] [ALPM] installed bc (1.08.1-1)
[2025-05-08T14:01:55+0800] [ALPM] transaction completed
[2025-05-08T14:01:55+0800] [ALPM] running '30-systemd-update.hook'...
[2025-05-08T14:01:55+0800] [ALPM] running 'texinfo-install.hook'...

Then my system went through two suspends:

May 08 12:16:02 my-labtop kernel: Low-power S0 idle used by default for system suspend
May 08 12:44:27 my-labtop systemd-logind[717]: The system will suspend now!
May 08 12:44:27 my-labtop systemd[1]: Starting NVIDIA system suspend actions...
May 08 12:44:27 my-labtop suspend[3393]: nvidia-suspend.service
May 08 12:44:27 my-labtop logger[3393]: <13>May  8 12:44:27 suspend: nvidia-suspend.service
May 08 12:44:28 my-labtop systemd[1]: nvidia-suspend.service: Deactivated successfully.
May 08 12:44:28 my-labtop systemd[1]: Finished NVIDIA system suspend actions.
May 08 12:44:28 my-labtop systemd[1]: Starting System Suspend...
May 08 12:44:28 my-labtop systemd-sleep[3419]: in suspend-then-hibernate operations or setups with encrypted home directories.
May 08 12:44:28 my-labtop systemd-sleep[3419]: Performing sleep operation 'suspend'...
May 08 12:44:28 my-labtop kernel: PM: suspend entry (s2idle)
May 08 13:00:48 my-labtop kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 08 13:00:48 my-labtop systemd-sleep[3419]: System returned from sleep operation 'suspend'.
May 08 13:00:48 my-labtop kernel: PM: suspend exit
May 08 13:00:49 my-labtop systemd[1]: systemd-suspend.service: Deactivated successfully.
May 08 13:00:49 my-labtop systemd[1]: Finished System Suspend.
May 08 13:00:49 my-labtop systemd[1]: systemd-suspend.service: Consumed 1.013s CPU time, 3.8M memory peak.
May 08 13:00:49 my-labtop systemd[1]: Reached target Suspend.
May 08 13:00:49 my-labtop systemd[1]: Stopped target Suspend.
May 08 13:00:49 my-labtop systemd-logind[717]: Operation 'suspend' finished.
May 08 13:00:49 my-labtop suspend[3529]: nvidia-resume.service
May 08 13:00:49 my-labtop logger[3529]: <13>May  8 13:00:49 suspend: nvidia-resume.service
May 08 13:04:18 my-labtop systemd-logind[717]: The system will suspend now!
May 08 13:04:18 my-labtop systemd[1]: Starting NVIDIA system suspend actions...
May 08 13:04:18 my-labtop suspend[3610]: nvidia-suspend.service
May 08 13:04:18 my-labtop logger[3610]: <13>May  8 13:04:18 suspend: nvidia-suspend.service
May 08 13:04:21 my-labtop systemd[1]: nvidia-suspend.service: Deactivated successfully.
May 08 13:04:21 my-labtop systemd[1]: Finished NVIDIA system suspend actions.
May 08 13:04:21 my-labtop systemd[1]: nvidia-suspend.service: Consumed 2.067s CPU time, 18.9M memory peak.
May 08 13:04:21 my-labtop systemd[1]: Starting System Suspend...
May 08 13:04:21 my-labtop systemd-sleep[3633]: in suspend-then-hibernate operations or setups with encrypted home directories.
May 08 13:04:21 my-labtop systemd-sleep[3633]: Performing sleep operation 'suspend'...
May 08 13:04:21 my-labtop kernel: PM: suspend entry (s2idle)
May 08 13:15:59 my-labtop kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 08 13:15:59 my-labtop kernel: PM: suspend exit
May 08 13:15:59 my-labtop systemd-sleep[3633]: System returned from sleep operation 'suspend'.
May 08 13:16:00 my-labtop systemd[1]: systemd-suspend.service: Deactivated successfully.
May 08 13:16:00 my-labtop systemd[1]: Finished System Suspend.
May 08 13:16:00 my-labtop systemd[1]: Reached target Suspend.
May 08 13:16:00 my-labtop systemd[1]: Stopped target Suspend.
May 08 13:16:00 my-labtop systemd-logind[717]: Operation 'suspend' finished.
May 08 13:16:00 my-labtop suspend[3676]: nvidia-resume.service
May 08 13:16:00 my-labtop logger[3676]: <13>May  8 13:16:00 suspend: nvidia-resume.service
May 08 13:21:19 my-labtop kwin_wayland_wrapper[3157]: W0000 00:00:1746681679.162531    3160 session_handler.cc:563] server went to suspend mode for 33m51.98415101s

Then there is the kernel panic, happens at 13:48:15, the log is at the top of my post.
These are the details of the three documented kernel panics. I hope I made it clear. I don't know much about linux so if need further information to check I hope you can let me know and I will try to give it.
And thanks for the help!

nemutai · 2025-05-14 10:24:29

It seems that the kernel panic no longer occurs after using this command,

sudo touch /etc/systemd/do-not-udevadm-trigger-on-update

but I will still watch it for a while longer and if the kernel panic doesn't occur again during this time,I will change the status of this issue to solved. Thanks for the above guy!

nemutai · 2025-05-17 04:31:55

So bruh, kernel panic is still there. For some reason I rebooted my labtop many times in a short time, which means there wasn't suspend or update. Kernel panic then appears on one of these many reboots. The culprit is still nvidia-powerd, which is obsessed with that NULL pointer.
Sigh, judging by the activity in this thread, it looks like I'm going to have to disable my nvidia graphics card until I need it and then turn it on temporarily, which, I have to say, basically negates the possibility of me playing games on a linux platform.

Edited: I switched to stable kernel and nvidia-open driver, I'll watch it for a while and if it works I'll switch the status of this thread to SOLVED.

Last edited by nemutai (2025-05-17 05:34:19)

seth · 2025-05-17 06:31:54

https://wiki.archlinux.org/title/CPU_fr … dia-powerd
a) is your system supported at all?
b) why do you think that's mission critical?

disable my nvidia graphics card until I need it and then turn it on temporarily

Are you somehow confusing it with https://wiki.archlinux.org/title/PRIME# … Management ?

nemutai · 2025-05-17 15:42:44

seth wrote:

https://wiki.archlinux.org/title/CPU_fr … dia-powerd
a) is your system supported at all?
b) why do you think that's mission critical?
disable my nvidia graphics card until I need it and then turn it on temporarily
Are you somehow confusing it with https://wiki.archlinux.org/title/PRIME# … Management ?

I appreciate your reply.

a) Before you mentioned it, I didn't know whether my laptop officially supports nvidia-powerd. Honestly, I wasn't even trying to figure that out (though now I know it is supported). I came here simply because I was looking for help with a kernel panic clearly caused by nvidia-powerd, which is conveniently bundled with the NVIDIA driver and quietly starts itself — right before causing a kernel panic. And it seems like I'm the only person on the internet dealing with this issue.

b) I'm not sure what you mean by "mission critical." If you're just asking "Can't you disable nvidia-powerd?", then from my point of view, something that causes a kernel panic shouldn't just be blindly disabled — especially when it's conveniently bundled with the driver and quietly starts itself. (Forgive me for repeating that, but I thought it was worth emphasizing.) That feels like the worst kind of workaround.
That said, now that I know it's optional, I will disable it — but I'll wait until it triggers another panic, just to be sure.

c) I don’t know the difference between nvidia-powerd and RTD3, or whether they’re related at all. If nvidia-powerd hadn’t triggered a kernel panic, I wouldn't even know it existed. And if you hadn’t brought up RTD3, I wouldn't have heard of that either.
By “disable,” I mean something like disabling the driver from loading or switching to integrated graphics mode (my laptop should support that via asusctl, though I haven’t tried it yet).

This turned out a bit wordy, but I hope I conveyed my thoughts clearly.

Last edited by nemutai (2025-05-17 15:56:24)

seth · 2025-05-17 18:31:41

"Can't you disable nvidia-powerd?", then from my point of view, something that causes a kernel panic shouldn't just be blindly disabled

It should especially not be blindly *EN*abled. nvidia-powerd isn't enabled by default and will also not "quietly start itself"

I'm not sure what you mean by "mission critical."

I'm going to have to disable my nvidia graphics card until I need it and then turn it on temporarily, which, I have to say, basically negates the possibility of me playing games on a linux platform

nvidia-powerd isn't relevant to use, control or play games on the nvidia GPU. That's what I meant with "not mission-critical". It's probably nice to have on supported HW - if it works.

I didn't know … I wasn't even trying … if you hadn’t brought up RTD3, I wouldn't have heard of that

So you've not read either the nvidia or the prime wiki but probably followed some likeshareandsubscribe youtuber who probably also told you to blindly enable nivida-powerd?
If you don't know why that's enabled, disable it or at least figure whether your HW is supposed to be supported at all and then whether you want it so badly that you want to figure why it's causing the module to crash w/ a nullptr deref (that's btw. not a kernel panic either) and then probably try to https://wiki.archlinux.org/title/NVIDIA … in_general => https://wiki.archlinux.org/title/NVIDIA … P_firmware (binary driver only, this will not work w/ nvidia-open)

Get used to consult the wiki for the system installation, configuration and first step when facing problems and don't blindly copy paste stuff - not from youtubers, not from blogs and even not from the wiki.

nemutai · 2025-05-18 03:30:41

Thanks for your reply. But I'd like to keep this discussion on topic.

seth wrote:

It should especially not be blindly *EN*abled. nvidia-powerd isn't enabled by default and will also not "quietly start itself"

You seem to insist that I enabled nvidia-powerd myself and that I'm just here wasting everyone's time trying to argue otherwise. *Sigh*

I've already emphasized — multiple times — that nvidia-powerd came bundled with nvidia-dkms, and I never ran anything like sudo systemctl enable nvidia-powerd. It simply started on its own after installation or anytime before kernel panic. I really, truly, and absolutely did not enable it myself.

If you’re convinced it’s disabled by default, then the only thing I can think of is that it might have been enabled by supergfxctl, which I did install to manage GPU modes on my laptop. I’ve set it to “hybrid mode” to ensure both iGPU and dGPU can be used. I don’t know if supergfxctl enables nvidia-powerd — it’s not mentioned anywhere in wiki — but it does work correctly for its purpose.

seth wrote:

So you've not read either the nvidia or the prime wiki but probably followed some likeshareandsubscribe youtuber who probably also told you to blindly enable nivida-powerd?

I can see from your post count that you’re probably an experienced user who's helped many people, including rookies like me. I also understand your lack of patience with certain things. But I’m not here to argue semantics or be accused of blindly following bad advice. Please don’t make assumptions. I did try searching for information but I found basically nothing so came here looking for help (BTW I checked your link and there is no information about nvidia-powerd causing the problem). I don’t run random commands from the internet with root. I try to understand what something does before I do it. So once again — for the fourth time — I never run sudo systemctl enable nvidia-powerd.

I came here to figure out how to fix a kernel panic clearly caused by nvidia-powerd — a component that was installed with nvidia-dkms, and, quietly started itstlf — at least in my own labtop. If that's not clear by now, then... *shrugs*.

Last edited by nemutai (2025-05-18 04:41:10)

seth · 2025-05-18 06:02:31

I don't know where you think I went off topic, but nvidia-powerd is part of nvidia-utils, not nvidia-dkms and since you're interested in redefining reality and not fxing anything, you'll have to tell your stories to somebody else.

pacman -Qo /usr/bin/nvidia-powerd

Good bye.

nemutai · 2025-05-18 07:32:31

seth wrote:

I don't know where you think I went off topic, but nvidia-powerd is part of nvidia-utils, not nvidia-dkms and since you're interested in redefining reality and not fxing anything, you'll have to tell your stories to somebody else.
pacman -Qo /usr/bin/nvidia-powerd
Good bye.

Alright, I'll try to look past the tone and focus on the content of what you're saying.

I’ve stated multiple times that I never run systemctl enable nvidia-powerd or anything similar. You’ve continued to assume otherwise and built your argument on that premise, while disregarding what I actually wrote. If that’s not going off-topic, I’m not sure what is.

At this point, I don’t think there’s anything more to say. Thank you though, at least you're trying to help me. I sincerely hope you have a good weekend. Goodbye.

nemutai · 2025-05-18 09:46:35

I’ve found new evidence that supergfxctl starts nvidia-powerd automatically, confirming my earlier suspicion:

nemutai wrote:

If you’re convinced it’s disabled by default, then the only thing I can think of is that it might have been enabled by supergfxctl, which I did install to manage GPU modes on my laptop. I’ve set it to “hybrid mode” to ensure both iGPU and dGPU can be used. I don’t know if supergfxctl enables nvidia-powerd — it’s not mentioned anywhere in wiki — but it does work correctly for its purpose.

Here is a relevant excerpt from journalctl -u supergfxd | grep "nvidia-powerd":

May 18 16:08:11 my-labtop supergfxd[717]: [DEBUG supergfxctl] Did CommandArgs { inner: ["start", "nvidia-powerd.service"] }

My device (FX507ZM) supports Dynamic Boost, and has 12700h and 3060 labtop. So nvidia-powerd should be supported as well. However, I still don’t understand why nvidia-powerd causes kernel panic. It’s unclear whether the cause lies in the zen kernel, the Nvidia driver, or other magic things.

I’ll continue monitoring the situation and update here if I learn more for future reference.

Last edited by nemutai (2025-05-18 09:52:19)

Arch Linux

#1 2025-05-08 06:50:50

nvidia-powerd caused kernel panic

#2 2025-05-08 07:00:18

Re: nvidia-powerd caused kernel panic

#3 2025-05-08 18:58:16

Re: nvidia-powerd caused kernel panic

#4 2025-05-09 05:21:42

Re: nvidia-powerd caused kernel panic

#5 2025-05-14 10:24:29

Re: nvidia-powerd caused kernel panic

#6 2025-05-17 04:31:55

Re: nvidia-powerd caused kernel panic

#7 2025-05-17 06:31:54

Re: nvidia-powerd caused kernel panic

#8 2025-05-17 15:42:44

Re: nvidia-powerd caused kernel panic

#9 2025-05-17 18:31:41

Re: nvidia-powerd caused kernel panic

#10 2025-05-18 03:30:41

Re: nvidia-powerd caused kernel panic

#11 2025-05-18 06:02:31

Re: nvidia-powerd caused kernel panic

#12 2025-05-18 07:32:31

Re: nvidia-powerd caused kernel panic

#13 2025-05-18 09:46:35

Re: nvidia-powerd caused kernel panic

Board footer