From: Michal Hocko <mhocko@kernel.org>
To: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: GPU hangs and X shot down with 4.11-rc6
Date: Tue, 25 Apr 2017 18:41:20 +0200 [thread overview]
Message-ID: <20170425164119.GA9804@dhcp22.suse.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]
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.
Let me know if you need additional information.
Thanks!
--
Michal Hocko
SUSE Labs
[-- Attachment #2: gpu_dump.gz --]
[-- Type: application/gzip, Size: 14952 bytes --]
next reply other threads:[~2017-04-25 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 16:41 Michal Hocko [this message]
2017-04-25 20:03 ` [Intel-gfx] " Chris Wilson
2017-04-26 9:28 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170425164119.GA9804@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®