Series 550 freezes laptop

Saltyming · 2024-04-21T06:24:07.371Z

NVIDIA Unified Memory kernel module (/lib/modules/uname -r/kernel/drivers/video/nvidia-uvm.ko); this kernel module provides functionality for sharing memory between the CPU and GPU in CUDA programs. It is generally loaded into the kernel when a CUDA program is started, and is used by the CUDA driver on supported platforms.

I don’t think CUDA related tasks will work after disabling it. NVENC also requires uvm, says ArchWiki.

demensdeum · 2024-04-21T07:42:12.197Z

Yes, but blacklisting it is ok for those who just want to wait until driver fix

demensdeum · 2024-04-21T20:07:12.471Z

I must say that I got laptop freeze again after 12 hours with blacklisted nvidia_uvm, I can help to provide any logs if Nvidia stuff wants

amrits · 2024-04-22T06:44:59.105Z

Hi All,
We are debugging this issue at this moment and will get back to you with more updates and may contact again if needed any additional information.

0xwojak · 2024-04-22T12:26:48.402Z

debuging

Patryqu · 2024-04-22T18:09:21.320Z

I also often have Kernel panics or desktop hanging when clicking on reboot/shutdown or sudo reboot/shutdown . Only systemctl reboot doesn’t hangs.
I have MSI laptop with NVIDIA GeForce RTX 3080, openSUSE Tumbleweed with Kernel 6.8.7, and 550.67 nvidia driver, but I had those hangs also on previous 550.54 nvidia driver and 6.8.x kernel versions.

