Bug 102404 - [BAT][BXT] loads of "*ERROR* Video mode command 0x00000041 send failed" when using a DSI panel
Summary: [BAT][BXT] loads of "*ERROR* Video mode command 0x00000041 send failed" when ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: highest critical
Assignee: Mika Kahola
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-25 10:30 UTC by Martin Peres
Modified: 2017-09-18 13:22 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features: display/DSI


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2017-08-25 10:30:29 UTC
A lot of tests generate the following dmesg warning on the machine fi-bxt-dsi (Broxton with a DSI panel attached) when running IGT:

[  543.401377] [drm:dpi_send_cmd.constprop.5 [i915]] *ERROR* Video mode command 0x00000041 send failed.

Full logs:
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-a.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c-frame-sequence.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@hang-read-crc-pipe-c.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_frontbuffer_tracking@basic.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@gem_exec_suspend@basic-s4-devices.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-flip-before-cursor-varying-size.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_busy@basic-flip-c.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-flip-before-cursor-atomic.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-c-frame-sequence.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@gem_exec_suspend@basic-s3.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_flip@basic-flip-vs-dpms.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@hang-read-crc-pipe-a.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@pm_rpm@basic-rte.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_flip@basic-flip-vs-wf_vblank.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-b.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@pm_rpm@basic-pci-d3-state.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-c.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_busy@basic-flip-b.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_busy@basic-flip-a.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@hang-read-crc-pipe-b.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_flip@basic-plain-flip.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@drv_module_reload@basic-reload-inject.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_flip@basic-flip-vs-modeset.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3001/fi-bxt-dsi/igt@drv_module_reload@basic-reload.html
Comment 1 Jani Saarinen 2017-09-01 07:25:47 UTC
Fix in wip: https://patchwork.freedesktop.org/series/29589/
Mika, please comment.
Comment 2 Mika Kahola 2017-09-01 07:52:54 UTC
Patches are now sent to intel-gfx mailing list for review

https://patchwork.kernel.org/patch/9933703/
https://patchwork.kernel.org/patch/9933701/
Comment 3 Vidya Srinivas 2017-09-05 09:52:34 UTC
The issue is happening due to Device Ready setting. It was added to resolve a DSI split screen issue in  dual link DSI panels. Since DSI dual link is not enabled and will require a bit of work in upstream, we should revert this change.

SHUTDOWN is a short packet peripheral command that turns off the display in a Video Mode display module for power saving. 

We have submitted a patch for the same reverting the change.
https://patchwork.kernel.org/patch/9938311/

This should solve the issue. We will continue to work on enabling the dual link support in upstream and handle the respective changes then.
Comment 4 Mika Kahola 2017-09-05 10:39:37 UTC
I tested this with APL+MIPI/DSI single link combo. The patch solved the issue on my setup.
Comment 7 Jani Saarinen 2017-09-13 09:24:39 UTC
Working on CI.


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.