MIME-Version: 1.0
In-Reply-To: <1480726985-12762-1-git-send-email-mattst88@gmail.com>
References: <1480726985-12762-1-git-send-email-mattst88@gmail.com>
From: Matt Turner <mattst88@gmail.com>
Date: Fri, 2 Dec 2016 17:26:43 -0800
Message-ID: <CAEdQ38E4S=D5v_C8k4e4hbmF0e56xFZbFbwq2xxikUhU7eugag@mail.gmail.com>
Subject: Re: [PATCH] drm/i915: Remove instructions to file a bug report.
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>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1082
Lines: 23

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