[Bug 212259] New: Entire graphics stack locks up when running SteamVR and sometimes Sway; is sometimes unrecoverable

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Sat Mar 13 05:39:48 UTC 2021


https://bugzilla.kernel.org/show_bug.cgi?id=212259

            Bug ID: 212259
           Summary: Entire graphics stack locks up when running SteamVR
                    and sometimes Sway; is sometimes unrecoverable
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.11.0
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: happysmash27 at protonmail.com
        Regression: No

Created attachment 295831
  --> https://bugzilla.kernel.org/attachment.cgi?id=295831&action=edit
Last 406 lines of dmesg at the time of error

This bug is driving me nuts! 

First time, it frequently happened when I ran Sway and LXDE at the same time,
where my entire graphics stack would freeze and I would be unable to switch
virtual TTYs or even kill X, even with kill -9 on everything. 

Now, I am experiencing this bug again, this time with SteamVR, and at a MUCH
higher frequency. It seems to happen, fairly randomly, whenever I start
SteamVR, but seems to be more likely when my system has been running for a long
time, or when Waterfox has been running for a long time. 

A couple weeks ago I found a way to reset my GPU as a workaround to the bug
(https://www.reddit.com/r/linuxquestions/comments/lpiwkg/how_to_reset_graphics_stack_when_x_stops/),
but today, this did not work. My screen went black, but I was still unable to
kill -9 X, even after trying the reset many times. In dmesg, there were
messages about the reset still being in-progress, but I did not see anything
seem to change. Eventually, I decided to give up on gracefully fixing this bug
with no downtime to my website and poweroff, then hold the power button of my
computer after the HDD activity light went off as even powering off doesn't
seem to work properly with this bug. Only then, could I reboot and recover. 

I have attached the end of the most recent dmesg where this failed. I also have
more dmesgs that may or may not be the same bug, but the attachment field only
allows for one.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.


More information about the dri-devel mailing list