Comment 97 for bug 1453298

(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 ?