Check if it is still in BAT

reproduced:

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4056/fi-ilk-m540/igt@gem_exec_suspend@basic-s3.html

setting priority to high since it is ILK

This issue occurred 3 months ago last time ago. Before that, it used to occur once in a week. With CI DRM the occurrence gap was 200 rounds or 1 month gap. So, we keep this bug open for few more weeks or at least 1 month, then this bug can think of closing this bug.

I have observed similar issue on ICL H/W while running IGT ./ksm_psr.
ICL H/W never came up after suspend.

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* fi-ilk-650: suspend tests - incomplete
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_213/fi-ilk-650/igt@kms_cursor_crc@cursor-256x256-suspend.html

A CI Bug Log filter associated to this bug has been updated:

{- fi-ilk-650: suspend tests - incomplete -}
{+ fi-ilk-650: suspend tests - incomplete +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_217/fi-ilk-650/igt@kms_flip@2x-flip-vs-suspend.html

Other than the systems just dying, I'm not sure how these last two failures are related. (1) Crashes waking up from S3, but (2) wakes up completely only to die later on.

The logs in comments #1,2 are not accessible.


 
(1)
"<6>[  310.084205] ACPI: Waking up from system sleep state S3"
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_217/fi-ilk-650/dmesg25.log

(2)
"<7>[  176.693274] [drm:verify_single_dpll_state.isra.105 [i915]] PCH DPLL A"
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_213/fi-ilk-650/dmesg6.log

This appears to be isolated to ICL and it occurs after suspend tests. One run doesn’t seem to come out of suspend, while the later comes out but resets later on down the road.

I wonder if it might be the watchdog kicking in too early, or not being kicked in time to prevent a reset.

(In reply to Don Hiatt from comment #8)
> This appears to be isolated to ICL and it occurs after suspend tests. One
> run doesn’t seem to come out of suspend, while the later comes out but
> resets later on down the road.
> 
> I wonder if it might be the watchdog kicking in too early, or not being
> kicked in time to prevent a reset.

Meant to say, ILK.

This has not been seeing for over 33 days, dropping priority and will monitor.

Closing as this bug has not been seen in well over 3 months.

Thanks, it indeed looks like has been fixed.

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.