[Bug 88012] [bisected BYT] complete freeze after: drm/i915/vlv: WA for Turbo and RC6 to work together

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=88012

--- Comment #63 from Andy Furniss <adf.lists at gmail.com> ---
(In reply to Maxime Bergeron from comment #62)
> (In reply to Andy Furniss from comment #61)
> > 8fb55197e64d5988ec57b54e973daeea72c3f2ff
> > drm/i915: Agressive downclocking on Baytrail
> > 
> > reverted and I didn't lock, so it seems I messed up somewhere for that test
> > initially.
> > 
> > So reverting above alone does make me stable on both the nightly I first
> > tested with and drm-intel-next-queued (tested as it was over the weekend).
> 
> Maybe not. I just tried this (latest drm-intel-next-queued with the commit
> reverted) and I locked after ~2 hours uptime (couldn't get logs, everything
> hung up including ssh). Definitely more stable without the commit (less
> stutter in 1080p video playback), but I had over 50 hours of uptime with
> 4.0.0-RC6 without any issue. Maybe there's something wrong elsewhere ?

Yea, I updated yesterday after seeing this and did manage to lock next-queued.

Possibly not anything recent, though,  as it seems whether I lock or not now
depends on how I test - 1080i30 (+deint) with some 1080p60 on 60Hz display =
lock. I had been testing before with 1080p24 or 1080i25 and retried like this
today - it's still running after 9 Hours.

Given the above the next commit I will try reverting in addition to aggressive
downclock =

6ad790c0f5ac55fd13f322c23519f0d6f0721864
drm/i915: Boost GPU frequency if we detect outstanding pageflips

and I will run samples where frame/field rate = refresh.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150416/08a35733/attachment.html>