Bug 108059

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

### New filters associated

* ICL: igt@pm_rps@min-max-config-loaded - Failed assertion: freqs[MAX] <= freqs[CUR] (No new failures associated)

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

### New filters associated

* ICL:  igt@pm_rps@.* - Failed assertion: boost_freqs[CUR] == boost_freqs[BOOST] (No new failures associated)

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

Will be fixed once https://patchwork.freedesktop.org/series/59278/ is merged.

commit 917dc6b53c273dd7e026f158ad4894ae366da326 (HEAD -> drm-intel-next-queued, 
drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Date:   Wed Apr 10 13:59:22 2019 +0300

    drm/i915: Use Engine1 instance for gen11 pm interrupts
    
    With gen11 the interrupt registers are shared between 2 engines,
    with Engine1 instance being upper word and Engine0 instance being
    lower. Annoyingly gen11 selected the pm interrupts to be in the
    Engine1 instance.
    
    Rectify the situation by shifting the access accordingly,
    based on gen.
    
    v2: comments, warn on overzealous rps_events
    
    Bugzilla: https://bugzilla.freedesktop.org/show_bug.cgi?id=108059
    Testcase: igt/i915_pm_rps@min-max-config-loaded
    Cc: Chris Wilson <chris@chris-wilson.co.uk>
    Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Link: https://patchwork.freedesktop.org/patch/msgid/20190410105923.18546-6-mika.kuoppala@linux.intel.com

Reopening this issue as there are new occurrences. Here are the latest failures where logs are available

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6706/shard-iclb2/igt@i915_pm_rps@min-max-config-loaded.html

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.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6650/shard-iclb1/igt@i915_pm_rps@reset.html

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.
**** DEBUG ****

(In reply to Lakshmi from comment #6)
> Reopening this issue as there are new occurrences. Here are the latest
> failures where logs are available
> 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6706/shard-iclb2/
> igt@i915_pm_rps@min-max-config-loaded.html
> 
> 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.
> 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6650/shard-iclb1/
> igt@i915_pm_rps@reset.html
> 
> 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.
> **** DEBUG ****

Adding Chris here.

This smells like a new bug to me. I would open a new one. Chris?

It's certainly not the same bug and it misbehaved on a few machines, then corrected itself again. It's a relatively noisy test that I am not too worried about -- there are a lot of scheduling factors at play with it being a worker, so long as the debugfs show that we were setting the right flags, I can be responsibly reassured. Doesn't speak well of the boost from a QoS pov though.

Bug 111409 is created to track these failures (Comment 6). Closing this bug.

Last seen original issue 4 months ago ( igt@pm_rps@min-max-config-loaded - Failed assertion: freqs[MAX] <= freqs[CUR]), until then the reproduction rate was 100%. Closing this issue as Fixed.

A separate bug 111409 is created to track other issues.

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

New failures matching the above filters will not be associated to this bug anymore.