Starting subtest: module-reload
(i915_pm_rpm:3968) CRITICAL: Test assertion failure function drm_resources_equal_subtest, file ../tests/i915/i915_pm_rpm.c:907:
(i915_pm_rpm:3968) CRITICAL: Failed assertion: wait_for_suspended()
The CI Bug Log issue associated to this bug has been updated.
### New filters associated
* SKL: igt@i915_pm_rpm@module-reload - fail - Failed assertion: wait_for_suspended()
This also seen once 1,5 months ago, Should this be highest?
(In reply to Jani Saarinen from comment #2)
> This also seen once 1,5 months ago, Should this be highest?
Setting the priority to not set. This issue occurred only once on CI_DRM_6425_55 (1 month, 3 weeks old).
This failure has occurred three times in the past 4 months. The last two occurrences of the failure have happened in the past 2 weeks. The number of runs between when this failure happened has reduced as well (7-11 runs vs 547 runs for the 1st occurrence).
The failure is that the system failed to be suspended (within timeout period) despite the graphics device entering D3 state after disabling all screens.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/336.