[Bug 105184] New: i915 GPU hang - random and REALLY annoying.

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 105184
           Summary: i915 GPU hang - random and REALLY annoying.
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: wwill at farreaches.org
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

I have searched the bugzilla archives and found tons of things similar but
nothing which makes any difference or progress toward correcting this.  It
started occurring when OpenSuSE "updated" LEAP 43.2 to the 4.4.114-42 kernel. 
Before, in the 4.4. <100 verions I had no such problems whatsoever.  There was
an intermediate update to the 4.4.104 kernel, and power management went out the
window.  No graphics issues then, and power management was restored / fixed
with this .114 increment.  

This GPU hang happens about a dozen times a day.  Too random to pin down, can
happen in any open window and any running application.  Usual tasks are one web
browser (PaleMoon - version 27.6.2 (64-bit)) with no more than five tabs open
at once; one email client (SeaMonkey Mail - User agent: Mozilla/5.0 (X11; Linux
x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1); and sometimes
an e-book reader (FBReader - version of the RPM package shows
fbreader-0.12.10-19.23.x86_64).

I really don't use much of anything else on a regular basis, don't 'game,' and
don't do much of anything more graphics-intensive than the odd video clip.  

Clipboard manager, wireless networking, and a battery monitor is about it.  KDE
window manager running, and thinking seriously about dumping EVERYTHING
'systemd' related and switching distros entirely to something WITHOUT systemd
or any of that foolishness.  (Lennart can STUFF his idiotic systemd crap.  Give
me my text file configurations back!!)

More info, just what I can guess is pertinent, ask for anything else you
require if it comes to your mind:

output of uname -a 
Linux toughbook.farreaches.org 4.4.114-42-default #1 SMP Tue Feb 6 10:58:10 UTC
2018 (b6ee9ae) x86_64 x86_64 x86_64 GNU/Linux

Hardware is an ex-Illinois-State-Police Panasonic CF-30 ToughBook laptop I
rescued from a recycler.  Nothing at all added or special in the hardware,
everything is bog-standard, just like straight out of the factory as far as the
memory and CPU specs go.  Other than the <expletive deleted> multiplexed USB
glidepad and touch screen which still gives me grief now and again, it does
yeoman service and is just as rugged as advertised.

The pertinent part of dmesg gives:

[drm] GPU HANG: ecode 4:0:0x828fffff, in X [2213], reason: Hang on render ring,
action: reset
[  266.808827] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[  266.808828] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[  266.808829] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[  266.808829] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[  266.808830] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  266.808894] drm/i915: Resetting chip after gpu hang

So here, as asked in the dmesg text, is a new bug for your perusal and
hopefully my edification.  Crash dump file /sys/class/drm/card0/error is ZERO
BYTES and cannot be deleted even as root.  If it had anything in it I would
attach it....

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