[Bug 98902] [BDW] WARN_ON(intel_state->cdclk == 0)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Dec 1 11:08:46 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=98902
mwa <matthew.auld at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #2 from mwa <matthew.auld at intel.com> ---
Fix has now been merged, so marking as resolved:
commit 6a259b1f8a9e99b1ed114f8bf8b0cfccee130e54
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date: Tue Nov 29 16:13:57 2016 +0200
drm/i915: Initialize dev_priv->atomic_cdclk_freq at init time
Looks like we're only initializing dev_priv->atomic_cdclk_freq
at resume and commit times, not at init time. Let's do that as
well.
We're now hitting the 'WARN_ON(intel_state->cdclk == 0)' in
hsw_compute_linetime_wm() on account of populating
intel_state->cdclk from dev_priv->atomic_cdclk_freq.
Previously we were mispopulating intel_state->cdclk with
dev_priv->cdclk_freq which always had a proper value at init
time and hence the WARN_ON() didn't trigger.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161201/dae7a3d8/attachment.html>
More information about the intel-gfx-bugs
mailing list