Select Proton games randomly freeze at startup on systems using Qtile(X11). Typically happens at the stage of company logos being shown. The image freezes, but the sound can still be heard. With some games, can also occur during shader compilation. Issue first spotted after first update from 555 to 560. Issue can be somewhat worked around by launching the game via gamescope, but it is still inconsistent and can still freeze, albeit less.
How to replicate: install Arch Linux and Qtile, install Nvidia drivers according to the archwiki, install Steam, install and run something like GTA V. Issue present on both barebones mainline Arch configurations and distros such as Arco Linux Qtile and Garuda Qtile.
Some of the games used to test the issue: GTA V, Hardspace: Shipbreaker, Lethal Company, all of which worked fine on 555 and prior.
Thank you for the answer, Iāll look on how to disable fbdev .
EDIT: I did disable fbdev, it gives me a black screen right at boot, had to set it back on.
kwin_wayland_drm: Pageflip timed out! This is a kernel bug
It seems specific to a specific kernelās interaction with specific versions of Plasma. GPU didnāt seem to matter as a lot of reports were with AMD and Intel GPUs. I donāt have any experience with Nobara but if it has the option available you could try a different kernel.
I donāt know how outdated/up-to-date Nobaraās Plasma version is. Current stable on Arch is 6.2.3, can find it with kinfo . Sorry I canāt be of more help.
Nothing to be sorry for, actually I thank you for the effort.
Tried 3 older kernels, also updated today to 6.11.9, there is the kinfo:
Operating System: Nobara Linux 40
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.7.2
Kernel Version: 6.11.9-200.fsync.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 Ć AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Same here, Nioh 2 is a great game, I wanted to replay it and I had to revert back to 550 drivers since it would just freeze and crash on 565 (and 560 and 555)
linux 6.12.1 for nvidia-565
linux-lts 6.6.63 for nvidia-550
I wouldāve used 6.12.1 with 550 but the dkms install just crashes, I will also include the logs from that
sudo dkms install --no-depmod nvidia/550.90.07 -k 6.12.1-arch1-1
I had kernel 6.11.9 before this, and the dkms package for 550 installed correctly, so itās a new problem with 6.12
I have a bunch of other random issues with 565, such as KDE wayland just flickering all over the place, and KDE X11 just refuses to wake from sleep
Iām gonna stay on nvidia-550 and the lts kernel for now, since itās by far the most stable setup
Hereās both the nvidia logs and proton logs for 565 and 550
nvidia-bug-report-550.log.gz (971.1 KB)
nvidia-bug-report-565.log.gz (1014.5 KB)
steam-1325200-nvidia-550.tar.gz (1.0 MB)
steam-1325200-nvidia-565.tar.gz (999.1 KB)
nvidia-dkms-error-make.tar.gz (13.2 KB)
I donāt get crashesā¦ only screen freezes (switching between TTY terminals itās usually enough), It would be nice to know when next drivers version gets released but I see no news.
Hi @Wahoo123
We have already tracked this issue via bug ID [4825128] but unfortunately I have been not able to duplicate it locally.
Could you please confirm if you have done any specific game or display settings.
Hi @amrits
Iāll give you as much info as I can:
- The game doesnāt freeze in the menus, you have to start a mission and run around for a bit (it can sometimes take a few minutes).
- It freezes much faster if you set the game at 120 fps instead of 30 or 60 in the graphics settings (it usually takes less than a minute on my setup)
- Switching from fullscreen to borderless to windowed mode still freezes
- Switching from High/Low graphics settings doesnāt seem to affect anything
- Iām using i3 inside of KDE X11 (replacing kwin), but Iāve tested and the same thing happens with just i3 on its own
- Any kind of wayland session is generally extremely unstable on my machine so I havenāt tested that
- nvidia-drm.modeset=1 and fbdev=1 (Iāve also tested with fbdev=0 and the same freeze happens)
- Iāve tested some custom command prefixes in steam, such as
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%but nothing seems to make any difference - I tried
gamemoderun %command% - I tested with multiple different versions of Proton (Proton GE, Experimental, 9.0, 8.0, 7.0) and it freezes all the same
- I tested different setups in
nvidia-settings(running my monitor at 60Hz instead of 240Hz, turning on/off vsync), no difference - if I run
sudo dmesg | grep -i nvidiaI get this error:[drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Failed to grab modeset ownership, but I also see this error with the 550 driver and the game runs fine - Iām using an RTX 2070 Super from EVGA plugged into display port (I havenāt tried switching to HDMI but I doubt that would make a difference)
GRUB_CMDLINE_LINUX_DEFAULT="udev.log_priority=3 acpi_enforce_resources=lax amd_pstate=guided"- Iām pretty sure I didnāt change anything in my BIOS settings
I canāt really think of anything else
Hereās my full hardware info in case itās relevant (itās showing the 550 drivers because I downgraded)
Kernel: 6.6.63-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-linux-lts
root=UUID=fc8f6751-36f9-4d69-85bc-82fa28fa76d3 rw udev.log_priority=3
acpi_enforce_resources=lax amd_pstate=guided
Desktop: KDE Plasma v: 6.2.3 tk: Qt v: N/A info: frameworks v: 6.8.0 wm: i3
v: 4.24 vt: 2 dm: SDDM Distro: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 5003 date: 10/07/2023
CPU:
Info: model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen 2 gen: 2
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
model-id: 0x71 (113) stepping: 0 microcode: 0x8701030
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3595 min/max: 550/4560 boost: enabled scaling:
driver: amd-pstate governor: schedutil cores: 1: 3595 2: 3595 3: 3595 4: 3595
5: 3595 6: 3595 7: 3595 8: 3595 9: 3595 10: 3595 11: 3595 12: 3595 13: 3595
14: 3595 15: 3595 16: 3595 bogomips: 124863
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
protection
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: eVga.com.
driver: nvidia v: 550.90.07 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-09; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: none off: DP-2 empty: DP-1, DP-3, HDMI-A-1, Unknown-2
bus-ID: 08:00.0 chip-ID: 10de:1e84 class-ID: 0300
Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
compositor: Picom v: 12.5 driver: X: loaded: nvidia
gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.87x11.85")
s-diag: 610mm (24")
Monitor-1: DP-2 res: 1920x1080 dpi: 93 size: 527x296mm (20.75x11.65")
diag: 604mm (23.8") modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast surfaceless: drv: nvidia x11: drv: nvidia
inactive: gbm,wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.90.07
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2070
SUPER/PCIe/SSE2 memory: 7.81 GiB
API: Vulkan v: 1.3.295 layers: 10 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2070 SUPER driver: nvidia v: 550.90.07 device-ID: 10de:1e84
surfaces: xcb,xlib
Audio:
Device-1: NVIDIA TU104 HD Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.1
chip-ID: 10de:10f8 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.6.63-1-lts status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: wg0-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
Info: services: NetworkManager, sshd, systemd-timesyncd
Drives:
Local Storage: total: 953.87 GiB used: 824.34 GiB (86.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW010T8
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 002C temp: 39.9 C scheme: GPT
Partition:
ID-1: / raw-size: 940.27 GiB size: 924.44 GiB (98.32%)
used: 824.24 GiB (89.2%) fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 99 MiB size: 95 MiB (95.96%)
used: 95 MiB (100.0%) fs: vfat dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 12.97 GiB used: 12 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p6 maj-min: 259:5
Sensors:
System Temperatures: cpu: 39.5 C mobo: 35.0 C gpu: nvidia temp: 47 C
Fan Speeds (rpm): fan-1: 892 fan-2: 1220 fan-3: 709 fan-4: 878 fan-5: 2528
fan-6: 1732 fan-7: 0 gpu: nvidia fan: 0%
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 5.31 GiB (17.0%)
Processes: 401 Power: uptime: 13h 51m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 1 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,upowerd
Init: systemd v: 256 default: graphical tool: systemctl
Packages: 1699 pm: pacman pkgs: 1672 libs: 446 tools: yay pm: flatpak
pkgs: 27 Compilers: gcc: 14.2.1 Shell: fish v: 3.7.1 running-in: alacritty
inxi: 3.3.36There is an issue being tracked for gamescope similar to the freezing mentioned here.
Setting VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_wait seems to fix the issue, at least for VKD3D/DX12 games.
New issue occuring since kernel 6.12 release, with both the open and closed drivers. I use fbdev disabled due to this issue I mentioned previously: NVidia fbdev does not use correct screen resolution / primary monitor on multi monitor setups
Using fbdev disabled causes an extra card to now show in /dev/dri, here is an example:
you can see card0 is now correlated to a āsimple framebufferā card, which takes priority over card1 which is my discrete gpu rtx 3070.
Having this card0 here causes a few problems, one being that some compositors wonāt launch, and others will be forced software rendering (hyprland for instance)
I can get around the issue on hyprland by using this environment variable : env = AQ_DRM_DEVICES,/dev/dri/card1
this asks aquamarine (a backend for hyprland) to use card1 instead of the default card0, allowing my compositor and gpu to work correctly again.
This could be solved by fixing my original issue linked above, then I could use fbdev freely and not come across this issue.
Are you on Arch? If so, the patch to disable the simpledrm device was dropped for kernel 6.12.
I filed an issue on Arch GitLab, and included a couple of workarounds for now.
Hello @amrits. Were you able to replicate my Qtile-specific issue? Over here 565 release feedback & discussion - #248 by ashrynne
Display modes above 2560x1440p@120hz with HDR enabled cause flickering/corruption within gamescope-session This is still an issue and we have heard no word yet on a fix
WARNING: the video clip has strobing lights
Yes, Gamescope-session (or gamescope -e -f -h 2160 -w 7680 -r 120 --hdr-enabled --mangoapp -- steam -steamdeck -steamos3 -steampal -gamepadui from TTY) still has massive flickering whenever HDR is enabled. It works fine up until the point of enabling HDR, but after that point it turns into the video above.
Another report from a different user showing the same thing (in their videos): [Nvidia] Black screen when HDR option is enabled Ā· Issue #1593 Ā· ValveSoftware/gamescope Ā· GitHub
Thanks for this info, I see now that you can blacklist it when building the kernel, however Iām using prebuilt kernels from arch repo and I donāt want to build my own, so I will continue to use my workaround for now as it works for my main compositor of choice (Hyprland)
My GPU with GSP enabled (open modules) just fell off again:
NVRM: GPU at PCI:0000:01:00: GPU-1dfdd8a3-609f-ab69-f862-db0ee121b8ce
[ 37.081161] NVRM: GPU Board Serial Number: 0
[ 37.081163] NVRM: Xid (PCI:0000:01:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
[ 37.081172] NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.
[ 37.081173] NVRM: GPU 0000:01:00.0: GPU serial number is 0.
[ 37.081193] NVRM: kgspRcAndNotifyAllChannels_IMPL: RC all channels for critical error 79.
[ 37.081214] NVRM: _threadNodeCheckTimeout: API_GPU_ATTACHED_SANITY_CHECK failed!
[ 37.081247] NVRM: _threadNodeCheckTimeout: API_GPU_ATTACHED_SANITY_CHECK failed!
[ 37.081258] NVRM: _threadNodeCheckTimeout: API_GPU_ATTACHED_SANITY_CHECK failed!
[ 37.081543] NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 78!
[ 37.081551] NVRM: nvCheckOkFailedNoLog: Check failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from nvdEngineDumpCallbackHelper(pGpu, pPrbEnc, pNvDumpState, pEngineCallback) @ nv_debug_dump.c:274
[ 37.081580] NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 78!
[ 37.081583] NVRM: nvCheckOkFailedNoLog: Check failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from nvdEngineDumpCallbackHelper(pGpu, pPrbEnc, pNvDumpState, pEngineCallback) @ nv_debug_dump.c:274
[ 37.081587] NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 78!
[ 37.081588] NVRM: nvCheckOkFailedNoLog: Check failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from nvdEngineDumpCallbackHelper(pGpu, pPrbEnc, pNvDumpState, pEngineCallback) @ nv_debug_dump.c:274
[ 37.081649] NVRM: RmLogGpuCrash: RmLogGpuCrash: failed to save GPU crash data
[ 37.081653] NVRM: _kgspLogRpcSanityCheckFailure: GPU0 sanity check failed 0xf waiting for RPC response from GSP. Expected function 103 (GSP_RM_ALLOC) (0x0 0x6c).
[ 37.081655] NVRM: GPU0 GSP RPC buffer contains function 78 (DUMP_PROTOBUF_COMPONENT) and data 0x0000000000000000 0x0000000000000000.
[ 37.081657] NVRM: GPU0 RPC history (CPU -> GSP):
[ 37.081658] NVRM: entry function data0 data1 ts_start ts_end duration actively_polling
[ 37.081660] NVRM: 0 103 GSP_RM_ALLOC 0x0000000000000000 0x000000000000006c 0x000627e8b90ae16a 0x0000000000000000 y
[ 37.081663] NVRM: -1 76 GSP_RM_CONTROL 0x00000000402c0105 0x0000000000000038 0x000627e8b9017a7b 0x000627e8b901caab 20528us
[ 37.081666] NVRM: -2 76 GSP_RM_CONTROL 0x00000000402c0105 0x0000000000000038 0x000627e8b90129ff 0x000627e8b9017a6e 20591us
[ 37.081669] NVRM: -3 76 GSP_RM_CONTROL 0x00000000402c0105 0x0000000000000038 0x000627e8b900d9a5 0x000627e8b90129f0 20555us
[ 37.081671] NVRM: -4 76 GSP_RM_CONTROL 0x00000000402c0105 0x0000000000000038 0x000627e8b9008970 0x000627e8b900d996 20518us
[ 37.081673] NVRM: -5 76 GSP_RM_CONTROL 0x00000000402c0105 0x0000000000000038 0x000627e8b9003928 0x000627e8b9008962 20538us
[ 37.081675] NVRM: -6 76 GSP_RM_CONTROL 0x00000000402c0105 0x0000000000000038 0x000627e8b8ffe1c5 0x000627e8b9003913 22350us
[ 37.081678] NVRM: -7 76 GSP_RM_CONTROL 0x000000002080e634 0x0000000000000188 0x000627e8b8ffd0a4 0x000627e8b8ffe139 4245us
[ 37.081680] NVRM: GPU0 RPC event history (CPU <- GSP):
[ 37.081681] NVRM: entry function data0 data1 ts_start ts_end duration during_incomplete_rpc
[ 37.081684] NVRM: 0 4099 POST_EVENT 0x0000000000000021 0x0000000000000020 0x000627e8b8ffcf1b 0x000627e8b8ffcf1f 4us
[ 37.081687] NVRM: -1 4099 POST_EVENT 0x0000000000000021 0x0000000000000100 0x000627e8b8b04bb8 0x000627e8b8b04bbe 6us
[ 37.081689] NVRM: -2 4108 UCODE_LIBOS_PRINT 0x0000000000000000 0x0000000000000000 0x000627e8b7fdab7f 0x000627e8b7fdab80 1us
[ 37.081691] NVRM: -3 4108 UCODE_LIBOS_PRINT 0x0000000000000000 0x0000000000000000 0x000627e8b7fdaa50 0x000627e8b7fdaa52 2us
[ 37.081693] NVRM: -4 4128 GSP_POST_NOCAT_RECORD 0x0000000000000002 0x0000000000000027 0x000627e8b7fd66d0 0x000627e8b7fd66d3 3us
[ 37.081695] NVRM: -5 4098 GSP_RUN_CPU_SEQUENCER 0x000000000000061c 0x0000000000003fe2 0x000627e8b7fcceb1 0x000627e8b7fce5ab 5882us
[ 37.081700] CPU: 11 UID: 1000 PID: 3469 Comm: nvidia-settings Tainted: G O 6.11.10-300.fc41.x86_64 #1
[ 37.081703] Tainted: [O]=OOT_MODULE
[ 37.081704] Hardware name: Dell Inc. Dell G15 5510/0H0F1D, BIOS 1.28.0 10/01/2024
[ 37.081706] Call Trace:
[ 37.081709] <TASK>
[ 37.081716] dump_stack_lvl+0x5d/0x80
[ 37.081731] _kgspRpcRecvPoll+0x37f/0x7a0 [nvidia]
[ 37.082436] _issueRpcAndWait+0x70/0x360 [nvidia]
[ 37.082739] rpcRmApiAlloc_GSP+0x1ed/0x500 [nvidia]
[ 37.082958] ? iterate_fd+0x82/0xa0
[ 37.082962] deviceConstruct_IMPL+0x52e/0x810 [nvidia]
[ 37.083202] ? deviceConstruct_IMPL+0x771/0x810 [nvidia]
[ 37.083450] ? __kmalloc_noprof+0x1c3/0x490
[ 37.083456] ? gpuGetByRef+0xc9/0x110 [nvidia]
[ 37.083688] ? __nvoc_ctor_RsResource+0x4e/0x70 [nvidia]
[ 37.083896] __nvoc_objCreate_Device+0x19e/0x2b0 [nvidia]
[ 37.084070] ? os_acquire_spinlock+0x12/0x30 [nvidia]
[ 37.084223] __nvoc_objCreateDynamic+0x46/0x80 [nvidia]
[ 37.084419] ? os_alloc_mem+0xc0/0xd0 [nvidia]
[ 37.084579] resservResourceFactory+0xa1/0x1d0 [nvidia]
[ 37.084793] _clientAllocResourceHelper+0x289/0x6e0 [nvidia]
[ 37.084988] ? _tlsThreadEntryGet+0x82/0x90 [nvidia]
[ 37.085172] serverAllocResourceUnderLock+0x3ec/0x990 [nvidia]
[ 37.085356] ? __serverFindClientEntryByHandle+0xcc/0x150 [nvidia]
[ 37.085524] ? portThreadGetCurrentThreadId+0x1d/0x30 [nvidia]
[ 37.085703] ? rmclientValidateLocks_IMPL+0x21/0xa0 [nvidia]
[ 37.085931] ? _serverLockClientWithLockInfo.constprop.0+0x105/0x280 [nvidia]
[ 37.086165] serverAllocResource+0x567/0x6e0 [nvidia]
[ 37.086587] rmapiAllocWithSecInfo+0x204/0x440 [nvidia]
[ 37.086855] rmapiAllocWithSecInfoTls+0x70/0xa0 [nvidia]
[ 37.087063] Nv04AllocWithAccessSecInfo+0x6a/0x80 [nvidia]
[ 37.087272] RmIoctl+0xa3a/0xdc0 [nvidia]
[ 37.087493] ? os_get_current_tick+0x3b/0xa0 [nvidia]
[ 37.087637] ? os_acquire_spinlock+0x12/0x30 [nvidia]
[ 37.087775] ? portSyncSpinlockAcquire+0x1d/0x50 [nvidia]
[ 37.087948] rm_ioctl+0x67/0x4d0 [nvidia]
[ 37.088182] ? __check_object_size+0x21c/0x230
[ 37.088188] nvidia_unlocked_ioctl+0x53b/0x8d0 [nvidia]
[ 37.088371] __x64_sys_ioctl+0x94/0xd0
[ 37.088379] do_syscall_64+0x82/0x160
[ 37.088396] ? nvidia_unlocked_ioctl+0x166/0x8d0 [nvidia]
[ 37.088530] ? syscall_exit_to_user_mode+0x10/0x220
[ 37.088539] ? do_syscall_64+0x8e/0x160
[ 37.088542] ? os_acquire_spinlock+0x12/0x30 [nvidia]
[ 37.088648] ? portSyncSpinlockAcquire+0x1d/0x50 [nvidia]
[ 37.088783] ? threadStateFree+0xcd/0x230 [nvidia]
[ 37.088980] ? rm_ioctl+0x7e/0x4d0 [nvidia]
[ 37.089162] ? generic_permission+0xe0/0x220
[ 37.089167] ? nvidia_unlocked_ioctl+0x166/0x8d0 [nvidia]
[ 37.089263] ? syscall_exit_to_user_mode+0x10/0x220
[ 37.089270] ? do_syscall_64+0x8e/0x160
[ 37.089278] ? syscall_exit_to_user_mode+0x10/0x220
[ 37.089281] ? do_syscall_64+0x8e/0x160
[ 37.089283] ? syscall_exit_to_user_mode+0x10/0x220
[ 37.089285] ? clear_bhb_loop+0x25/0x80
[ 37.089291] ? clear_bhb_loop+0x25/0x80
[ 37.089292] ? clear_bhb_loop+0x25/0x80
[ 37.089294] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 37.089305] RIP: 0033:0x7f767c5665ad
[ 37.089362] Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
[ 37.089365] RSP: 002b:00007ffd73890550 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 37.089369] RAX: ffffffffffffffda RBX: 0000000000000030 RCX: 00007f767c5665ad
[ 37.089370] RDX: 00007ffd738906d0 RSI: 00000000c030462b RDI: 000000000000000c
[ 37.089372] RBP: 00007ffd738905a0 R08: 00007ffd738906d0 R09: 00007ffd738906f8
[ 37.089373] R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd738906d0
[ 37.089374] R13: 000000000000000c R14: 00000000c030462b R15: 000000000000002b
[ 37.089376] </TASK>
[ 37.089581] NVRM: Xid (PCI:0000:01:00): 154, pid='<unknown>', name=<unknown>, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)
[ 38.073547] nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
[ 38.073579] nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
[ 38.073593] nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
[ 39.682184] NVRM: Error in service of callback
nvidia-bug-report.log.gz (902.9 KB)
Still no acknowledgement from nvidia on the list of issues provided here:
no acknowledgement for this post either: 565 release feedback & discussion - #243 by faz
nvidia team, what is going on? I understand the issues take a while to fix and I appreciate your time for doing so and making the linux driver better for us. However there seems to be no interaction from anyone on the nvidia team for all of these issues. Could I please be provided with the internal bug report IDs?
Meanwhile I spend my time ctrl + alt + f3/f2 because screens randomly freeze. No Eta for new drivers, old ones are a mess or good but totally unsafe (560). I donāt like to complain really, but in this situation where so many issues are present silence shouldnāt be an option. Thank you very much on my side too for your work at nvidia, but be a lil more vocal please.
I donāt think the 560 drivers are a security concern if youāre the only user on the system.
I wouldnāt use them on production or work computers thoā.