Apr 22 19:09:16 localhost.localdomain kernel: BUG: kernel NULL pointer dereference, address: 0000000000000049
Apr 22 19:09:16 localhost.localdomain kernel: #PF: supervisor read access in kernel mode
Apr 22 19:09:16 localhost.localdomain kernel: #PF: error_code(0x0000) - not-present page
Apr 22 19:09:16 localhost.localdomain kernel: PGD 0 P4D 0
Apr 22 19:09:16 localhost.localdomain kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Apr 22 19:09:16 localhost.localdomain kernel: CPU: 12 PID: 775 Comm: systemd-journal Tainted: P           OE      6.8.7-1-default #1 openSUSE Tumbleweed c4561c6468a5a7a8147b8a1c044f64b0b0e6fc6c
Apr 22 19:09:16 localhost.localdomain kernel: Hardware name: Micro-Star International Co., Ltd. Vector GP76 12UH/MS-17K4, BIOS E17K4IMS.40C 06/26/2023
Apr 22 19:09:16 localhost.localdomain kernel: RIP: 0010:simple_xattr_get+0x31/0xa0
Apr 22 19:09:16 localhost.localdomain kernel: Code: 00 00 41 56 49 89 ce 41 55 4c 8d 6f 08 41 54 49 89 d4 55 48 89 f5 53 48 89 fb 4c 89 ef e8 67 52 89 00 48 8b 1b 48 85 db 74 1b <48> 8b 7b 18 48 89 ee
e8 b3 79>
Apr 22 19:09:16 localhost.localdomain kernel: RSP: 0018:ffffbd0f03943980 EFLAGS: 00010202
Apr 22 19:09:16 localhost.localdomain kernel: RAX: 0000000000000000 RBX: 0000000000000031 RCX: 0000000000000067
Apr 22 19:09:16 localhost.localdomain kernel: RDX: ffff9f05399f6800 RSI: ffffbd0f03943a50 RDI: ffff9f053aae9810
Apr 22 19:09:16 localhost.localdomain kernel: RBP: ffffbd0f03943a50 R08: ffff9f05399f6800 R09: 0000000000000067
Apr 22 19:09:16 localhost.localdomain kernel: R10: ffffbd0f03943a50 R11: 0000000000000002 R12: ffff9f05399f6800
Apr 22 19:09:16 localhost.localdomain kernel: R13: ffff9f053aae9810 R14: 0000000000000067 R15: ffffbd0f03943a50
Apr 22 19:09:16 localhost.localdomain kernel: FS:  00007f3cb9fcb900(0000) GS:ffff9f0c7fa00000(0000) knlGS:0000000000000000
Apr 22 19:09:16 localhost.localdomain kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 22 19:09:16 localhost.localdomain kernel: CR2: 0000000000000049 CR3: 000000011116e000 CR4: 0000000000f50ef0
Apr 22 19:09:16 localhost.localdomain kernel: PKRU: 55555554
Apr 22 19:09:16 localhost.localdomain kernel: Call Trace:
Apr 22 19:09:16 localhost.localdomain kernel:  <TASK>
Apr 22 19:09:16 localhost.localdomain kernel:  ? __die+0x23/0x70
Apr 22 19:09:16 localhost.localdomain kernel:  ? page_fault_oops+0x14d/0x490
Apr 22 19:09:16 localhost.localdomain kernel:  ? exc_page_fault+0x71/0x160
Apr 22 19:09:16 localhost.localdomain kernel:  ? asm_exc_page_fault+0x26/0x30
Apr 22 19:09:16 localhost.localdomain kernel:  ? simple_xattr_get+0x31/0xa0
Apr 22 19:09:16 localhost.localdomain kernel:  __vfs_getxattr+0x7f/0xb0
Apr 22 19:09:16 localhost.localdomain kernel:  do_getxattr+0xf0/0x180
Apr 22 19:09:16 localhost.localdomain kernel:  getxattr+0x7f/0xc0
Apr 22 19:09:16 localhost.localdomain kernel:  ? __check_object_size+0x25b/0x2c0
Apr 22 19:09:16 localhost.localdomain kernel:  ? strncpy_from_user+0x4f/0x150
Apr 22 19:09:16 localhost.localdomain kernel:  ? user_path_at_empty+0x44/0x60
Apr 22 19:09:16 localhost.localdomain kernel:  path_getxattr+0x6a/0xc0
Apr 22 19:09:16 localhost.localdomain kernel:  do_syscall_64+0x83/0x170
Apr 22 19:09:16 localhost.localdomain kernel:  ? proc_cgroup_show+0x266/0x330
Apr 22 19:09:16 localhost.localdomain kernel:  ? single_release+0x35/0x40
Apr 22 19:09:16 localhost.localdomain kernel:  ? kfree+0x2bd/0x2f0
Apr 22 19:09:16 localhost.localdomain kernel:  ? __x64_sys_close+0x3d/0x80
Apr 22 19:09:16 localhost.localdomain kernel:  ? kmem_cache_free+0x3b7/0x3e0
Apr 22 19:09:16 localhost.localdomain kernel:  ? syscall_exit_to_user_mode+0x83/0x230
Apr 22 19:09:16 localhost.localdomain kernel:  ? do_syscall_64+0x90/0x170
Apr 22 19:09:16 localhost.localdomain kernel:  ? vfs_read+0xac/0x340
Apr 22 19:09:16 localhost.localdomain kernel:  ? simple_read_from_buffer+0x65/0xb0
Apr 22 19:09:16 localhost.localdomain kernel:  ? __seccomp_filter+0x31b/0x4e0
Apr 22 19:09:16 localhost.localdomain kernel:  ? ksys_read+0x67/0xe0
Apr 22 19:09:16 localhost.localdomain kernel:  ? syscall_exit_to_user_mode+0x83/0x230
Apr 22 19:09:16 localhost.localdomain kernel:  ? do_syscall_64+0x90/0x170
Apr 22 19:09:16 localhost.localdomain kernel:  ? __seccomp_filter+0x31b/0x4e0
Apr 22 19:09:16 localhost.localdomain kernel:  ? ksys_read+0x67/0xe0
Apr 22 19:09:16 localhost.localdomain kernel:  ? syscall_exit_to_user_mode+0x83/0x230
Apr 22 19:09:16 localhost.localdomain kernel:  ? do_syscall_64+0x90/0x170
Apr 22 19:09:16 localhost.localdomain kernel:  ? do_syscall_64+0x90/0x170
Apr 22 19:09:16 localhost.localdomain kernel:  ? exc_page_fault+0x71/0x160
Apr 22 19:09:16 localhost.localdomain kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Apr 22 19:09:16 localhost.localdomain kernel: RIP: 0033:0x7f3cb990f43e
Apr 22 19:09:16 localhost.localdomain kernel: Code: 96 2c 01 00 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 49 89 ca b8 c0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73
01 c3 48>
Apr 22 19:09:16 localhost.localdomain kernel: RSP: 002b:00007fff4b8e31a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000c0
Apr 22 19:09:16 localhost.localdomain kernel: RAX: ffffffffffffffda RBX: 0000000000000067 RCX: 00007f3cb990f43e
Apr 22 19:09:16 localhost.localdomain kernel: RDX: 0000562ee844c5e0 RSI: 0000562ee69e1320 RDI: 0000562ee8448c00
Apr 22 19:09:16 localhost.localdomain kernel: RBP: 0000562ee844c5e0 R08: 0000000000000007 R09: 0000000000000005
Apr 22 19:09:16 localhost.localdomain kernel: R10: 0000000000000067 R11: 0000000000000246 R12: 0000562ee8448c00
Apr 22 19:09:16 localhost.localdomain kernel: R13: 0000000000000007 R14: 0000562ee69e1320 R15: 0000000000000000
Apr 22 19:09:16 localhost.localdomain kernel:  </TASK>
Apr 22 19:09:16 localhost.localdomain kernel: Modules linked in: af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat
nf_tables>
Apr 22 19:09:16 localhost.localdomain kernel:  intel_uncore_frequency_common snd_hda_intel x86_pkg_temp_thermal intel_powerclamp snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec coretemp snd_hda_core
processo>
Apr 22 19:09:16 localhost.localdomain kernel:  hid_multitouch hid_generic crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul xhci_pci nvme xhci_pci_renesas ghash_clmulni_intel
xhci_hcd nvme>
Apr 22 19:09:16 localhost.localdomain kernel: CR2: 0000000000000049
Apr 22 19:09:16 localhost.localdomain kernel: ---[ end trace 0000000000000000 ]---

