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 11:07:20 +0200 [thread overview]
Message-ID: <20150721090720.GC16722@phenom.ffwll.local> (raw)
In-Reply-To: <55AE09CA.7060206@winsoft.pl>
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.
-Daniel
--
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
next prev parent reply other threads:[~2015-07-21 9:04 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 [this message]
2015-07-21 9:43 ` Chris Wilson
2015-07-21 12:48 ` Krzysztof Kolasa
2015-07-21 14:03 ` Daniel Vetter
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=20150721090720.GC16722@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