Bug 110741 - [CI][SHARDS] igt@kms_cursor_crc@pipe-[abc]-cursor-suspend - incomplete - ACPI: EC: interrupt blocked
Summary: [CI][SHARDS] igt@kms_cursor_crc@pipe-[abc]-cursor-suspend - incomplete - ACPI...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-23 14:02 UTC by Martin Peres
Modified: 2019-11-08 19:32 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: display/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-05-23 14:02:42 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6118/shard-skl3/igt@kms_cursor_crc@pipe-c-cursor-suspend.html

<7> [718.847428] [drm:skl_enable_dc6 [i915]] Enabling DC6
<7> [718.847697] [drm:gen9_set_dc_state [i915]] Setting DC state from 00 to 02
<7> [718.848329] [drm:intel_power_well_disable [i915]] disabling always-on
<7> [718.848793] [drm:gen9_set_dc_state [i915]] Setting DC state from 02 to 00
<7> [718.849575] [drm:intel_power_well_disable [i915]] disabling power well 1
<7> [718.849768] [drm:hsw_wait_for_power_well_disable.isra.14 [i915]] power well 1 forced on (bios:1 driver:0 kvmr:0 debug:0)
<7> [718.862765] i915 Wakeref last acquired:
   track_intel_runtime_pm_wakeref+0x1b/0xb0 [i915]
   intel_display_power_get+0x1d/0x60 [i915]
   intel_atomic_commit_tail+0x1031/0x1340 [i915]
   intel_atomic_commit+0x240/0x2e0 [i915]
   drm_atomic_helper_set_config+0x7b/0x90
   drm_mode_setcrtc+0x199/0x710
   drm_ioctl_kernel+0x83/0xf0
   drm_ioctl+0x2f3/0x3b0
<7> [718.864540] i915 Wakeref last released:
   __untrack_all_wakerefs+0x67/0x70 [i915]
   __intel_wakeref_dec_and_check_tracking+0x68/0x90 [i915]
   __intel_runtime_pm_put+0x143/0x2a0 [i915]
   intel_pin_and_fence_fb_obj+0xd1/0x150 [i915]
   intel_plane_pin_fb+0x3c/0xd0 [i915]
   intel_prepare_plane_fb+0x1d2/0x5e0 [i915]
   drm_atomic_helper_prepare_planes+0x82/0x100
   intel_atomic_commit+0xad/0x2e0 [i915]
<7> [718.864554] i915 Wakeref count: 7
<7> [718.865840] i915 Wakeref x4 taken at:
   track_intel_runtime_pm_wakeref+0x1b/0xb0 [i915]
   intel_display_power_get+0x1d/0x60 [i915]
   modeset_get_crtc_power_domains+0x117/0x130 [i915]
   intel_atomic_commit_tail+0xd9/0x1340 [i915]
   intel_atomic_commit+0x240/0x2e0 [i915]
   drm_atomic_helper_set_config+0x7b/0x90
   drm_mode_setcrtc+0x199/0x710
   drm_ioctl_kernel+0x83/0xf0
<7> [718.867938] i915 Wakeref x1 taken at:
   track_intel_runtime_pm_wakeref+0x1b/0xb0 [i915]
   intel_display_power_get+0x1d/0x60 [i915]
   intel_ddi_pre_pll_enable+0x5e/0x200 [i915]
   intel_encoders_pre_pll_enable.isra.19+0x61/0x80 [i915]
   haswell_crtc_enable+0x5c/0x750 [i915]
   intel_update_crtc+0x51/0x3c0 [i915]
   skl_update_crtcs+0x266/0x2b0 [i915]
   intel_atomic_commit_tail+0x205/0x1340 [i915]
<7> [718.870026] i915 Wakeref x1 taken at:
   track_intel_runtime_pm_wakeref+0x1b/0xb0 [i915]
   intel_display_power_get+0x1d/0x60 [i915]
   intel_ddi_pre_enable+0x121/0xb70 [i915]
   intel_encoders_pre_enable.isra.20+0x61/0x80 [i915]
   haswell_crtc_enable+0x82/0x750 [i915]
   intel_update_crtc+0x51/0x3c0 [i915]
   skl_update_crtcs+0x266/0x2b0 [i915]
   intel_atomic_commit_tail+0x205/0x1340 [i915]
<7> [718.871600] i915 Wakeref x1 taken at:
   track_intel_runtime_pm_wakeref+0x1b/0xb0 [i915]
   intel_display_power_get+0x1d/0x60 [i915]
   edp_panel_vdd_on+0xd5/0x210 [i915]
   intel_dp_aux_xfer+0xac/0x8c0 [i915]
   intel_dp_aux_transfer+0x124/0x200 [i915]
   drm_dp_dpcd_access+0x76/0x110
   drm_dp_dpcd_write+0x21/0x90
   intel_dp_sink_dpms+0x4f/0x100 [i915]
<6> [718.886225] ACPI: EC: interrupt blocked
Comment 1 CI Bug Log 2019-05-23 14:03:32 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@kms_cursor_crc@pipe-[abc]-cursor-suspend - incomplete - ACPI: EC: interrupt blocked
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13018/shard-skl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13022/shard-skl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13031/shard-skl5/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13037/shard-skl5/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6116/shard-skl6/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6118/shard-skl3/igt@kms_cursor_crc@pipe-c-cursor-suspend.html

* SKL: igt@kms_cursor_crc@pipe-[abc]-cursor-suspend - incomplete
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4993/shard-skl8/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6095/shard-skl2/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6110/shard-skl8/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl5/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13065/shard-skl9/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
Comment 2 Vanshidhar Konda 2019-11-08 19:32:47 UTC
This issue occurs multiple times everyday on SKL machines. No other machines were noted as failing with the kms_cursor_crc@pipe-[abc]-cursor-suspend tests. TGL errors are being tracked by another bug.

The ACPI: EC: interrupt blocked line in the logs occurs even during successful runs. This line is indicating that the system is getting ready to enter suspend to RAM (S3) state. The actual error is only that the test is "incomplete".

There are 2 kinds of failures captured by this bug/filter. One is that the machine just resumes from S3 and then fails. The other is that the machine even fails to enter S3.


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.