[Bug 100110] New: [SNB] 4.11-rc1: gpu hang after about 10 minutes of Plasma session usage during rsync file copy

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 8 10:50:40 UTC 2017


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

            Bug ID: 100110
           Summary: [SNB] 4.11-rc1: gpu hang after about 10 minutes of
                    Plasma session usage during rsync file copy
           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: Martin at Lichtvoll.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 130120
  --> https://bugs.freedesktop.org/attachment.cgi?id=130120&action=edit
complete dmesg of boot where intel gpu hung

I got around to test whether GPU hangs on ThinkPad T520 with Sandybridge HD
3000 graphics that started with 4.9 are fixed in 4.11-rc1. Unfortunately they
are not, but this time I had another box to SSH into the laptop and gather the
error file.

I compiled 4.11-rc1 + a few commits, booted from it and then copied some files
around with rsync. I had one Plasma session with kwin_x11 and Compositing
running. During the rsync, which might be related or pure coincidence, graphic
output froze. I was able to switch to TTY1, but cursor was frozen to.

I SSH´d from my training workstation to the laptop I saw the following in
dmesg:

[ 1393.553774] [drm] GPU HANG: ecode 6:0:0x00ffffff, in kwin_x11 [2261],
reason: Hang on render ring, action: reset
[ 1393.553778] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 1393.553779] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 1393.553780] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 1393.553781] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 1393.553782] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1393.553833] drm/i915: Resetting chip after gpu hang
[ 1401.549065] drm/i915: Resetting chip after gpu hang
[ 1401.549077] [drm:i915_reset] *ERROR* GPU recovery failed

As the hang happened I waited at least a minute for it to recover, but
apparently I wasn´t able to.

This is on ThinkPad T520 with Sandybridge HD 3000 graphics on Debian Sid with
Xorg running with modesetting driver. There is no custom configuration like
enabling DRI 3 or so… modesetting driver is default on Debian Sid since some
time.

I will attach complete dmesg and Xorg log of that boot.

Relevant package versions:

~> apt-show-versions | egrep
"libdrm|libgbm|xserver-xorg:|xserver-xorg-core:|libgl1-mesa-dri" | grep amd64
libdrm-amdgpu1:amd64/sid 2.4.74-1 uptodate
libdrm-dev:amd64/sid 2.4.74-1 uptodate
libdrm-intel1:amd64/sid 2.4.74-1 uptodate
libdrm-nouveau2:amd64/sid 2.4.74-1 uptodate
libdrm-radeon1:amd64/sid 2.4.74-1 uptodate
libdrm2:amd64/sid 2.4.74-1 uptodate
libgbm1:amd64/experimental 17.0.1-1 uptodate
libgl1-mesa-dri:amd64/experimental 17.0.1-1 uptodate
xserver-xorg:amd64/sid 1:7.7+18 uptodate
xserver-xorg-core:amd64/sid 2:1.19.2-1 uptodate

What I offer:
- test patches
- test different driver settings
- provide additional information if obtainable with reasonable amount of time

What I do not offer:
- git bisect (due to amount of time needed and fact that this is a production
machine)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list 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/20170308/bdd43130/attachment-0001.html>


More information about the intel-gfx-bugs mailing list