[CI][SHARDS][TGL] suspend tests - incomplete
Submitted by LAKSHMINARAYANA VUDUM @l4kshmi
Assigned to Sujaritha Sundaresan @sujaritha
Link to original bug (#111850)
Description
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6960/shard-tglb3/igt@gem_eio@suspend.html
<6>
[367.327666] Console: switching to colour dummy device 80x25
<6>
[367.327702] [IGT] gem_eio: executing
<5>
[367.330390] Setting dangerous option reset - tainting kernel
<5>
[367.330463] Setting dangerous option reset - tainting kernel
<6>
[367.330846] i915 0000:00:02.0: GPU HANG: ecode 12:57:0x00000000, Manually set wedged engine mask = ffffffffffffffff
<6>
[367.330890] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
<6>
[367.330891] Please file a new bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Depends on
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Bugzilla Migration User added CI feature: GEM feature: power/suspend-resume platform: TGL priority::medium severity::major + 1 deleted label
added CI feature: GEM feature: power/suspend-resume platform: TGL priority::medium severity::major + 1 deleted label
CI Bug Log said:The CI Bug Log issue associated to this bug has been updated.
New filters associated
* TGL: igt@gem_eio@suspend - incomplete - GPU HANG: ecode 12:57:0x00000000, Manually set wedged engine mask = ffffffffffffffff
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6960/shard-tglb3/igt@gem_eio@suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6961/shard-tglb2/igt@gem_eio@suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6962/shard-tglb1/igt@gem_eio@suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6963/shard-tglb2/igt@gem_eio@suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6964/shard-tglb2/igt@gem_eio@suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6966/shard-tglb2/igt@gem_eio@suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6967/shard-tglb3/igt@gem_eio@suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6969/shard-tglb1/igt@gem_eio@suspend.html CI Bug Log said:The CI Bug Log issue associated to this bug has been updated.
New filters associated
* TGL: igt@gem_eio@suspend - incomplete - PM: suspend entry (s2idle)
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6963/re-tgl1-display/igt@gem_eio@suspend.html Chris Wilson@ickle
said:tgl suspend being broken is a common theme.
Please note the GPU hang here is part of the test and incidental. CI Bug Log said:A CI Bug Log filter associated to this bug has been updated:
TGL: igt@gem_eio@suspend - incomplete - GPU HANG: ecode 12:57:0x00000000, Manually set wedged engine mask = ffffffffffffffff
TGL: igt@gem_eio@suspend - incomplete
No new failures caught with the new filter CI Bug Log said:The CI Bug Log issue associated to this bug has been updated.
Removed filters
* TGL: igt@gem_eio@suspend - incomplete - PM: suspend entry (s2idle) (added on 2 hours ago) CI Bug Log said:A CI Bug Log filter associated to this bug has been updated:
TGL: igt@gem_eio@suspend - incomplete
TGL: suspend tests - incomplete
New failures caught by the filter:
CI Bug Log said:A CI Bug Log filter associated to this bug has been updated:
TGL: suspend tests - incomplete
TGL: suspend tests - incomplete
New failures caught by the filter:
Francesco Balestrieri@baleboy
said:Suspend tests are not a priority at this moment, so while the impact is major, I'm prioritizing to medium.
CI Bug Log said:A CI Bug Log filter associated to this bug has been updated:
TGL: suspend tests - incomplete
TGL: suspend tests - incomplete
No new failures caught with the new filter CI Bug Log said:A CI Bug Log filter associated to this bug has been updated:
TGL: suspend tests - incomplete
TGL: suspend tests - incomplete
New failures caught by the filter:
-
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5211/shard-tglb3/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7001/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7002/shard-tglb2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7003/shard-tglb1/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7005/shard-tglb5/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7006/shard-tglb8/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7009/shard-tglb7/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7009/shard-tglb8/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5215/shard-tglb5/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5211/shard-tglb3/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
CI Bug Log said:A CI Bug Log filter associated to this bug has been updated:
TGL: suspend tests - incomplete
TGL: suspend tests - incomplete
New failures caught by the filter:
-
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5229/shard-tglb1/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5229/shard-tglb7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-d-planes.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7094/shard-tglb5/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-d-planes.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5231/shard-tglb1/igt@kms_cursor_crc@pipe-d-cursor-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7095/shard-tglb3/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7096/shard-tglb1/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7098/shard-tglb1/igt@kms_cursor_crc@pipe-d-cursor-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7098/shard-tglb1/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7099/shard-tglb7/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
-
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5229/shard-tglb1/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
- Bugzilla Migration User assigned to @sujaritha
assigned to @sujaritha
- Jon Ewins added feature: display/Other label
added feature: display/Other label
This bug and #456 (closed) are both being used to track the same signatures. The most recent in both cases sees the suspend and resume complete, but a WARNING taints the testing. In each case there are two warnings seen. The first is that a wakeref is still being held by the display code, possibly related to the snd_hda driver: <4>[ 566.469665] i915 raw-wakerefs=1 wakelocks=1 on cleanup <4>[ 566.469702] WARNING: CPU: 7 PID: 6632 at drivers/gpu/drm/i915/intel_runtime_pm.c:602 intel_runtime_pm_driver_release+0x27/0x40 [i915] <4>[ 566.469703] Modules linked in: snd_hda_intel i915 vgem snd_hda_codec_hdmi mei_hdcp x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul cdc_ether usbnet mii ghash_clmulni_intel snd_intel_dspcfg snd_hda_codec snd_hwdep snd_hda_core e1000e mei_me snd_pcm mei ptp pps_core intel_lpss_pci prime_numbers [last unloaded: i915]
The full dmesg shows the list of wakeref users, all in display paths for this display test.
The second warning happens when a wakeref put is done (not sure if its the missing one from before) which is not on the intel_wakeref_t debug tracking stack.
Therefore I recommend we close either this bug or 456. Adding display/Other component.
Collapse replies - Reporter
Issue related to the warning "i915 raw-wakerefs=1 wakelocks=1 on cleanup" is tracked under #1602 (closed). I will close and archive this issue as a duplicate of #456 (closed).
- Jon Ewins mentioned in issue #456 (closed)
mentioned in issue #456 (closed)
- LAKSHMINARAYANA VUDUM closed
closed
- Reporter
The CI Bug Log issue associated to this bug has been archived.
New failures matching the above filters will not be associated to this bug anymore.