Bug 111592 - [CI][RESUME] igt@perf_pmu@.*-bcs0 - incomplete - Spinner not running after 10000.00ms
Summary: [CI][RESUME] igt@perf_pmu@.*-bcs0 - incomplete - Spinner not running after 10...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-09 07:07 UTC by Martin Peres
Modified: 2019-09-17 07:20 UTC (History)
1 user (show)

See Also:
i915 platform: TGL
i915 features: GEM/Other, Perf/PMU


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-09-09 07:07:58 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_362/fi-tgl-u/igt@perf_pmu@render-node-busy-bcs0.html

Starting subtest: render-node-busy-bcs0
(perf_pmu:1194) WARNING: Spinner not running after 250.00ms
(perf_pmu:1194) WARNING: Spinner not running after 500.00ms
(perf_pmu:1194) WARNING: Spinner not running after 750.00ms
(perf_pmu:1194) WARNING: Spinner not running after 1000.00ms
(perf_pmu:1194) WARNING: Spinner not running after 1250.00ms
(perf_pmu:1194) WARNING: Spinner not running after 1500.00ms
(perf_pmu:1194) WARNING: Spinner not running after 1750.00ms
(perf_pmu:1194) WARNING: Spinner not running after 2000.00ms
(perf_pmu:1194) WARNING: Spinner not running after 2250.00ms
(perf_pmu:1194) WARNING: Spinner not running after 2500.00ms
(perf_pmu:1194) WARNING: Spinner not running after 2750.00ms
(perf_pmu:1194) WARNING: Spinner not running after 3000.00ms
[...]
(perf_pmu:1194) WARNING: Spinner not running after 684750.03ms
(perf_pmu:1194) WARNING: Spinner not running after 685000.03ms
(perf_pmu:1194) WARNING: Spinner not running after 685250.03ms
(perf_pmu:1194) WARNING: Spinner not running after 685500.03ms
(perf_pmu:1194) WARNING: Spinner not running after 685750.03ms

And while you are at it, please fix the test so as it bails out after 10s, not 10 minutes ;)
Comment 2 Chris Wilson 2019-09-09 07:13:41 UTC
https://patchwork.freedesktop.org/series/66405/
Comment 3 Tvrtko Ursulin 2019-09-09 09:20:22 UTC
Patch to cap the timeout reviewed, but root case of why this doesn't work still remains of course.
Comment 4 Chris Wilson 2019-09-09 09:30:27 UTC
The hang is in the context restore, our initial context setup is still suspect.
Comment 5 Chris Wilson 2019-09-09 09:40:20 UTC
Immediate problem fixed,

commit 7ab426dcb98b973e36ebd050ba5c5ebb6bd67d39
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Sep 9 08:09:20 2019 +0100

    i915/perf_pmu: Check on the health of the spinner while waiting
    
    And give up if we never even make it to the start.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111592
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

The underlying problem I think is the same as bug 111597
Comment 6 CI Bug Log 2019-09-17 07:19:42 UTC
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.
Comment 7 Martin Peres 2019-09-17 07:20:22 UTC
(In reply to Chris Wilson from comment #5)
> Immediate problem fixed,
> 
> commit 7ab426dcb98b973e36ebd050ba5c5ebb6bd67d39
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Mon Sep 9 08:09:20 2019 +0100
> 
>     i915/perf_pmu: Check on the health of the spinner while waiting
>     
>     And give up if we never even make it to the start.
>     
>     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111592
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>     Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> 
> The underlying problem I think is the same as bug 111597

Looks good, thanks!


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.