All tests - dmesg-warn/dmesg-fail.incomplete - *ERROR* DPCD read failed, address .*

Submitted by Martin Peres @mupuf

Assigned to Swati2 Sharma @swati2.sharma

Link to original bug (#108566)

Description

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_133/fi-apl-guc/igt@gem_workarounds@suspend-resume-context.html

<3> [226.775927] [drm:lspcon_write_infoframe [i915]] ERROR DPCD read failed, address 0x5df
<3> [226.775994] [drm:lspcon_write_infoframe [i915]] ERROR Failed to write AVI infoframes

added CI feature: display/LSPCON platform: BXT platform: KBL priority::high severity::normal + 1 deleted label

Martin Peres @mupuf said:

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_134/fi-apl-guc/igt@gem_softpin@noreloc-s3.html

<3> [178.134601] [drm:lspcon_write_infoframe [i915]] ERROR DPCD read failed, address 0x5df
<3> [178.134699] [drm:lspcon_write_infoframe [i915]] ERROR Failed to write AVI infoframes

Martin Peres @mupuf said:

Also seen on KBL: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5059/shard-kbl7/igt@gem_workarounds@suspend-resume.html

<3> [241.884948] [drm:lspcon_write_infoframe [i915]] ERROR DPCD read failed, address 0x5df
<3> [241.884984] [drm:lspcon_write_infoframe [i915]] ERROR Failed to write AVI infoframes

Martin Peres @mupuf said:

Bumping the priority because the bug is also seen on KBL shards.

CI Bug Log said:

The CI Bug Log issue associated to this bug has been updated.

New filters associated

* KBL: igt@kms_chamelium@hdmi-crc-multiple - dmesg-fail - *ERROR* DPCD read failed
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_168/fi-kbl-7567u/igt@kms_chamelium@hdmi-crc-multiple.html

CI Bug Log said:

A CI Bug Log filter associated to this bug has been updated:

{- APL KBL: igt@(suspend|s3) - dmesg-warn - ERROR DPCD read failed, address -}
{+ APL KBL: igt@(suspend|s3) - dmesg-warn - ERROR DPCD read failed, address +}

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4807/shard-apl4/igt@kms_flip@flip-vs-suspend-interruptible.html

LAKSHMINARAYANA VUDUM @l4kshmi said:

Last seen CI_DRM_5633_full (2 hours, 50 minutes / 2 runs ago)
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5633/shard-apl6/igt@gem_ctx_isolation@bcs0-s3.html

Swati2 Sharma @swati2.sharma said:

May be need to communicate with MCA again for this issue, however for apl need confirmation from Tomi if fw is 1.75.01 or 1.75?
There were 2 fw updates from MCA
1.75 (corrected LT failure)
1.75.01 (corrected DPCD write failure at 0x5c0)
However, for both the fw on hardware page we get fw version as 1.75 only. Can this be modified?

CI Bug Log said:

A CI Bug Log filter associated to this bug has been updated:

{- APL KBL: igt@(suspend|s3) - dmesg-warn - ERROR DPCD read failed, address -}
{+ APL KBL: igt@(suspend|s3) - dmesg-warn - ERROR DPCD read failed, address +}

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4984/shard-apl2/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
  
• https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4985/shard-apl1/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
  
• https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4985/shard-apl5/igt@kms_cursor_crc@pipe-a-cursor-suspend.html

CI Bug Log said:

A CI Bug Log filter associated to this bug has been updated:

{- APL KBL: igt@(suspend|s3) - dmesg-warn - ERROR DPCD read failed, address -}
{+ APL KBL: igt@(suspend|s3) - dmesg-warn / dmesg-fail - ERROR DPCD read failed, address +}

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6285/shard-kbl4/igt@gem_eio@in-flight-suspend.html

CI Bug Log said:

A CI Bug Log filter associated to this bug has been updated:

{- APL KBL: igt@(suspend|s3) - dmesg-warn / dmesg-fail - ERROR DPCD read failed, address -}
{+ APL KBL: igt@(suspend|s3) + random tests - dmesg-warn / dmesg-fail - ERROR DPCD read failed, address +}

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6373/shard-apl5/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html

Vanshidhar Konda said:

This issue is observed multiple times a day on CI runs on APL and KBL machines.

CI Bug Log said:

A CI Bug Log filter associated to this bug has been updated:

{- APL KBL: igt@(suspend|s3) + random tests - dmesg-warn / dmesg-fail - ERROR DPCD read failed, address -}
{+ APL KBL: All tests - dmesg-warn / dmesg-fail - ERROR DPCD read failed, address +}

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7270/shard-apl6/igt@kms_flip@basic-flip-vs-modeset.html

CI Bug Log said:

A CI Bug Log filter associated to this bug has been updated:

{- APL KBL: All tests - dmesg-warn / dmesg-fail - ERROR DPCD read failed, address -}
{+ APL KBL: All tests - dmesg-warn / dmesg-fail - ERROR DPCD read failed, address +}


No new failures caught with the new filter

CI Bug Log said:

The CI Bug Log issue associated to this bug has been updated.

Removed filters

* KBL: igt@kms_chamelium@hdmi-crc-multiple - dmesg-fail - *ERROR* DPCD read failed (added on 10 months, 1 week ago)

assigned to @swati2.sharma

Hi, I have been experiencing this bug for roughly 3 months and the effects are really annoying. I have Xeon E3 1245v (KabyLake) with Arch+KDE constantly updated. After the monitors wake up the screen is frozen, but the mouse is moving and clicks are registered (if I click on Youtube video it will play). If I switch the tty2 (Ctrl+Alt+F2) and back to tty1 the screen is unfrozen and everything works normally until the monitors go to sleep. The issue is usually not present immediately after restart but it appears after a few sleep/wake cycles. The issue has been constant with kernels 5.3 and 5.4 and latest couple of video driver updates. I have the following kernel options enabled in /etc/modprobe.d/i915.conf

options i915 enable_guc=3 # setting value 2 diesn't help options i915.enable_fbc=1 # freame buffer compression

Here are the logs from the event: 29/01/2020 20:58 kernel logitech-hidpp-device 0003:046D:402D.0008: multiplier = 8 29/01/2020 20:58 kernel [drm:lspcon_write_infoframe] *ERROR* Parade FW not ready to accept AVI IF 29/01/2020 20:58 kernel [drm:lspcon_write_infoframe] *ERROR* Failed to write AVI infoframes 29/01/2020 20:58 kernel [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. 29/01/2020 20:58 systemd Started Getty on tty2. 29/01/2020 20:58 audit SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 29/01/2020 20:58 org_kde_powerdevil powerdevil: ACTIVE SESSION PATH CHANGED: "/" 29/01/2020 20:58 kernel audit: type=1130 audit(1580327924.914:178): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 29/01/2020 20:58 org_kde_powerdevil powerdevil: Switched to inactive session - leaving unchanged 29/01/2020 20:58 org_kde_powerdevil powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_31" 29/01/2020 20:58 org_kde_powerdevil powerdevil: Current session is now active 29/01/2020 20:58 kcminit Initializing "kcm_mouse" : "kcminit_mouse"

Please let me know what logs or testing scenarios I can run in order to help with the issue. What logs can help with the solution? Thanks.

Can you please update FW? https://downloadcenter.intel.com/download/29162/HDMI-Firmware-Update-Tool-for-NUC7i3BN-NUC7i5BN-NUC7i7BN

Issue seems to be with Parade LSPCON. [drm:lspcon_write_infoframe] *ERROR* Parade FW not ready to accept AVI IF

Please attach dmesg logs, display info for further debug.

Hi, thanks for the reply. I think the issue is not coming from the chip you suggested. I am using Supermicro MB and according to their diagram the GP -> HDMI converter chip is PS175. Anyway switch my monitors to the DVI and DP ports to avoid potential issues with the conversion chip. I will let you know if the issue is reproduced.

The CI Bug Log issue associated to this bug has been updated by Lakshmi Vudum.

New filters associated

• KBL: igt@gem_exec_schedule@wide-vebox - incomplete - no useful logs
  • https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4328/shard-kbl7/igt@gem_exec_schedule@wide-vebox.html