[Intel-gfx] ✗ Fi.CI.IGT: warning for igt/core_suspend: Exercise igt_system_suspend_autoresume()
Imre Deak
imre.deak at intel.com
Mon Oct 16 10:43:33 UTC 2017
On Mon, Oct 16, 2017 at 11:34:03AM +0100, Chris Wilson wrote:
> Quoting Patchwork (2017-10-16 11:30:46)
> > == Series Details ==
> >
> > Series: igt/core_suspend: Exercise igt_system_suspend_autoresume()
> > URL : https://patchwork.freedesktop.org/series/31986/
> > State : warning
> >
> > == Summary ==
> >
> > Test kms_frontbuffer_tracking:
> > Subgroup fbc-rgb101010-draw-mmap-gtt:
> > skip -> PASS (shard-hsw)
> > Test core_suspend:
> > Subgroup suspend-freze-processors:
> > notrun -> INCOMPLETE (shard-hsw)
> > Subgroup suspend-freze-core:
> > notrun -> INCOMPLETE (shard-hsw)
>
> Looks like we are not parsing the available debug modes correctly:
>
> <4>[ 487.523649] PM: Unsupported test mode for suspend to idle, please choose none/freezer/devices/platform.
> <6>[ 487.523657] PM: suspend exit
> <6>[ 487.523683] PM: suspend entry (s2idle)
>
> i.e. neither processors or core are available, and repeats ad nauseam.
As I recall only the available suspend states can be queried, for that
you may want to use get_supported_suspend_states(). As for the test
mode, maybe just hard-wire not use the invalid combinations?
--Imre
> -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
More information about the Intel-gfx
mailing list