[Bug 111100] New: i915 GPU hang with kwin_x11

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jul 10 14:08:16 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=111100

            Bug ID: 111100
           Summary: i915 GPU hang with kwin_x11
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: sb56637 at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 144749
  --> https://bugs.freedesktop.org/attachment.cgi?id=144749&action=edit
/sys/class/drm/card0/error

Hi there, not sure if you want duplicate reports or not, because I suspect I am
experiencing bug #111014.

I started experiencing this major bug in one of the openSUSE Tumbleweed
(x86-64) updates within the past couple of weeks. It's hard to say for sure
what is the root cause, because there were kernel updates (currently at
5.1.16), Plasma shell and KWin updates (currently 5.16.2), KDE Framework
updates (currently 5.59.0), and Mesa / Mesa-dri updates (currently at
19.1.1-223.1).

Very frequently (several times within an hour) I notice that the Plasma panel
clock stops updating, and the App Menu and Calendar popups stop rendering (just
the outline), and notification popups show black with a copy of the panel
underneath. When I restart `plasmashell` it fixes it for a while, but later
starts glitching again. It's not a complete system freeze. It mainly seems to
be the panel and notifications. Applications continue to work, as does Alt+Tab
switching. But clicking on running applications in the panel does nothing. Also
files on my ~/Desktop do not update after adding or removing them when this bug
appears. Also Krunner does continue to work, which lets me kill and restart
plasmashell.

This is on a Thinkpad T530 laptop with integrated Intel graphics, running the X
modesetting drivers. I also tried switching to the Xorg Intel driver, but it
still behaves the same. I tried switching the KWin compositor from X11
rendering to openGL, but it made no difference.

I somehow suspect it has something to do with system load, especially RAM
situations, since yesterday was the first day after the major updates that I
was running my Windows VM in VirtualBox. I use zRAM and sometimes hit the
memory pretty hard. It seemed to be after high RAM usage situations, even after
freeing up plenty of RAM, that this glitch started happening. But I'm not 100%
certain.

I switched to an older kernel 5.1.7 that I still have installed, and I haven't
experienced this bug since doing so. That would appear to correlate with this
bug starting to happen when I upgraded from kernel 5.1.7 to 5.1.15 (skipped
some Tumbleweed updates in between).

This is the `dmesg` error:
----------------------
[Tue Jul  9 14:03:12 2019] i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe,
in kwin_x11 [1478], hang on rcs0
[Tue Jul  9 14:03:12 2019] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Tue Jul  9 14:03:12 2019] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Tue Jul  9 14:03:12 2019] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Tue Jul  9 14:03:12 2019] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Tue Jul  9 14:03:12 2019] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
[Tue Jul  9 14:03:12 2019] i915 0000:00:02.0: Resetting chip for hang on rcs0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190710/6b3668de/attachment-0001.html>


More information about the intel-gfx-bugs mailing list