| Summary: | drivers/gpu/drm/i915/intel_uncore.c:1083 __unclaimed_reg_debug - HP Pavilion x360 | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Len Brown <lenb> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs, ville.syrjala |
| Version: | XOrg git | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | Triaged | ||
| i915 platform: | BSW/CHT | i915 features: | |
| Bug Depends on: | |||
| Bug Blocks: | 110785 | ||
|
Description
Len Brown
2018-09-13 00:25:47 UTC
Triggered by chv_phy_control_init()/I915_WRITE(DISPLAY_PHY_CONTROL,...) . According to Ville the register is backed by the 'Display' power well. Not actually sure why the WARN triggers only sometimes, this power well should be off whenever we resume from idle. Len, could you provide a full drm.debug=0x1e log including the WARN with the following patch applied (based on 4.19.0-rc2): From d7065f41143d9826554a11fd26052f6f9110dc9f Mon Sep 17 00:00:00 2001 From: Imre Deak <imre.deak@intel.com> Date: Thu, 13 Sep 2018 17:26:58 +0300 Subject: [PATCH] drm/i915: Dump power domains state during init/resume Signed-off-by: Imre Deak <imre.deak@intel.com> --- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c b/drivers/gpu/drm/i915/intel_runtime_pm.c index 6b5aa3b074ec..4ac88ed3c1a4 100644 --- a/drivers/gpu/drm/i915/intel_runtime_pm.c +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c @@ -3528,6 +3528,8 @@ static void vlv_cmnlane_wa(struct drm_i915_private *dev_priv) cmn->ops->disable(dev_priv, cmn); } +static void intel_power_domains_dump_info(struct drm_i915_private *dev_priv); + /** * intel_power_domains_init_hw - initialize hardware power domain state * @dev_priv: i915 device instance @@ -3545,6 +3547,8 @@ void intel_power_domains_init_hw(struct drm_i915_private *dev_priv, bool resume) power_domains->initializing = true; + intel_power_domains_dump_info(dev_priv); + if (IS_ICELAKE(dev_priv)) { icl_display_core_init(dev_priv, resume); } else if (IS_CANNONLAKE(dev_priv)) { @@ -3606,8 +3610,11 @@ static void intel_power_domains_dump_info(struct drm_i915_private *dev_priv) for_each_power_well(dev_priv, power_well) { enum intel_display_power_domain domain; - DRM_DEBUG_DRIVER("%-25s %d\n", - power_well->name, power_well->count); + DRM_DEBUG_DRIVER("%-25s %d enabled %d\n", + power_well->name, + power_well->count, + power_well->ops->is_enabled(dev_priv, + power_well)); for_each_power_domain(domain, power_well->domains) DRM_DEBUG_DRIVER(" %-23s %d\n", -- 2.13.2 Len, any progress here? Len, do you still have the issue? Can you apply the patch suggested by Imre and send full dmesg with kernel parameter drm.debug=0x1e? No feedback from more than a month. closing as resolved works for me. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.