https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6954/shard-skl10/igt@perf@gen8-unprivileged-single-ctx-counters.html Starting subtest: gen8-unprivileged-single-ctx-counters (perf:3209) CRITICAL: Test assertion failure function __perf_open, file ../tests/perf.c:239: (perf:3209) CRITICAL: Failed assertion: ret >= 0 (perf:3209) CRITICAL: Last errno: 12, Cannot allocate memory Subtest gen8-unprivileged-single-ctx-counters failed.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * SKL: igt@perf@gen8-unprivileged-single-ctx-counters - dmesg-fail - Failed assertion: ret >= 0, Cannot allocate memory - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6954/shard-skl10/igt@perf@gen8-unprivileged-single-ctx-counters.html
*** Bug 111824 has been marked as a duplicate of this bug. ***
A CI Bug Log filter associated to this bug has been updated: {- SKL: igt@perf@gen8-unprivileged-single-ctx-counters - dmesg-fail - Failed assertion: ret >= 0, Cannot allocate memory -} {+ SKL KBL: igt@perf@gen8-unprivileged-single-ctx-counters - dmesg-fail - Failed assertion: ret >= 0, Cannot allocate memory +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_379/fi-kbl-soraka/igt@perf@gen8-unprivileged-single-ctx-counters.html
The test captures counter snapshots using MI RPC before and after a few render workloads. The batch consisting of the MI-RPC also does a PIPE_FLUSH and reads/stores the TIMESTAMP value from the render timestamp register. Since there may be a context switch during the execution of these workloads, the test also collects reports from the OA buffer between the OA timestamps collected from the MI RPCs. Is uses all these reports to calculate the actual delta between the counters A0, A21 and A26. The delta of the counters is expected to be a certain fixed value for the render copy performed. The failure is likely from a large deviance between "timestamp delta from MI RPC OA timestamps" and "timestamp delta between render timestamps collected along with MI-RPC". The large deviance causes the test to try again. Every time the test tries again, it allocates some resources. Eventually results in OOM. Machines: skl, kbl Repro rate: 5% Impact: Accuracy of perf snapshots from MI-RPC Severity: Medium Pririty: High
-- 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/452.
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.