bakabo8 · 2024-04-25T13:13:14.677Z

New Nvidia driver 550.78 released:
Fixed a regression that led to Xid errors when loading the NVIDIA driver on some notebook systems with RTX 4xxx series GPUs

Dont know if its going to fix this issue here.

eric.esteban28 · 2024-04-25T19:12:52.187Z

they haven’t solved it

demensdeum · 2024-04-26T05:28:22.437Z

I will stick to 535.171.04 and kernel 6.8.7, it works great.

rashadgasimli · 2024-04-26T06:09:57.314Z

They haven’t solved it. Nvidia 550.xx drivers cause kernel panic on my laptop with rtx 3050.

amrits · 2024-04-26T07:10:36.152Z

Hi All,
The freeze issue which I observed locally on my setup has a different stack which has been reported here.
I have tried repro since then on couple of systems for few days where I tried updating packages followed by multiple reboots/logouts but not observed freeze issue.

Would appreciate if anyone has reliable repro steps for the freeze issue.
Also, for isolation purpose, can someone please try below steps and confirm if solves the issue.

Add"zswap.enabled=0" and “numa=off” to the kernel parameter
Changed the nvidia to nvidia-open-dkms

jc81 · 2024-04-26T07:46:26.462Z

The nvidia-open-dkms solved for me the random freezes and the system runs stable with them now. But I cannot uses suspend with them. X11 doesn’t come up again. When I try to reboot, systemd says that nvidia-suspence is blocking that.
I am using NixOS, not Arch (because it seems like everyone else in here uses Arch or an Arch-based distro).

jose.hipolito.santos.2001 · 2024-04-26T09:31:27.168Z

Hello @amrits, regarding the freezing i myself cannot tell if its somehow related to the kernel panics too that have been laid out here in this discussion too, my example here just in photo though…, since in my case the system when powering off would at times trigger in panic rendering completely frozen, and so unable to even use REISUB.

Ever since adding

“amdgpu.vm_update_mode=3 amdgpu.dcdebugmask=0x4”

kernel parameters i have not had kernel panics (so far), but i just wanted to ask like, has this been observed too?

balrog86 · 2024-04-26T10:57:50.225Z

as @bakabo8 pointed out, I tried the 550.78 (open) drivers .
Those fixed the issue(s) for me! (4050, gentoo, hwprobe, emerge --info)

What I tested:

