Summary: | [CI] igt@perf_pmu@busy-vcs0 - fail - Failed assertion: (double)(val) <= (1.0 + (tolerance)) * (double)(flags & (1) ? slept : 0.f) && (double)(val) >= (1.0 - (tolerance)) * (double)(flags & (1) ? slept : 0.f) | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | SNB | i915 features: | Perf/PMU |
Description
Martin Peres
2018-02-28 10:09:00 UTC
We think this should be fixed by commit d502f055ac4500cada758876a512ac4f14b34851 Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Date: Wed Apr 4 10:51:52 2018 +0100 tests/perf_pmu: Avoid RT thread for accuracy test Realtime scheduling interferes with execlists submission (tasklet) so try to simplify the PWM loop in a few ways: * Drop RT. * Longer batches for smaller systematic error. * More truthful test duration calculation. * Less clock queries. * No self-adjust - instead just report the achieved cycle and let the parent check against it. * Report absolute cycle error. No changes... We still see the problem every single run... Lots more tuning of the test since. (In reply to Chris Wilson from comment #3) > Lots more tuning of the test since. Not seen since drmtip_56 (3 months / 49 runs ago). Closing! |
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.