All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Intel Gfx Mailing List <intel-gfx@freedesktop.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel	Sandybridge (was: Re: Linux 4.9-rc4)
Date: Mon, 07 Nov 2016 19:09:36 +0200	[thread overview]
Message-ID: <87k2cf8be7.fsf@intel.com> (raw)
In-Reply-To: <2766000.XjMLcDtyKU@merkaba>

On Mon, 07 Nov 2016, Martin Steigerwald <martin@lichtvoll.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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Intel Gfx Mailing List <intel-gfx@freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel      Sandybridge (was: Re: Linux 4.9-rc4)
Date: Mon, 07 Nov 2016 19:09:36 +0200	[thread overview]
Message-ID: <87k2cf8be7.fsf@intel.com> (raw)
In-Reply-To: <2766000.XjMLcDtyKU@merkaba>

On Mon, 07 Nov 2016, Martin Steigerwald <martin@lichtvoll.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

  reply	other threads:[~2016-11-07 17:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 23:46 Linux 4.9-rc4 Linus Torvalds
2016-11-06 14:48 ` [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4) Martin Steigerwald
2016-11-06 14:48   ` Martin Steigerwald
2016-11-06 15:25   ` Mihai Donțu
2016-11-06 15:25     ` Mihai Donțu
2016-11-06 15:40     ` Martin Steigerwald
2016-11-06 15:40       ` Martin Steigerwald
2016-11-06 17:50     ` Martin Steigerwald
2016-11-06 17:50       ` Martin Steigerwald
2016-11-07 11:04   ` [Intel-gfx] " Jani Nikula
2016-11-07 14:29     ` Martin Steigerwald
2016-11-07 14:29       ` [Intel-gfx] " Martin Steigerwald
2016-11-07 17:09       ` Jani Nikula [this message]
2016-11-07 17:09         ` Jani Nikula
2016-11-07 22:53         ` Martin Steigerwald
2016-11-07 22:53           ` [Intel-gfx] " Martin Steigerwald
2016-11-08 15:11         ` Martin Steigerwald
2016-11-08 15:11           ` [Intel-gfx] " Martin Steigerwald
2016-11-08 15:17           ` Martin Steigerwald
2016-11-09  8:20             ` Martin Steigerwald
2016-11-09  8:20               ` [Intel-gfx] " Martin Steigerwald
2016-11-09  9:42               ` Jani Nikula
2016-11-09  9:42                 ` [Intel-gfx] " Jani Nikula
2016-11-09  9:59                 ` Martin Steigerwald
2016-11-09  9:59                   ` [Intel-gfx] " Martin Steigerwald

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=87k2cf8be7.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.