Summary: | [CI][SHARDS] igt@i915_pm_sseu@full-enable - fail - Failed assertion: pos != NULL | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | high | CC: | intel-gfx-bugs, lionel.g.landwerlin |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | SKL | i915 features: | power/Other |
Description
Lakshmi
2019-05-03 06:17:58 UTC
@Lionel any help here, this bug is similar to Bug 105400 but occurring on SKL. The CI Bug Log issue associated to this bug has been updated. ### New filters associated * SKL: igt@i915_pm_sseu@full-enable - fail - Failed assertion: pos != NULL - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6024/shard-skl1/igt@i915_pm_sseu@full-enable.html I think there is another bug about this problem (can't remember the number). I left a comment explaining why we should rewrite this test as an i915 self test. Essentially reading the values of the powergating registers from the CPU is racy. These register only contain values after the GPU has run at least a single context. This test fails because we've waken up uncore, but no context has been run on the RCS, leaving the EUs still not powered on (hence 0 values). This is actually an instance of https://bugs.freedesktop.org/show_bug.cgi?id=110584 The effect is the same - same machines affected and we are powergated when we expect not to be, but just a bit more than in the 110584. Because of that we don't even have "Enabled Slice0 subslices:" line in the debugfs. With https://patchwork.freedesktop.org/series/64158/ the error message will change to something more meaningful, maybe even the same as in the other bug. *** This bug has been marked as a duplicate of bug 110584 *** |
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.