linux-kernel - Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

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]

Date:   Mon, 07 Nov 2016 19:09:36 +0200
From:   Jani Nikula <jani.nikula@...ux.intel.com>
To:     Martin Steigerwald <martin@...htvoll.de>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Intel Gfx Mailing List <intel-gfx@...edesktop.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel      Sandybridge (was: Re: Linux 4.9-rc4)

On Mon, 07 Nov 2016, Martin Steigerwald <martin@...htvoll.de> wrote:
> It is also the same kind of corruptions as shown in
>
> [Bug 177701] warning in intel_dp_aux_transfer
> https://bugzilla.kernel.org/show_bug.cgi?id=177701
>
> Just compare
>
> https://bugzilla.kernel.org/attachment.cgi?id=241801
>
> with 
>
> https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
>
>
> However that bug report links to
>
> https://bugs.freedesktop.org/show_bug.cgi?id=97344
>
> yet the patch mentioned in there does not fix the issue. So I wonder whether 
> bug #97344 and bug #177701 are really the same.

They are the same, it's just that #177701 conflates two issues, a
warning (tracked at fdo #973449) and a graphics corruption. The latter
appears to be https://bugs.freedesktop.org/show_bug.cgi?id=98402.

The fix has now been pushed to drm-intel-fixes branch of
http://cgit.freedesktop.org/drm-intel, which is -rc4 plus half a dozen
latest fixes. Please try that and report back.

> Of course I can report a bug at fdo as well, but I am a bit confused
> whether it may not already have been reported. Well I hope I get a
> chance to report it there as well and you get to decide.

If drm-intel-fixes doesn't fix the issue for you, please file a *new*
bug over at the freedesktop.org bugzilla.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center