linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Martin Steigerwald <martin@lichtvoll.de>,
	intel-gfx@lists.freedesktop.org
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: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel      Sandybridge (was: Re: Linux 4.9-rc4)
Date: Wed, 09 Nov 2016 11:42:36 +0200	[thread overview]
Message-ID: <87d1i5gfar.fsf@intel.com> (raw)
In-Reply-To: <2133270.BvWHEGSr0T@merkaba>

On Wed, 09 Nov 2016, Martin Steigerwald <martin@lichtvoll.de> wrote:
> Also no graphics glitches with external DisplayPort connected display.

Thanks for confirming this. The fix should make it to -rc5.

> *However*, I got a soft freeze and a hard freeze (well after about a
> minute I gave up and rebooted by pressing power button long enough to
> forcefully switch off the laptop) when playing PlaneShift using
> drm-intel-fixes branch.
>
> Unfortunately I have no further time to debug any of this week, but it
> seems not all fixes are there are ready for next stable kernel.

Current drm-intel-fixes is just six commits on top of -rc4, and it's
very hard for me to believe any of those would cause the symptoms you
see. I presume the problem, whatever it is, is already in -rc4.

That, of course, is not a happy thing per se, but please don't block the
current batch of fixes by making unsubstantiated claims. Please do file
a bug about that issue over at [1] so we don't hijack this thread.

Thanks,
Jani.


[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2016-11-09  9:42 UTC|newest]

Thread overview: 14+ 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 15:25   ` Mihai Donțu
2016-11-06 15:40     ` 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 17:09       ` Jani Nikula
2016-11-07 22:53         ` Martin Steigerwald
2016-11-08 15:11         ` Martin Steigerwald
2016-11-08 15:17           ` Martin Steigerwald
2016-11-09  8:20             ` Martin Steigerwald
2016-11-09  9:42               ` Jani Nikula [this message]
2016-11-09  9:59                 ` 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=87d1i5gfar.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@freedesktop.org \
    --cc=intel-gfx@lists.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 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).