Boot with “default” commandline/kernelsettings
nvidia-smi works now. Didn’t work with closed 550.76 drivers, as the module(s) failed to work correctly (didn’t test without uvm, as @demensdeum suggested, as this has drawbacks). Turning on pci debugging showed some errors related to vulkaninfo/eglinfo blocking? (on 550.76 closed) I’d guess this is why nvidia-smi or other applications were stuck. dmesg 550.76-closed at 18:03:45
prime-run valheim max settings, no dlss@1080p (~55 avg fps, no huge drops in starting area) didn’t see any issues in a quick test
nvidia/pci power management seems to finally work again, going to D3COLD when dGPU is not in use. It didn’t work reliable at all on 550.xx yet for me, so I downgraded to “stable” 535.171.04(closed)
suspend also works in combination with acpi_osi=! "acpi_osi=Windows 2015" bootparameter ("Windows 2015" is correct for me, you need to lookup yours). I sadly can’t remember, but either on 550.76-open/closed or 535.171-open the first suspend (with dGPU locked in D0 after resume) succeeded and the second to third suspend resulted in a kernel panic. (for reproducing).

However:

lots of warnings due to nvidia-open 0x0[dot]st/XHek.txt
glxgears has strange output ibb[dot]co/2tKYRgy
will do some more testing/benchmarking, but I will probably downgrade to 535.xx-closed again for now.

edit: Not fixed for nvidia-550.78-closed.

What works on closed:

Boot->startx->nvidia-smi
I’m not sure about initial pci power state.

What didn’t work on closed:

starting valheim as before(gets stuck), starting nvidia-smi after this again(now stuck, not responding, ctrl+c not working) dmesg 550.78-closed (similar to above 550.76 dmesg) - I guess you can reproduce it with other directx/vulkan/3d applications/games that utilize the dGPU by prime-run
/sys/bus/pci/devices/0000:01:00.0/power/runtime_status remains active
edit: shutdown. System was stuck on ending user processes. SysRq r+e+i didn’t solve it either. Had to SysRq s+u+b in order to reboot forcefully. edit2: SysRq + o didn’t shutdown the system, I had to press power key for 10 sec.

edit: numa=off didn’t change anything as it seems (compared to above 550.78-closed run). bpa[dot]st/MGCA

ps.: nvidia-smi does not show “X” as application anymore, not sure if this is 550.xx, or xorg related.

kodatarule · 2024-04-26T14:15:11.469Z

In my use case on my Lenovo Legion 5 I needed the nvidia-open-dkms(as I use custom kernel) and “amdgpu.vm_update_mode=3 amdgpu.dcdebugmask=0x4” in order to resolve the problems entirely.

balrog86 · 2024-04-26T16:03:36.466Z

Not sure if we do discuss several different but similar 550.xx related 3xxx 4xxx laptop issues here, as I’m not experiencing the same random freeze as in initial post. Gentoo irc/devs linked me to this thread and said it’s related.

For completion to my previous report I added all of the above amdgpu.vm_update_mode=3 amdgpu.dcdebugmask=0x4 zswap.enabled=0 numa=off , but they didn’t change my issues on 550.78-closed or 550.78-open.

jose.hipolito.santos.2001 · 2024-04-26T16:49:05.673Z

Makes sense, mb there are also issues from mesa smh with dualgpu systems?
But anyhow we need to get the facts straight to at least help others in the future too xp.

edit: forgot to add, i also am just using 550-76 dkms now, endeavourOS has this package that does things for you and so they still include the dkms and i just sit with it xp.

Saltyming · 2024-04-27T06:52:19.195Z

I don’t think amdgpu.vm_update_mode=3 amdgpu.dcdebugmask=0x4 is related to series 550. That is an amdgpu bug that has been around more than a year, before nvidia 550 series debuted. But I will test the option if it actually matters.

EDIT1: nvidia proprietary driver 550.78 crashed with zswap and numa enabled, was doing some CUDA tasks.

EDIT2: It crashed with zswap disabled. I deleted nvidia-open section cause I only tested it for a few minutes.

mario156090 · 2024-04-28T23:30:17.246Z

You need to try install packages that request a hardware reload system manager configuration, so, you can test with supergfxctl.

amrits · 2024-04-29T08:03:38.455Z

@mario156090
I compiled package supergfxctl and used the utility to switch between Hybrid and Integrated mode multiple times but still not observe freeze issue.
How frequent it was for you to duplicate issue?