I’m experiencing a kernel oops from the NVIDIA driver:
[ 18.392907] BUG: unable to handle page fault for address: 00000000000016c0
[ 18.392911] #PF: supervisor read access in kernel mode
[ 18.392912] #PF: error_code(0x0000) - not-present page
[ 18.392913] PGD 0 P4D 0
[ 18.392915] Oops: 0000 [#1] PREEMPT SMP PTI
[ 18.392917] CPU: 5 PID: 200 Comm: nvidia-modeset/ Tainted: P OE 6.0.2-arch1-1 #1 50c0f0880a1bf780734fcafd72b58c22e0d25b99
[ 18.392920] Hardware name: ASUS All Series/Z97-PRO(Wi-Fi ac), BIOS 2702 10/27/2015
[ 18.392920] RIP: 0010:_nv016988rm+0x177/0x2b0 [nvidia]
This is occurring immediately after boot when the SDDM login prompt shows and causes the display to freeze, though remote access via ssh is still possible.
This issue first started occurring when I added 2x Dell U2723QE 4k monitors to my system, however it is not occurring on ever boot. With all four screens attached it happens nearly every time, by removing the LG TV it
Distribution: Arch
nvidia-bug-report.log.gz (190.7 KB)
generix
October 19, 2022, 10:13am
2
Looks like Dell provides a firmware update for their U2723QE, did you already try to apply it?
I had not tried that, but have now updated both monitors to the new firmware, and it’s still experiencing the same issue.
i am experiencing the same on a Lenovo Thinkpad with 2 LG 4k monitors connected, it does not happen always as already stated, once every few boot attempts
in my case i have a NVIDIA Corporation TU117GLM [T1200 Laptop GPU] (rev a1)
ott 21 17:34:00 amarok kernel: BUG: unable to handle page fault for address: 00000000000016c0
ott 21 17:34:00 amarok kernel: #PF: supervisor read access in kernel mode
ott 21 17:34:00 amarok kernel: #PF: error_code(0x0000) - not-present page
ott 21 17:34:00 amarok kernel: PGD 1583c2067 P4D 1583c2067 PUD 0
ott 21 17:34:00 amarok kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
ott 21 17:34:00 amarok kernel: CPU: 5 PID: 550 Comm: nvidia-modeset/ Tainted: P OE 6.0.2-arch1-1 #1 50c0f0880a1bf780734fcafd72b58c22e0d25b99
ott 21 17:34:00 amarok kernel: Hardware name: LENOVO 20YQ0016FR/20YQ0016FR, BIOS N37ET42W (1.23 ) 08/31/2022
ott 21 17:34:00 amarok kernel: RIP: 0010:_nv016988rm+0x177/0x2b0 [nvidia]
ott 21 17:34:00 amarok kernel: Code: b5 4c 06 00 00 4c 89 e7 e8 e6 47 fc ff 48 89 c7 48 c7 c6 60 15 f5 c3 e8 37 91 56 00 41 83 bf c4 16 00 00 02 0f 84 10 01 00 00 <44> 8b>
ott 21 17:34:00 amarok kernel: RSP: 0018:ffffb43140f93be0 EFLAGS: 00010293
ott 21 17:34:00 amarok kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000006
ott 21 17:34:00 amarok kernel: RDX: 0000000000000007 RSI: 0000000000272cdd RDI: 0000000000000000
ott 21 17:34:00 amarok kernel: RBP: ffff9588894f5ba0 R08: ffffffffc3e96280 R09: ffff958863ff96b8
ott 21 17:34:00 amarok kernel: R10: 0000000000001368 R11: 0000000000000001 R12: ffff95884aea0008
ott 21 17:34:00 amarok kernel: R13: ffff95886242c008 R14: ffff958863ff8010 R15: ffff958863ff8008
ott 21 17:34:00 amarok kernel: FS: 0000000000000000(0000) GS:ffff95975fb40000(0000) knlGS:0000000000000000
ott 21 17:34:00 amarok kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
ott 21 17:34:00 amarok kernel: CR2: 00000000000016c0 CR3: 000000011c8b6001 CR4: 0000000000770ee0
ott 21 17:34:00 amarok kernel: PKRU: 55555554
ott 21 17:34:00 amarok kernel: Call Trace:
ott 21 17:34:00 amarok kernel: <TASK>
ott 21 17:34:00 amarok kernel: _nv016894rm+0x47/0xf0 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv018885rm+0xe0e/0x1780 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv037977rm+0x172/0x180 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv018740rm+0xd8/0x170 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv039752rm+0x256/0x2b0 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv012274rm+0x4c3/0x5b0 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv038118rm+0x53/0xb0 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv011025rm+0x50/0xa0 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: _nv011024rm+0x46/0x50 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: ? _nv011024rm+0x2f/0x50 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: rm_kernel_rmapi_op+0x141/0x190 [nvidia 50966e709ce4b441733617602348e211d5c5e904]
ott 21 17:34:00 amarok kernel: nvkms_call_rm+0x4c/0x80 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: _nv002545kms+0x51/0x60 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: _nv001220kms+0x124/0x3a0 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: _nv001495kms+0xb4/0xc0 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: _nv001590kms+0x1f/0x40 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: nvkms_kthread_q_callback+0x9c/0x100 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: _main_loop+0x90/0x150 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset adfc2eb22cf5d5632e7956c861838ed993d8d904]
ott 21 17:34:00 amarok kernel: kthread+0xdb/0x110
ott 21 17:34:00 amarok kernel: ? kthread_complete_and_exit+0x20/0x20
ott 21 17:34:00 amarok kernel: ret_from_fork+0x1f/0x30
ott 21 17:34:00 amarok kernel: </TASK>
ott 21 17:34:00 amarok kernel: Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_>
ott 21 17:34:00 amarok kernel: snd_soc_acpi videobuf2_v4l2 kvm soundwire_bus videobuf2_common snd_soc_core irqbypass mei_hdcp mei_pxp crct10dif_pclmul videodev spi_nor s>
ott 21 17:34:00 amarok kernel: platform_profile rfkill tpm_tis snd tpm_tis_core int3403_thermal int340x_thermal_zone tpm soundcore int3400_thermal video intel_hid acpi_t>
ott 21 17:34:00 amarok kernel: Unloaded tainted modules: pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq()>
ott 21 17:34:00 amarok kernel: acpi_cpufreq():1 fjes():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 fjes():1 acpi_cpufreq():1 fjes():1 pcc_cpufreq():1 acpi_cpufreq>
ott 21 17:34:00 amarok kernel: CR2: 00000000000016c0
ott 21 17:34:00 amarok kernel: ---[ end trace 0000000000000000 ]---
ott 21 17:34:00 amarok kernel: RIP: 0010:_nv016988rm+0x177/0x2b0 [nvidia]
ott 21 17:34:00 amarok kernel: Code: b5 4c 06 00 00 4c 89 e7 e8 e6 47 fc ff 48 89 c7 48 c7 c6 60 15 f5 c3 e8 37 91 56 00 41 83 bf c4 16 00 00 02 0f 84 10 01 00 00 <44> 8b>
ott 21 17:34:00 amarok kernel: RSP: 0018:ffffb43140f93be0 EFLAGS: 00010293
ott 21 17:34:00 amarok kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000006
ott 21 17:34:00 amarok kernel: RDX: 0000000000000007 RSI: 0000000000272cdd RDI: 0000000000000000
ott 21 17:34:00 amarok kernel: RBP: ffff9588894f5ba0 R08: ffffffffc3e96280 R09: ffff958863ff96b8
ott 21 17:34:00 amarok kernel: R10: 0000000000001368 R11: 0000000000000001 R12: ffff95884aea0008
ott 21 17:34:00 amarok kernel: R13: ffff95886242c008 R14: ffff958863ff8010 R15: ffff958863ff8008
ott 21 17:34:00 amarok kernel: FS: 0000000000000000(0000) GS:ffff95975fb40000(0000) knlGS:0000000000000000
ott 21 17:34:00 amarok kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
ott 21 17:34:00 amarok kernel: CR2: 00000000000016c0 CR3: 000000011c8b6001 CR4: 0000000000770ee0
ott 21 17:34:00 amarok kernel: PKRU: 55555554
I’ve done some investigation to find what combination of monitors is triggering this kernel oops.
The issue only occurs when the boot monitor (i.e. the monitor that UEFI/BIOS and the grub loader is displayed on) is one of the dell displays connected via DisplayPort, and another monitor is connected via HDMI.
I have tried every combination of two monitors of DisplayPort and HDMI screen including using one of the dell monitors as the HDMI device and the other as DisplayPort with the following result:
One Monitor connected via DisplayPort as boot display, second monitor connected via DisplayPort - No issue. Issue occurs. No Issue No issue
Unfortunately I do not have any other DisplayPort monitors to check if this is unique to the Dell monitors.