Bug 111650 - [CI][RESUME] igt@i915_pm_rps@(waitboost|reset) - fail - Failed assertion: post_freqs[CUR] < post_freqs[MAX]
Summary: [CI][RESUME] igt@i915_pm_rps@(waitboost|reset) - fail - Failed assertion: pos...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: sujaritha.sundaresan
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 111839 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-09-11 07:56 UTC by Martin Peres
Modified: 2019-11-11 16:45 UTC (History)
2 users (show)

See Also:
i915 platform: TGL
i915 features: power/runtime PM


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-09-11 07:56:14 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_365/fi-tgl-u/igt@i915_pm_rps@waitboost.html

Starting subtest: waitboost
(i915_pm_rps:993) CRITICAL: Test assertion failure function waitboost, file ../tests/i915/i915_pm_rps.c:608:
(i915_pm_rps:993) CRITICAL: Failed assertion: post_freqs[CUR] < post_freqs[MAX]
(i915_pm_rps:993) CRITICAL: error: 1100 >= 1100
Comment 3 sujaritha.sundaresan 2019-09-16 21:03:04 UTC
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.
Comment 4 Lakshmi 2019-09-17 07:52:49 UTC
(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.
Comment 5 Chris Wilson 2019-09-27 10:04:52 UTC
*** Bug 111839 has been marked as a duplicate of this bug. ***
Comment 6 Chris Wilson 2019-10-04 20:17:47 UTC
GPU clocks on tgl are currently snafu; the HW does not seem to honour our frequency requests.
Comment 8 sujaritha.sundaresan 2019-11-04 22:42:30 UTC
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.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.