Thanks for the tip,

Working with the ubuntu mainline-crack source it seems a rather humongous task though, any way to narrow down the commits? (also verified 4.2.0-unstable was ok and thought its closer to v4.3-rc1 on the timeline).

odt@cube:mainline-crack$ git log --oneline v4.2 v4.3-rc1 | grep i915 | wc -l

On Wed, Apr 5, 2017 at 9:53 AM, <> wrote:

Comment # 4 on bug 100414 from Jani Nikula
(In reply to oliver from comment #3)
> Any thoughts on how to bisect this?

git bisect good 4.2.8
git bisect bad 4.3.0-rc1

You are receiving this mail because:
  • You are on the CC list for the bug.
  • You reported the bug.