linux-kernel - Re: [PATCH] drm/i915: Remove instructions to file a bug report.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEdQ38E4S=D5v_C8k4e4hbmF0e56xFZbFbwq2xxikUhU7eugag@mail.gmail.com>
Date:   Fri, 2 Dec 2016 17:26:43 -0800
From:   Matt Turner <mattst88@...il.com>
To:     "intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>
Cc:     Daniel Vetter <daniel.vetter@...el.com>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        Mika Kuoppala <mika.kuoppala@...el.com>,
        Kenneth Graunke <kenneth@...tecape.org>,
        Mark Janes <mark.a.janes@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Matt Turner <mattst88@...il.com>,
        Ben Widawsky <ben@...dawsk.net>
Subject: Re: [PATCH] drm/i915: Remove instructions to file a bug report.

On Fri, Dec 2, 2016 at 5:03 PM, Matt Turner <mattst88@...il.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@...il.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