Summary: | [CI][BAT] igt@i915_pm_rpm@pc8-residency - fail - Machine is not reaching PC8+ states, please check its configuration. | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | KBL | i915 features: | power/runtime PM |
Description
Martin Peres
2019-04-29 10:51:44 UTC
Setting the priority to medium since this is only impacting the power consumption. The CI Bug Log issue associated to this bug has been updated. ### New filters associated * KBL: igt@i915_pm_rpm@pc8-residency - fail - Machine is not reaching PC8+ states, please check its configuration. - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2931/fi-kbl-7567u/igt@i915_pm_rpm@pc8-residency.html A CI Bug Log filter associated to this bug has been updated: {- KBL: igt@i915_pm_rpm@pc8-residency - fail - Machine is not reaching PC8+ states, please check its configuration. -} {+ KBL: igt@i915_pm_rpm@*pc8* - fail - Machine is not reaching PC8+ states, please check its configuration. +} No new failures caught with the new filter A CI Bug Log filter associated to this bug has been updated: {- KBL: igt@i915_pm_rpm@*pc8* - fail - Machine is not reaching PC8+ states, please check its configuration. -} {+ SKL KBL: igt@i915_pm_rpm@*pc8* - fail - Machine is not reaching PC8+ states, please check its configuration. +} No new failures caught with the new filter No failures are under this bug in CI bug log since the first failure which occurred 3 months ago. Closing this issue as WORKSFORME. 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. |
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.