From: Matt Turner <mattst88@gmail.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Mika Kuoppala <mika.kuoppala@intel.com>,
Kenneth Graunke <kenneth@whitecape.org>,
Mark Janes <mark.a.janes@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Matt Turner <mattst88@gmail.com>, Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: Remove instructions to file a bug report.
Date: Fri, 2 Dec 2016 17:26:43 -0800 [thread overview]
Message-ID: <CAEdQ38E4S=D5v_C8k4e4hbmF0e56xFZbFbwq2xxikUhU7eugag@mail.gmail.com> (raw)
In-Reply-To: <1480726985-12762-1-git-send-email-mattst88@gmail.com>
On Fri, Dec 2, 2016 at 5:03 PM, Matt Turner <mattst88@gmail.com> wrote:
> From these instructions, users assume that /sys/class/drm/card0/error
> contains all the information a developer needs to diagnose and fix a GPU
> hang.
>
> In fact it doesn't, and we have no tools for solving them (other than
> stabbing in the dark). Most of the time the error state itself isn't
> even useful because it just shows a hang on a PIPE_CONTROL or similar.
>
> Until a time when the error state contains enough information to
> actually solve a hang, stop telling users to file unsolvable bugs, and
> instead rely on users who know where and how to file a good bug report
> to find their own way there.
>
> Signed-off-by: Matt Turner <mattst88@gmail.com>
> ---
> Maybe now's a good time to discuss what *would* be useful to put in the
> error state for debugging hangs. The currently executing shader program
> would be a great place to start.
Looks like Ben had a patch:
https://cgit.freedesktop.org/~bwidawsk/drm-intel/commit/?h=extra_error_objs&id=711da2570cd3302d0cb9f2489a101e4a7c966a6c
next prev parent reply other threads:[~2016-12-03 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 1:03 [PATCH] drm/i915: Remove instructions to file a bug report Matt Turner
2016-12-03 1:26 ` Matt Turner [this message]
2016-12-03 8:57 ` [Intel-gfx] " Chris Wilson
2016-12-03 9:52 ` Jani Nikula
2016-12-06 0:55 ` Matt Turner
2016-12-07 16:09 ` [Intel-gfx] " Daniel Vetter
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='CAEdQ38E4S=D5v_C8k4e4hbmF0e56xFZbFbwq2xxikUhU7eugag@mail.gmail.com' \
--to=mattst88@gmail.com \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kenneth@whitecape.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.janes@intel.com \
--cc=mika.kuoppala@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).