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

### New filters associated

* TGL: igt@i915_pm_rps@(waitboost|reset) - fail - Failed assertion: post_freqs[CUR] < post_freqs[MAX]
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_365/fi-tgl-u/igt@i915_pm_rps@waitboost.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14335/re-tgl-u/igt@i915_pm_rps@reset.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14335/re-tgl-u/igt@i915_pm_rps@waitboost.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@i915_pm_rps@waitboost.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@i915_pm_rps@reset.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@i915_pm_rps@waitboost.html

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

### New filters associated

* TGL: igt@i915_pm_rps@min-max-config-loaded - fail - Failed assertion: freqs[MAX] <= freqs[CUR]
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_366/fi-tgl-u/igt@i915_pm_rps@min-max-config-loaded.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_365/fi-tgl-u/igt@i915_pm_rps@min-max-config-loaded.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@i915_pm_rps@min-max-config-loaded.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14335/re-tgl-u/igt@i915_pm_rps@min-max-config-loaded.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@i915_pm_rps@min-max-config-loaded.html

Bug Assessment : VLK - 4701
 
    • Reproduction rate : 100% (from CI Bug Log) from 6 runs.
    • Last seen 2 days back on TGL systems.
    • pm_rps@min-max-config-load – Subtest to verify the constraints with high load and to check if we can reach max.
    • pm_rps@waitboost – Subtest to verify if we can achieve boost using gem_wait.
    • pm_rps@reset – Subtest to test boost frequency after GPU reset.
    • In this case, the issue seems to be the min-max-config-loaded test that is failing in turn causing the waitboost and reset tests to fails. During the min-max test, the loaded-check expects the current frequency to be greater than the max frequency. The tests fails since this condition is not met. 
    • This condition should be verified. I will continue to follow the issue.

(In reply to sujaritha.sundaresan from comment #3)
> Bug Assessment : VLK - 4701
>  
>     • Reproduction rate : 100% (from CI Bug Log) from 6 runs.
>     • Last seen 2 days back on TGL systems.
>     • pm_rps@min-max-config-load – Subtest to verify the constraints with
> high load and to check if we can reach max.
>     • pm_rps@waitboost – Subtest to verify if we can achieve boost using
> gem_wait.
>     • pm_rps@reset – Subtest to test boost frequency after GPU reset.
>     • In this case, the issue seems to be the min-max-config-loaded test
> that is failing in turn causing the waitboost and reset tests to fails.
> During the min-max test, the loaded-check expects the current frequency to
> be greater than the max frequency. The tests fails since this condition is
> not met. 
>     • This condition should be verified. I will continue to follow the issue.

Thanks for the initial assessment. Once you know the user impact, can you please set the severity of this bug? Currently severity is not set.

*** Bug 111839 has been marked as a duplicate of this bug. ***

GPU clocks on tgl are currently snafu; the HW does not seem to honour our frequency requests.

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

### New filters associated

* TGL:  igt@i915_pm_rps@(min-max-config-idle|waitboost) - fail - Failed assertion: freqs[ACT] == freqs[RPn]
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3617/shard-tglb6/igt@i915_pm_rps@waitboost.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3617/shard-tglb8/igt@i915_pm_rps@min-max-config-idle.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5243/shard-tglb1/igt@i915_pm_rps@min-max-config-idle.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5243/shard-tglb2/igt@i915_pm_rps@waitboost.html

Increasing the loaded wait timeout from 3000 to 3500 resolves this issue and allows the min-max-config-loaded, reset and waitboost tests to pass.

-- 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/413.