You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my Thinkpad P16 Gen 2 with an Nvidia GPU, a strange issue rarely comes up where the screen freezes and display output stops functioning while mostly everything else continues to function (sounds will play, programs will run, the system will respond to keyboard inputs, etc). Connecting a monitor via the HDMI port on the laptop while this issue is occurring results in the monitor displaying a blank screen. The only things that don't function in this state is plugging in new USB devices and some keyboard shortcuts like volume and brightness control. Additionally I cannot switch to a TTY whenever this happens. After force-shutting down the laptop and powering it back up, most programs that were opened when the issue occurred had their window resized to 640x480.
Looking at the journal of the last boot showed a bunch of "Pageflip timed out!" errors after the issue started occurring (which was at 21:28:44 in the journal as it happened right after exiting full-screen of a running game). There was one kernel message complaining about an OpenGL buffer at the same time the issue happened but I could not capture it in time since the kernel messages vanished from the journal while I was viewing it in the KDE journal viewer (most likely due to another Nvidia bug where the driver spams errors to dmesg while any chromium-based application is open).
This issue has been happening ever since I installed Bazzite on the laptop and happens regardless of what I am doing on the laptop. I have no idea if there is a fix for this issue or what is even causing this issue to happen.
I also made a post in the Discord Bazzite help channel about this issue too earlier in hopes of getting assistance with this issue.
What did you expect to happen?
Display output and the built-in screen to not stop functioning randomly.
Describe the bug
On my Thinkpad P16 Gen 2 with an Nvidia GPU, a strange issue rarely comes up where the screen freezes and display output stops functioning while mostly everything else continues to function (sounds will play, programs will run, the system will respond to keyboard inputs, etc). Connecting a monitor via the HDMI port on the laptop while this issue is occurring results in the monitor displaying a blank screen. The only things that don't function in this state is plugging in new USB devices and some keyboard shortcuts like volume and brightness control. Additionally I cannot switch to a TTY whenever this happens. After force-shutting down the laptop and powering it back up, most programs that were opened when the issue occurred had their window resized to 640x480.
Looking at the journal of the last boot showed a bunch of "Pageflip timed out!" errors after the issue started occurring (which was at 21:28:44 in the journal as it happened right after exiting full-screen of a running game). There was one kernel message complaining about an OpenGL buffer at the same time the issue happened but I could not capture it in time since the kernel messages vanished from the journal while I was viewing it in the KDE journal viewer (most likely due to another Nvidia bug where the driver spams errors to dmesg while any chromium-based application is open).
20240821_journallog.txt
This issue has been happening ever since I installed Bazzite on the laptop and happens regardless of what I am doing on the laptop. I have no idea if there is a fix for this issue or what is even causing this issue to happen.
I also made a post in the Discord Bazzite help channel about this issue too earlier in hopes of getting assistance with this issue.
What did you expect to happen?
Display output and the built-in screen to not stop functioning randomly.
Output of
rpm-ostree status
Hardware
CPU: Intel i9-13950HX vPro
GPU 1: Intel Raptor Lake-S UHD Graphics
GPU 2: Nvidia RTX 5000 Ada Laptop GPU
RAM: 128 GB DDR5 5600 MHz ECC
Extra information or context
No response
The text was updated successfully, but these errors were encountered: