Bug 110768

Summary: [CI][DRMTIP] igt@kms_3d - dmesg-warn - WARN_ON(intel_wait_for_register(&dev_priv->uncore, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1))
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: critical    
Priority: highest CC: imre.deak, intel-gfx-bugs, ville.syrjala
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: ICL i915 features: display/Other

Description Lakshmi 2019-05-27 10:43:56 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_293/fi-icl-u3/igt@kms_3d.html

<4> [324.435007] WARN_ON(intel_wait_for_register(&dev_priv->uncore, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1))
<4> [324.435080] WARNING: CPU: 7 PID: 194 at drivers/gpu/drm/i915/intel_runtime_pm.c:650 hsw_wait_for_power_well_enable.isra.9+0x4a/0x50 [i915]
<4> [324.435146] Workqueue: i915-dp i915_digport_work_func [i915]
<4> [324.435266]  intel_power_well_enable+0x35/0x40 [i915]
<4> [324.435288]  __intel_display_power_get_domain.part.17+0x69/0x80 [i915]
<4> [324.435312]  intel_display_power_get+0x44/0x60 [i915]
<4> [324.435379]  intel_dp_aux_xfer+0x94/0x8c0 [i915]
<4> [324.435391]  ? drm_dp_dpcd_access+0x62/0x110
<4> [324.435412]  ? drm_dp_dpcd_access+0x62/0x110
<4> [324.435473]  intel_dp_aux_transfer+0xa7/0x200 [i915]
<4> [324.435480]  drm_dp_dpcd_access+0x76/0x110
<4> [324.435488]  drm_dp_dpcd_read+0x29/0xc0
<4> [324.435566]  intel_dp_read_dpcd+0x38/0x120 [i915]
<4> [324.435625]  intel_dp_get_dpcd+0x1d/0xe0 [i915]
<4> [324.435660]  intel_dp_hpd_pulse+0xef/0x370 [i915]
<4> [324.435704]  i915_digport_work_func+0xbb/0x140 [i915]
<4> [324.435758] WARNING: CPU: 7 PID: 194 at drivers/gpu/drm/i915/intel_runtime_pm.c:650 hsw_wait_for_power_well_enable.isra.9+0x4a/0x50 [i915]
Comment 1 CI Bug Log 2019-05-27 10:50:53 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@kms_3d - dmesg-warn - WARN_ON(intel_wait_for_register(&amp;dev_priv-&gt;uncore, regs-&gt;driver, (0x1 &lt;&lt; ((pw_idx) * 2)), (0x1 &lt;&lt; ((pw_idx) * 2)), 1))
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_293/fi-icl-u3/igt@kms_3d.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_294/fi-icl-u3/igt@kms_3d.html
Comment 2 CI Bug Log 2019-05-27 10:51:32 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL:  igt@runner@aborted - fail - Previous test: kms_3d
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_293/fi-icl-u3/igt@runner@aborted.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_294/fi-icl-u3/igt@runner@aborted.html
Comment 3 Lakshmi 2019-05-27 11:22:35 UTC 
This failure occurs on last two drmtip runs on icl-u3. So, at the moment the reproduction rate is 100%.
Comment 4 Mika Kahola 2019-05-27 11:23:01 UTC 
kms_3d tests add 3D modes on top of existing EDID. The connector is forced on and 3D mode configurations are put under a test. In a successful scenario we are able to perform modeset by using 3D modes.

Failure on this test could indicate that the user is unable to use 3D modes on particular connector.
Comment 5 Jani Saarinen 2019-05-27 11:57:10 UTC 
Imre, is this some known issue.
Comment 6 Imre Deak 2019-05-27 13:21:03 UTC 
(In reply to Jani Saarinen from comment #5)
> Imre, is this some known issue.

It's AUX B enabling failure without AUX A being enabled. Perhaps solved by

https://patchwork.freedesktop.org/patch/306887/?series=61123&rev=1

although power well timeouts were not seen before. My suggestion is to wait after the above patch is merged, to see if the problem reported here still happens. If so we have to track down what is the separate reason triggering it.
Comment 7 Jani Saarinen 2019-05-28 09:41:06 UTC 
This was merged, resolving to get CI feedback if fixed or not.  
https://cgit.freedesktop.org/drm-tip/commit/?id=4361ccac2810553d6cfaa6860bd4bd65f4742ed2

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.