Summary: | [CI][SHARDS] : igt@kms_busy@extended-modeset-hang-oldfb-render-a - dmesg-warn- *ERROR* DPCD write failed at:0x5c0, *ERROR* Failed to write AVI infoframes | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | minor | ||
Priority: | low | CC: | intel-gfx-bugs, shashank.sharma, swati2.sharma |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | KBL | i915 features: | display/LSPCON |
Description
Lakshmi
2019-09-20 11:39:43 UTC
(In reply to Lakshmi from comment #0) > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6925/shard-kbl2/ > igt@kms_busy@extended-modeset-hang-oldfb-render-a.html > > <3> [365.882373] [drm:lspcon_write_infoframe [i915]] *ERROR* DPCD write > failed at:0x5c0 > <3> [365.882409] [drm:lspcon_write_infoframe [i915]] *ERROR* Failed to write > AVI infoframes Component is let to LSPCON, please revert back if it's incorrect. The CI Bug Log issue associated to this bug has been updated. ### New filters associated * KBL: igt@kms_busy@extended-modeset-hang-oldfb-render-a - dmesg-warn- *ERROR* DPCD write failed at:0x5c0, *ERROR* Failed to write AVI infoframes - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6925/shard-kbl2/igt@kms_busy@extended-modeset-hang-oldfb-render-a.html This error has occurred only once on one KBL platform. The warning is that writing to the LSPCON register failed despite multiple retries. Setting the priority to low for now because the error has only been seen once. -- 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/437. |
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.