Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1953710AbdDYUDs (ORCPT ); Tue, 25 Apr 2017 16:03:48 -0400 Received: from mail.fireflyinternet.com ([109.228.58.192]:56580 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1948689AbdDYUDl (ORCPT ); Tue, 25 Apr 2017 16:03:41 -0400 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Date: Tue, 25 Apr 2017 21:03:32 +0100 From: Chris Wilson To: Michal Hocko Cc: Daniel Vetter , Jani Nikula , David Airlie , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org Subject: Re: [Intel-gfx] GPU hangs and X shot down with 4.11-rc6 Message-ID: <20170425200332.GJ11432@nuc-i3427.alporthouse.com> Mail-Followup-To: Chris Wilson , Michal Hocko , Daniel Vetter , Jani Nikula , David Airlie , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org References: <20170425164119.GA9804@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170425164119.GA9804@dhcp22.suse.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2257 Lines: 43 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. -Chris -- Chris Wilson, Intel Open Source Technology Centre