Bug 111409 - [CI][SHARDS]igt@i915_pm_rps@* - fail - Failed assertion: freqs[MAX] <= freqs[CUR]|Failed assertion: boost_freqs[CUR] == boost_freqs[BOOST]
Summary: [CI][SHARDS]igt@i915_pm_rps@* - fail - Failed assertion: freqs[MAX] <= freqs[...
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: low normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Whiteboard: ReadyForDev
Depends on:
Reported: 2019-08-16 06:41 UTC by Lakshmi
Modified: 2019-11-29 19:23 UTC (History)
1 user (show)

See Also:
i915 platform: ICL
i915 features: power/Other


Description Lakshmi 2019-08-16 06:41:58 UTC
Starting subtest: min-max-config-loaded
(i915_pm_rps:2348) CRITICAL: Test assertion failure function loaded_check, file ../tests/i915/i915_pm_rps.c:503:
(i915_pm_rps:2348) CRITICAL: Failed assertion: freqs[MAX] <= freqs[CUR]
(i915_pm_rps:2348) CRITICAL: Last errno: 2, No such file or directory
(i915_pm_rps:2348) CRITICAL: error: 1050 > 1017
Subtest min-max-config-loaded failed.

Starting subtest: reset
(i915_pm_rps:1153) CRITICAL: Test assertion failure function waitboost, file ../tests/i915/i915_pm_rps.c:607:
(i915_pm_rps:1153) CRITICAL: Failed assertion: boost_freqs[CUR] == boost_freqs[BOOST]
(i915_pm_rps:1153) CRITICAL: error: 450 != 1050
Subtest reset failed.
Comment 1 Lakshmi 2019-08-16 06:48:55 UTC
Above failures are captured under Bug 108059 in CI buglog. Since these are not part of Bug 108059, this issue is is created.
Comment 2 CI Bug Log 2019-08-16 06:52:54 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@i915_pm_rps@min-max-config-loaded - fail - Failed assertion: freqs[MAX] &lt;= freqs[CUR]
  (No new failures associated)

* ICL: igt@i915_pm_rps@reset - fail - Failed assertion: boost_freqs[CUR] == boost_freqs[BOOST]
  (No new failures associated)
Comment 3 Don Hiatt 2019-09-12 21:02:47 UTC
The test min-max-config ("tests/i915/i915_pm_rps.c") is attempting to boost the frequency to the maximum value. It compares the current frequency with the max and in this case the system is never getting to the maximum frequency and exits with the assert.

This appears to only be happening on the shard-iclb systems starting with CI_DRM_6747_full (3 weeks, 1 day old) up until CI_DRM_6753_full (3 weeks old).

However, all runs since -- CI_DRM_6754_full (3 weeks old) until CI_DRM_6877_full (1 hour, 18 minutes old) are passing.
(filter="test_name='igt@i915_pm_rps@min-max-config-loaded' AND machine_name ICONTAINS 'shard-iclb'")

This issue seems to be resolved, we should continue to monitor. Adjusting severity to medium/normal.
Comment 4 Martin Peres 2019-11-29 19:23:33 UTC
-- 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/370.

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.