[Bug 1226220] New: X session ends abruptly
https://bugzilla.suse.com/show_bug.cgi?id=1226220 Bug ID: 1226220 Summary: X session ends abruptly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs@suse.de Reporter: rosuna@suse.com QA Contact: sndirsch@suse.com Target Milestone: --- Found By: --- Blocker: --- My X session has crashed abruptly 3 days in a row (Monday, Tuesday, Wednesday). During the 8-9-10 hours I'm working, this has happened only once every day. I do have the latest Nvidia drivers provided by the Tumbleweed repository. I use X11, not Wayland, in case this gives any further information. Tumbleweed is pretty updated. I'm attaching a supportconfig, I know the rest of this report doesn't give much information. It looks like there seems to be some problem with the latest drivers, some source: https://www.gamingonlinux.com/2024/06/you-may-want-to-avoid-nvidia-driver-55... Lenovo ThinkPad P15 Gen 2i Supportconfig within Engineering internal network, shared in my Export: https://w3.suse.de/~rosuna/supportconfig/ Let me know if someone else needs to access it in a more public place. Happy to report it against Nvidia if you consider that (and if you tell me how). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c1 --- Comment #1 from Raúl Osuna <rosuna@suse.com> --- If you're looking for timestamps in the logs, the last crash was not long before the supportconfig was taken. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c2 --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- Could also be related to latest 6.9 kernel. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gfx-bugs@suse.de |sndirsch@suse.com Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c3 --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- grep nvidia messages.txt |grep -i error|cut -d " " -f 3-30 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 1 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 2 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 1 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 2 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 1 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 2 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22 kernel: [drm:nv_drm_revoke_sub_ownership [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to revoke sub-ownership from NVKMS kernel: [drm:nv_drm_master_drop [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] nv_drm_atomic_helper_disable_all failed with error code -22 ! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c4 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rosuna@suse.com) CC| |rosuna@suse.com --- Comment #4 from Stefan Dirsch <sndirsch@suse.com> --- If this isn't a regression of the driver, I suggest to try with an older kernel < 6.9. https://download.opensuse.org/history/ https://download.opensuse.org/history/20240523/tumbleweed/repo/oss/x86_64/ We need to figure out if it's a driver or kernel regression. Driver 550.78 is still available. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c5 --- Comment #5 from Raúl Osuna <rosuna@suse.com> --- (In reply to Stefan Dirsch from comment #4)
If this isn't a regression of the driver, I suggest to try with an older kernel < 6.9.
https://download.opensuse.org/history/ https://download.opensuse.org/history/20240523/tumbleweed/repo/oss/x86_64/
We need to figure out if it's a driver or kernel regression. Driver 550.78 is still available.
It's my workstation and I have not such an easy to go back and forth testing. Specially if I have no clue how to trigger the crash (BTW, in case it was not clear what I meant with "crash": it means, the X session dies and after a couple seconds I'm at the initial login screen of the window manager). Today it has not crashed so far, and I'm still on the same kernel and driver version: raul@mordor:~$ uname -r 6.9.3-1-default raul@mordor:~$ rpm -qa|grep -i nvidia-drivers nvidia-drivers-G06-550.90.07-23.1.x86_64 If I go to an old driver, or to an old kernel, how long do I need to stay there to consider it "not crashing"? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c6 Raúl Osuna <rosuna@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rosuna@suse.com) | --- Comment #6 from Raúl Osuna <rosuna@suse.com> --- Removing needinfo till I really know what/how/when to test. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c7 --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- Thanks. Understood. Probably you would need to test a few days without crashes with the old kernel/driver to verify that it's a regression. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c8 --- Comment #8 from Raúl Osuna <rosuna@suse.com> --- System did not crash since I opened the bug. It did not shut down properly once though, not sure whether related or not. Anyway, there's an update from 6.9.3-1 to 6.9.4-1, which I'm applying right now. Will report back if anything changes (otherwise, feel free to close the bug after a reasonable time with "worksforme" or something similar). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c9 --- Comment #9 from Stefan Dirsch <sndirsch@suse.com> --- Thanks for the update! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226220 https://bugzilla.suse.com/show_bug.cgi?id=1226220#c10 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|IN_PROGRESS |RESOLVED --- Comment #10 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Let's assume for now that things have improved. Closing. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com