Nvidia driver causes unhandled page fault on Thinkpad P53

ryuu_risto · 2025-12-14 16:52:04

Issue:
Whenever I have Visual Studio Code open in order to develop software, at a random point my laptop suddenly seemingly completely hangs.
The only solution I found to this is to hard reset the device, as I can't switch my terminal with CTRL+F#.

On next boot I can use journalctl -b-1 to check the kernel log, and find the following:

Dec 14 17:24:20 ryuu-laptop kernel: BUG: unable to handle page fault for address: 0000000400000010
Dec 14 17:24:20 ryuu-laptop kernel: #PF: supervisor read access in kernel mode
Dec 14 17:24:20 ryuu-laptop kernel: #PF: error_code(0x0000) - not-present page
Dec 14 17:24:20 ryuu-laptop kernel: PGD 0 P4D 0 
Dec 14 17:24:20 ryuu-laptop kernel: Oops: Oops: 0000 [#1] SMP NOPTI
Dec 14 17:24:20 ryuu-laptop kernel: CPU: 8 UID: 0 PID: 6017 Comm: kworker/8:3 Tainted: P           OE       6.17.9-arch1-1 #1 PREEMPT(full)  71adf6020e7d04ea315feaf360c679be0fb5cb04
Dec 14 17:24:20 ryuu-laptop kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Dec 14 17:24:20 ryuu-laptop kernel: Hardware name: LENOVO 20QN0053MX/20QN0053MX, BIOS N2NET64W (1.49 ) 08/18/2025
Dec 14 17:24:20 ryuu-laptop kernel: Workqueue: kacpi_notify acpi_os_execute_deferred
Dec 14 17:24:20 ryuu-laptop kernel: RIP: 0010:_nv049438rm+0x2a/0x80 [nvidia]
Dec 14 17:24:20 ryuu-laptop kernel: Code: 66 0f 1f 00 41 55 49 89 f5 41 54 53 48 83 ed 10 89 d3 89 de 48 8d 55 0f c6 45 0f 00 e8 2f ee 31 ff 80 7d 0f 00 41 89 c4 75 11 <41> 39 5d 10 76 20 49 8b 45 00 c1 eb 02 44 8b 24 98 5b 44 89 e0 41
Dec 14 17:24:20 ryuu-laptop kernel: RSP: 0018:ffffd461d43afae0 EFLAGS: 00010246
Dec 14 17:24:20 ryuu-laptop kernel: RAX: 0000000000000000 RBX: 000000000010a800 RCX: 000000000010a800
Dec 14 17:24:20 ryuu-laptop kernel: RDX: ffff8c8fefcf2e4f RSI: ffff8c8fecba4008 RDI: ffff8c8fefa48008
Dec 14 17:24:20 ryuu-laptop kernel: RBP: ffff8c8fefcf2e40 R08: 0000000000000020 R09: 0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: RDX: ffff8c8fefcf2e4f RSI: ffff8c8fecba4008 RDI: ffff8c8fefa48008
Dec 14 17:24:20 ryuu-laptop kernel: RBP: ffff8c8fefcf2e40 R08: 0000000000000020 R09: 0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: R10: 000000000010a800 R11: fffff632c5903400 R12: 0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: R13: 0000000400000000 R14: 0000000000000000 R15: 0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: FS:  0000000000000000(0000) GS:ffff8c9730309000(0000) knlGS:0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 14 17:24:20 ryuu-laptop kernel: CR2: 0000000400000010 CR3: 00000007a9824006 CR4: 00000000003726f0
Dec 14 17:24:20 ryuu-laptop kernel: Call Trace:
Dec 14 17:24:20 ryuu-laptop kernel:  <TASK>
Dec 14 17:24:20 ryuu-laptop kernel:  _nv015867rm+0x10f/0x170 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv028382rm+0x61/0xf0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv013394rm+0x20/0xb0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv055242rm+0x52/0xa0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  ? _nv052281rm+0x70/0x70 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv052457rm+0x38/0x1f0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv052263rm+0x1d5/0x8fc [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  ? _nv052263rm+0xf2/0x8fc [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv052283rm+0x140/0x400 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  ? _nv052283rm+0x102/0x400 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv042746rm+0x79/0xb0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  ? _nv042746rm+0x3a/0xb0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv042774rm+0xbe/0x160 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv042681rm+0x36/0x70 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv016353rm+0x1ae/0x1c0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  _nv059287rm+0x98/0x1d0 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  rm_acpi_notify+0x1e3/0x280 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  ? acpi_os_signal_semaphore+0x82/0xb0
Dec 14 17:24:20 ryuu-laptop kernel:  acpi_ev_notify_dispatch+0x4e/0x70
Dec 14 17:24:20 ryuu-laptop kernel:  acpi_os_execute_deferred+0x1a/0x30
Dec 14 17:24:20 ryuu-laptop kernel:  process_one_work+0x193/0x350
Dec 14 17:24:20 ryuu-laptop kernel:  worker_thread+0x2d7/0x410
Dec 14 17:24:20 ryuu-laptop kernel:  ? __pfx_worker_thread+0x10/0x10
Dec 14 17:24:20 ryuu-laptop kernel:  kthread+0xf9/0x240
Dec 14 17:24:20 ryuu-laptop kernel:  ? __pfx_kthread+0x10/0x10
Dec 14 17:24:20 ryuu-laptop kernel:  ? __pfx_kthread+0x10/0x10
Dec 14 17:24:20 ryuu-laptop kernel:  ret_from_fork+0x1c1/0x1f0
Dec 14 17:24:20 ryuu-laptop kernel:  ? __pfx_kthread+0x10/0x10
Dec 14 17:24:20 ryuu-laptop kernel:  ret_from_fork_asm+0x1a/0x30
Dec 14 17:24:20 ryuu-laptop kernel:  </TASK>
Dec 14 17:24:20 ryuu-laptop kernel: Modules linked in: cmac ccm snd_seq_dummy snd_hrtimer snd_seq bnep snd_sof_pci_intel_cnl intel_uncore_frequency intel_uncore_frequency_common snd_sof_intel_hda_generic intel_pmc_core_pltdrv intel_pmc_co>
Dec 14 17:24:20 ryuu-laptop kernel:  snd_soc_avs aesni_intel mac80211 uvcvideo rapl snd_soc_hda_codec snd_hda_ext_core intel_cstate snd_hda_intel videobuf2_vmalloc snd_usb_audio processor_thermal_device_pci_legacy libarc4 uvc snd_hda_code>
Dec 14 17:24:20 ryuu-laptop kernel:  intel_soc_dts_iosf i2c_nvidia_gpu drm_ttm_helper snd_timer mc thunderbolt int340x_thermal_zone pinctrl_cannonlake acpi_thermal_rel acpi_pad wacom mmc_block rpmb_core mac_hid nvidia(POE) i2c_dev crypto_>
Dec 14 17:24:20 ryuu-laptop kernel: CR2: 0000000400000010
Dec 14 17:24:20 ryuu-laptop kernel: ---[ end trace 0000000000000000 ]---
Dec 14 17:24:20 ryuu-laptop kernel: RIP: 0010:_nv049438rm+0x2a/0x80 [nvidia]
Dec 14 17:24:20 ryuu-laptop kernel: Code: 66 0f 1f 00 41 55 49 89 f5 41 54 53 48 83 ed 10 89 d3 89 de 48 8d 55 0f c6 45 0f 00 e8 2f ee 31 ff 80 7d 0f 00 41 89 c4 75 11 <41> 39 5d 10 76 20 49 8b 45 00 c1 eb 02 44 8b 24 98 5b 44 89 e0 41
Dec 14 17:24:20 ryuu-laptop kernel: RSP: 0018:ffffd461d43afae0 EFLAGS: 00010246
Dec 14 17:24:20 ryuu-laptop kernel: RAX: 0000000000000000 RBX: 000000000010a800 RCX: 000000000010a800
Dec 14 17:24:20 ryuu-laptop kernel: RDX: ffff8c8fefcf2e4f RSI: ffff8c8fecba4008 RDI: ffff8c8fefa48008
Dec 14 17:24:20 ryuu-laptop kernel: RBP: ffff8c8fefcf2e40 R08: 0000000000000020 R09: 0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: R10: 000000000010a800 R11: fffff632c5903400 R12: 0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: R13: 0000000400000000 R14: 0000000000000000 R15: 0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: FS:  0000000000000000(0000) GS:ffff8c9730309000(0000) knlGS:0000000000000000
Dec 14 17:24:20 ryuu-laptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 14 17:24:20 ryuu-laptop kernel: CR2: 0000000400000010 CR3: 00000007a9824006 CR4: 00000000003726f0

This issue so far has only happened when I have VSCode open.

Hardware:
Lenovo Thinkpad P53
Intel i7-9850H (12) @ 4.600GHz
Intel CoffeeLake-H GT2 [UHD Graphics 630]
NVIDIA Quadro RTX 3000 Mobile / Max-Q

Setup:
Kernel 6.17.9-arch1-1
Plasma 6.5.4 with kwin
nvidia 580.105.08-4

I'm using the proprietary nvidia driver to be able to use GPU power saving under a PRIME setup.

Scimmia · 2025-12-14 16:58:03

That's a Turing card, have you tried nvidia-open instead? Yes, I know about the power issue, this is for testing.

Last edited by Scimmia (2025-12-14 16:58:52)

ryuu_risto · 2025-12-14 17:10:12

Scimmia wrote:

That's a Turing card, have you tried nvidia-open instead? Yes, I know about the power issue, this is for testing.

I have replaced the driver now and will report whether the crash happens again.

ryuu_risto · 2025-12-15 00:24:40

It appears that nvidia-open does not have this issue.

I cannot use it however, as it sometimes boots me to a black screen, which I have to resolve by going to a different TTY and restarting my laptop until it happens to work, in addition to lack of power saving.

seth · 2025-12-15 08:39:41

I'm using the proprietary nvidia driver to be able to use GPU power saving under a PRIME setup.

Dec 14 17:24:20 ryuu-laptop kernel:  rm_acpi_notify+0x1e3/0x280 [nvidia 7600fe72813d9d917858a4eb57d2f0dd025eec3c]
Dec 14 17:24:20 ryuu-laptop kernel:  ? acpi_os_signal_semaphore+0x82/0xb0
Dec 14 17:24:20 ryuu-laptop kernel:  acpi_ev_notify_dispatch+0x4e/0x70
Dec 14 17:24:20 ryuu-laptop kernel:  acpi_os_execute_deferred+0x1a/0x30

And can you reproduce that w/ disabling RTD3?
Try to disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware

ryuu_risto · 2025-12-16 12:00:28

seth wrote:

And can you reproduce that w/ disabling RTD3?
Try to disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware

The GSP firmware is in fact already disabled, as that is one of the steps necessary to enable power management, which I use to preserve battery.
My modprobe config for nvidia module is as follows:

nvidia-pm.conf
options nvidia "NVreg_DynamicPowerManagement=0x02"

nvidia-sleep.conf
options nvidia NVreg_PreserveVideoMemoryAllocations=0

nvidia.conf
options nvidia "NVreg_EnableGpuFirmware=0"

seth · 2025-12-16 15:04:20

that is one of the steps necessary to enable power management

Not strictly, but it is or was a common fissure.
What happens if you conversely enable the GSP (and also test to disable RTD3 because it looks like the crash is coming from there)

Sanity check:
You do a have nvidia-persistenced.service enabled? Is it running

systemctl status nvidia-persistenced.service

Arch Linux

#1 2025-12-14 16:52:04

Nvidia driver causes unhandled page fault on Thinkpad P53

#2 2025-12-14 16:58:03

Re: Nvidia driver causes unhandled page fault on Thinkpad P53

#3 2025-12-14 17:10:12

Re: Nvidia driver causes unhandled page fault on Thinkpad P53

#4 2025-12-15 00:24:40

Re: Nvidia driver causes unhandled page fault on Thinkpad P53

#5 2025-12-15 08:39:41

Re: Nvidia driver causes unhandled page fault on Thinkpad P53

#6 2025-12-16 12:00:28

Re: Nvidia driver causes unhandled page fault on Thinkpad P53

#7 2025-12-16 15:04:20

Re: Nvidia driver causes unhandled page fault on Thinkpad P53

Board footer