From: Jani Nikula <jani.nikula@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Fabian Pie <fpie@teleker.com>
Subject: Re: Screen flicker regression on Baytrail
Date: Fri, 28 Oct 2016 08:43:48 +0300 [thread overview]
Message-ID: <87r371m3jf.fsf@intel.com> (raw)
In-Reply-To: <22cc36c5-e29a-ef95-c86e-9c8af0051128@linux.intel.com>
On Thu, 27 Oct 2016, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> wrote:
> While testing our upcoming HDMI audio patches, I experienced pretty bad
> screen flicker regressions on my Baytrail compute stick. This happens
> with both v09-rc2 and drm-intel-nightly.
>
> A quick bisect with all the audio patches removed points to the
> following commit:
>
> 2efb813d5388e18255c54afac77bd91acd586908 is the first bad commit
> commit 2efb813d5388e18255c54afac77bd91acd586908
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date: Thu Aug 18 17:17:06 2016 +0100
>
> drm/i915: Fallback to using unmappable memory for scanout
>
> More logs below. I don't have the background to fix this myself and I
> don't see an obvious link with Baytrail but I hope someone smarter than
> me can help fix this
Looking around, there's bug [1] with same culprit. Please follow up
there.
BR,
Jani.
[1] https://bugs.freedesktop.org/show_bug.cgi?id=98036
>
> -Pierre
>
>
> git bisect start
> # bad: [d8923dcfa53d59886d432a3fc430e26cb92ce86a] drm/i915: Track
> display alignment on VMA
> git bisect bad d8923dcfa53d59886d432a3fc430e26cb92ce86a
> # good: [03af84fe7f48937941fbb4dcd6cf66c68ae0edd4] drm/i915: Choose
> partial chunksize based on tile row size
> git bisect good 03af84fe7f48937941fbb4dcd6cf66c68ae0edd4
> # good: [50349247ea807ad0950bbcedb1abb576e6a785db] drm/i915: Drop
> ORIGIN_GTT for untracked GTT writes
> git bisect good 50349247ea807ad0950bbcedb1abb576e6a785db
> # bad: [2efb813d5388e18255c54afac77bd91acd586908] drm/i915: Fallback to
> using unmappable memory for scanout
> git bisect bad 2efb813d5388e18255c54afac77bd91acd586908
> # good: [821188778b9be2050d45490c4b2b009d51f041e0] drm/i915: Choose not
> to evict faultable objects from the GGTT
> git bisect good 821188778b9be2050d45490c4b2b009d51f041e0
> # first bad commit: [2efb813d5388e18255c54afac77bd91acd586908] drm/i915:
> Fallback to using unmappable memory for scanout
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-10-28 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 18:48 Screen flicker regression on Baytrail Pierre-Louis Bossart
2016-10-28 5:43 ` Jani Nikula [this message]
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=87r371m3jf.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=fpie@teleker.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pierre-louis.bossart@linux.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 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.