public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Krzysztof Kolasa <kkolasa@winsoft.pl>
Cc: daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
	mika.kuoppala@intel.com
Subject: Re: interference on display, Intel 945GM, 32bit system, kernel next
Date: Tue, 21 Jul 2015 16:03:12 +0200	[thread overview]
Message-ID: <20150721140312.GN16722@phenom.ffwll.local> (raw)
In-Reply-To: <55AE3F95.4060305@winsoft.pl>

On Tue, Jul 21, 2015 at 02:48:21PM +0200, Krzysztof Kolasa wrote:
> On 21.07.2015 11:43, Chris Wilson wrote:
> > On Tue, Jul 21, 2015 at 11:07:20AM +0200, Daniel Vetter wrote:
> >> On Tue, Jul 21, 2015 at 10:58:50AM +0200, Krzysztof Kolasa wrote:
> >>> On 21.07.2015 10:41, Daniel Vetter wrote:
> >>>> I meant whether you can reset the bad commit and it's immediate parent
> >>>> extensively to make sure the bisect is really correct. gpu's occasionally
> >>>> take a while to hang themselves, so could be that the bisect was
> >>>> mislead somewhere.
> >>>
> >>> Again I will bisect, more testing good sections.
> >>>
> >>> At the moment on my old laptop, the latest official, properly working kernel is 4.1.2
> >> You don't need to redo the full bisect, only retest the bad and the parent
> >> of the bad extensively. That's enough to confirm the bisect result for
> >> sure.
> > The bisection is misleading. It's a missing write-barrier.
> > -Chris
> >
> tested again:
> 
> # good: [cd102a687beed1042824d5fa81c6ba8bfe78e6a4] drm/i915: Remove misleading comment around bind_to_vm
> git bisect good cd102a687beed1042824d5fa81c6ba8bfe78e6a4
> # bad: [0875546c5318c85c13d07014af5350e9000bc9e9] drm/i915: Fix up the vma aliasing ppgtt binding
> git bisect bad 0875546c5318c85c13d07014af5350e9000bc9e9
> # first bad commit: [0875546c5318c85c13d07014af5350e9000bc9e9] drm/i915: Fix up the vma aliasing ppgtt binding
> 
> 
> Screen does not lie :) first bad is BAD, good is GOOD
> 
> on commit cd102a687beed10, computer worked steadily (with a large number of windows, applications) about an hour and stopped the tests, everything was OK
> 
> on commit 0875546c5318c85, after about one minute, the screen gone mad

Suprising. Can you try out the below patch, it should disable the active
ingredient of the offending. On older kernels just remove the if
(bind_flags) before the call to ->bind_vma - the point is to call
->bind_vma unconditionally.
-Daniel

diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
index cc133c700686..1227cd69c624 100644
--- a/drivers/gpu/drm/i915/i915_gem_gtt.c
+++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
@@ -2908,9 +2908,6 @@ int i915_vma_bind(struct i915_vma *vma, enum i915_cache_level cache_level,
 	else
 		bind_flags &= ~vma->bound;
 
-	if (bind_flags == 0)
-		return 0;
-
 	if (vma->bound == 0 && vma->vm->allocate_va_range) {
 		trace_i915_va_alloc(vma->vm,
 				    vma->node.start,
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-07-21 14:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 18:07 interference on display, Intel 945GM, 32bit system, kernel next Krzysztof Kolasa
2015-07-21  7:30 ` Daniel Vetter
     [not found]   ` <55ADFDF0.4060407@winsoft.pl>
2015-07-21  8:41     ` Daniel Vetter
2015-07-21  8:58       ` Krzysztof Kolasa
2015-07-21  9:07         ` Daniel Vetter
2015-07-21  9:43           ` Chris Wilson
2015-07-21 12:48             ` Krzysztof Kolasa
2015-07-21 14:03               ` Daniel Vetter [this message]
2015-07-21 18:07                 ` Krzysztof Kolasa
2015-07-22  8:27                   ` Daniel Vetter
2015-07-22  9:38                     ` Krzysztof Kolasa
2015-07-31 14:11                     ` Krzysztof Kolasa
2015-07-31 14:54                       ` Chris Wilson

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=20150721140312.GN16722@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kkolasa@winsoft.pl \
    --cc=mika.kuoppala@intel.com \
    /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