linux-kernel - Re: [Intel-gfx] GPU hangs and X shot down with 4.11-rc6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 26 Apr 2017 11:28:36 +0200
From:   Michal Hocko <mhocko@...nel.org>
To:     Chris Wilson <chris@...is-wilson.co.uk>
Cc:     Daniel Vetter <daniel.vetter@...el.com>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        David Airlie <airlied@...ux.ie>,
        intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
        dri-devel@...ts.freedesktop.org
Subject: Re: [Intel-gfx] GPU hangs and X shot down with 4.11-rc6

On Tue 25-04-17 21:03:32, Chris Wilson wrote:
> On Tue, Apr 25, 2017 at 06:41:20PM +0200, Michal Hocko wrote:
> > Hi,
> > I have just experienced X being shut down once with 4.11-rc2 and 2 times
> > with 4.11-rc6 kernel.  I do not remember seeing something like this
> > before but it is quite possible I was just lucky to not trigger this
> > issue before. It always happened while I was working on a presentation
> > in LibreOffice which I do very seldom. The kernel log contains:
> > 
> > [ 7456.721893] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [3594], reason: Hang on render ring, action: reset
> > [ 7456.721897] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
> > [ 7456.721898] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
> > [ 7456.721900] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
> > [ 7456.721901] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
> > [ 7456.721902] [drm] GPU crash dump saved to /sys/class/drm/card0/error
> > [ 7456.721925] drm/i915: Resetting chip after gpu hang
> > [ 7456.722117] [drm] RC6 on
> > [ 7456.734588] [drm] GuC firmware load skipped
> > [ 7464.686209] drm/i915: Resetting chip after gpu hang
> > [ 7464.686284] [drm] RC6 on
> > [ 7464.702469] [drm] GuC firmware load skipped
> > [ 7472.686180] drm/i915: Resetting chip after gpu hang
> > [ 7472.686241] [drm] RC6 on
> > [ 7472.704565] [drm] GuC firmware load skipped
> > [ 7480.686179] drm/i915: Resetting chip after gpu hang
> > [ 7480.686241] [drm] RC6 on
> > [ 7480.704583] [drm] GuC firmware load skipped
> > [ 7493.678130] drm/i915: Resetting chip after gpu hang
> > [ 7493.678206] [drm] RC6 on
> > [ 7493.696505] [drm] GuC firmware load skipped
> > 
> > The kernel message tells that the problem might be anywhere and I should
> > report to freedesktop but I haven't changed the userspace recently so it
> > smells more like a kernel bug to me. Does this ring bells? The GPU crash
> > dump is attached in case it is useful.
> 
> There are lots of very similar GPU hangs for mesa across a wide range of
> kernels, with several reports noting a correlation with libreoffice.
> 
> At first glance, I would say you were just unlucky to hit it.

OK, good to know. Thanks!
-- 
Michal Hocko
SUSE Labs