Bug 103313 - [CI] [KBL only] igt@* - dmesg-warn - *ERROR* LSPCON mode hasn't settled
Summary: [CI] [KBL only] igt@* - dmesg-warn - *ERROR* LSPCON mode hasn't settled
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high normal
Assignee: shashank.sharma@intel.com
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks: 103558 105979
  Show dependency treegraph
 
Reported: 2017-10-17 12:09 UTC by Marta Löfstedt
Modified: 2018-12-04 13:29 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features: display/LSPCON


Attachments
kern_log_KBL_FF (16.63 MB, text/plain)
2017-12-20 17:28 UTC, Elizabeth
no flags Details
i915_display_info (7.52 KB, text/plain)
2017-12-20 17:42 UTC, Elizabeth
no flags Details
LSPCON FW V1.70 (210.53 KB, application/x-rar)
2017-12-27 16:52 UTC, shashank.sharma@intel.com
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marta Löfstedt 2017-10-17 12:09:40 UTC
CI_DRM_3249 KBL-shards igt@kms_cursor_crc@cursor-64x64-suspend

[   53.844731] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[   53.950809] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[   53.950870] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[   54.294332] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3249/shard-kbl6/igt@kms_cursor_crc@cursor-64x64-suspend.html

I am aware that we just closed BUG 102295. 
However, I create a new one to not confuse ourselved with data from before BUG 102295.

ALso, this appear to be quite rare. I just happened to stumble onto it since the issue is covered by other bugs on KBL-shards.
Comment 1 Marta Löfstedt 2017-10-23 12:32:40 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3275/shard-kbl7/igt@gem_exec_async@concurrent-writes-bsd2.html

[  152.195804] Setting dangerous option reset - tainting kernel
[  152.416988] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  152.537561] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  152.537766] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  152.586477] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  152.586776] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
Comment 2 Marta Löfstedt 2017-10-23 12:37:49 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3275/shard-kbl7/igt@pm_rpm@cursor-dpms.html

[  114.253077] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  114.298110] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Comment 3 Marta Löfstedt 2017-10-23 12:38:10 UTC
	https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3275/shard-kbl7/igt@kms_busy@extended-modeset-hang-newfb-render-C.html


[  250.358807] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  250.477625] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  250.477744] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  250.526598] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  250.526829] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
[  250.742333] Setting dangerous option reset - tainting kernel
[  250.743475] Setting dangerous option reset - tainting kernel
[  250.744560] Setting dangerous option reset - tainting kernel
[  251.264218] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  251.307663] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  251.308061] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
[  251.632961] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Comment 4 Marta Löfstedt 2017-10-23 12:38:30 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3275/shard-kbl7/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-A.html

	

[  117.120756] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  117.237093] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  117.237197] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  117.683960] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                 TDH                  <0>
                 TDT                  <2>
                 next_to_use          <2>
                 next_to_clean        <0>
               buffer_info[next_to_clean]:
                 time_stamp           <fffd09e5>
                 next_to_watch        <0>
                 jiffies              <fffd3800>
                 next_to_watch.status <0>
               MAC Status             <40000083>
               PHY Status             <796d>
               PHY 1000BASE-T Status  <3800>
               PHY Extended Status    <3000>
               PCI Status             <10>
[  117.828303] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  117.945327] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  117.945588] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  118.161717] Setting dangerous option reset - tainting kernel
[  118.162681] Setting dangerous option force_reset_modeset_test - tainting kernel
[  119.667332] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Comment 5 Marta Löfstedt 2017-10-23 12:38:49 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3275/shard-kbl7/igt@kms_plane_multiple@legacy-pipe-A-tiling-none.html

	

[  150.943677] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  151.061161] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  151.061331] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  151.109982] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  151.110209] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
[  151.650854] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                 TDH                  <0>
                 TDT                  <2>
                 next_to_use          <2>
                 next_to_clean        <0>
               buffer_info[next_to_clean]:
                 time_stamp           <fffd09e5>
                 next_to_watch        <0>
                 jiffies              <fffdbcc0>
                 next_to_watch.status <0>
               MAC Status             <40000083>
               PHY Status             <796d>
               PHY 1000BASE-T Status  <3800>
               PHY Extended Status    <3000>
               PCI Status             <10>
[  151.925279] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  151.970594] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  151.970928] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
Comment 6 Marta Löfstedt 2017-10-23 12:39:20 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3275/shard-kbl7/igt@kms_rotation_crc@cursor-rotation-180.html

[  225.461788] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  225.567345] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  225.567422] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  225.611280] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  225.611420] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
[  225.662294] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                 TDH                  <0>
                 TDT                  <2>
                 next_to_use          <2>
                 next_to_clean        <0>
               buffer_info[next_to_clean]:
                 time_stamp           <fffd09e5>
                 next_to_watch        <0>
                 jiffies              <fffede00>
                 next_to_watch.status <0>
               MAC Status             <40000083>
               PHY Status             <796d>
               PHY 1000BASE-T Status  <3800>
               PHY Extended Status    <3000>
               PCI Status             <10>
[  226.223849] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  226.345781] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  226.345906] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  226.397726] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  226.397959] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
[  226.986756] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  227.104714] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  227.104993] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  227.153588] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  227.153984] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
[  227.645160] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Comment 7 Marta Löfstedt 2017-10-27 08:17:54 UTC
CI_DRM_3287 shard-kbl1 igt@debugfs_test@read_all_entries_display_off

[  107.715886] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  107.830309] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  107.830515] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  108.481623] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  108.526006] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3287/shard-kbl1/igt@debugfs_test@read_all_entries_display_off.html
Comment 8 Elizabeth 2017-11-01 20:12:41 UTC
We got the message on SKL with test igt@prime_vgem@basic-fence-flip:

IGT-Version: 1.20-g7aac0e8 (x86_64) (Linux: 4.14.0-rc7-drm-intel-qa-ww44-commit-ec9f758+ x86_64)
Subtest basic-fence-flip: SUCCESS (0.694s)
Test requirement not met in function __real_main757, file prime_vgem.c:849:
Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT)

dmesg:
[  548.105523] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
Comment 11 Elizabeth 2017-11-10 20:40:34 UTC
This is a "me too" with SKL and test  igt@prime_vgem@basic-fence-flip. Linux: 4.14.0-rc8-drm-intel-qa-ww45-commit-6f3dca3+ x86_64
[  540.617124] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
Comment 15 Marta Löfstedt 2017-11-15 07:14:07 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_chv_cursor_fail@pipe-c-64x64-bottom-edge.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_plane@plane-position-hole-dpms-pipe-c-planes.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_flip@modeset-vs-vblank-race.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_ccs@pipe-e-bad-rotation-90.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_cursor_legacy@all-pipes-single-bo.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_universal_plane@disable-primary-vs-flip-pipe-b.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_universal_plane@universal-plane-pipe-b-sanity.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_flip@flip-vs-modeset-vs-hang.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_plane_multiple@legacy-pipe-a-tiling-x.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3347/shard-kbl1/igt@kms_plane_multiple@atomic-pipe-b-tiling-yf.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3344/shard-kbl1/igt@pm_rpm@dpms-non-lpsp.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3344/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-blt.html
Comment 21 Elizabeth 2017-12-06 20:06:25 UTC
On SKL with igt@prime_vgem@basic-fence-flip

IGT-Version: 1.20-g1db1246 (x86_64) (Linux: 4.15.0-rc2-drm-intel-qa-ww49-commit-1a0d67e+ x86_64)
Subtest basic-fence-flip: SUCCESS (0.679s)
Test requirement not met in function __real_main757, file prime_vgem.c:849:
Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT)

We're also getting the message:

[  453.145388] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
Comment 25 Elizabeth 2017-12-13 21:17:00 UTC
Hello Marta, I added SKL before the [KBL only] was added, should I open a new bug for SKL? Thank you.
Comment 26 Marta Löfstedt 2017-12-14 08:12:59 UTC
(In reply to Elizabeth from comment #25)
> Hello Marta, I added SKL before the [KBL only] was added, should I open a
> new bug for SKL? Thank you.

yes. The reason why I want to separate these bugs on platforms, is that the LSPCON HW could be different and we usually need to cooperate with the LSPCON vendors in order to solve these type of bugs.
Comment 27 Elio 2017-12-19 14:59:16 UTC
Upgrading LSPCON Firwmare to 1.72 version, we should verify that this works after running failing tests.
Comment 28 Elizabeth 2017-12-20 17:28:18 UTC
Created attachment 136328 [details]
kern_log_KBL_FF

(In reply to Elio from comment #27)
> Upgrading LSPCON Firwmare to 1.72 version, we should verify that this works
> after running failing tests.
After upgrading to 1.72, we started having this messages on our KBL, before those only appearing in SKL (bug 104269)

Tests:
igt@kms_flip@basic-flip-vs-dpms
igt@kms_flip@basic-flip-vs-modeset

dmesg:	
[  359.002541] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  359.099187] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  359.099240] [drm:intel_dp_detect [i915]] *ERROR* LSPCON resume failed
[  359.900689] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
Comment 29 Elizabeth 2017-12-20 17:42:04 UTC
Created attachment 136329 [details]
i915_display_info
Comment 30 Elizabeth 2017-12-20 17:52:21 UTC
Sorry for the spam, I'm getting the LSPCON FW from this site https://downloadcenter.intel.com/download/26609/NUCs-HDMI-2-0-Firmware-Update-Tool-for-Intel-NUC-Kit-NUC7i3BN-NUC7i5BN-NUC7i7BN-NUC6CAY?wapkw=nuc7i7bnh, is this the actual "latest" version?? Should I ask to Shashank? Thank you.
Comment 31 Jani Saarinen 2017-12-22 13:42:02 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4079/shard-kbl3/igt@kms_color@pipe-b-legacy-gamma-reset.html

Dmesg	
[  138.496804] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  138.610319] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
[  138.610473] [drm:intel_dp_detect [i915]] *ERROR* LSPCON resume failed
[  138.656509] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  138.656708] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
[  139.411276] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  139.454559] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  139.454842] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsucce
Comment 32 shashank.sharma@intel.com 2017-12-27 16:52:57 UTC
Created attachment 136408 [details]
LSPCON FW V1.70

Attaching FW 1.70 just for verification
Comment 33 shashank.sharma@intel.com 2017-12-27 16:54:47 UTC
Hi Elizabeth, 
Thanks for the updates, just to confirm the binary, I have attached LSPCON FW Version 1.70 with this BZ. Can you please try flashing this ? 

As such, there is no change (of our interest) between 1.72 and 1.70, and I got this FW from MCA directly, so this should give us proper status. 

- Shashank
Comment 38 Elizabeth 2018-01-16 20:19:19 UTC
(In reply to shashank.sharma@intel.com from comment #33)
> Hi Elizabeth, 
> Thanks for the updates, just to confirm the binary, I have attached LSPCON
> FW Version 1.70 with this BZ. Can you please try flashing this ? 
> 
> As such, there is no change (of our interest) between 1.72 and 1.70, and I
> got this FW from MCA directly, so this should give us proper status. 
> 
> - Shashank
Hello again, after downgrading to 1.70 last week we haven't met the error again, we'll be monitoring for the message in the next FF cycles.
Comment 41 Marta Löfstedt 2018-01-24 13:24:45 UTC
Note, we have changed from KVM to HDMI dummies, still we hit new tests:

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3680/shard-kbl4/igt@gem_exec_store@pages-bsd2.html
Comment 52 Marta Löfstedt 2018-02-20 08:42:33 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4268/shard-hsw7/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html

run.log:
running: igt/kms_vblank/pipe-a-ts-continuation-dpms-suspend

[29/97] skip: 11, pass: 18 /                               
FATAL: command execution failed
...
Completed CI_IGT_test CI_DRM_3800/shard-hsw7/8 : FAILURE
CI_IGT_test runtime 316 seconds
Rebooting shard-hsw7

from dmesg:
<7>[ 4400.744449] [IGT] kms_vblank: starting subtest pipe-A-ts-continuation-dpms-suspend
...
Last dmesg:
<7>[ 4400.845869] [drm:sandybridge_pcode_write_timeout [i915]] warning: pcode (write of 0x00000011 to mbox 11) mailbox access failed for hsw_write_dcomp [i915]: -6
<7>[ 4400.845922] [drm:hsw_write_dcomp [i915]] Failed to write to D_COMP
<7>[ 4400.850952] [drm:intel_runtime_suspend [i915]] Device suspended
Comment 53 Marta Löfstedt 2018-02-20 08:43:05 UTC
(In reply to Marta Löfstedt from comment #52)
> https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4268/shard-hsw7/
> igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
> 
> run.log:
> running: igt/kms_vblank/pipe-a-ts-continuation-dpms-suspend
> 
> [29/97] skip: 11, pass: 18 /                               
> FATAL: command execution failed
> ...
> Completed CI_IGT_test CI_DRM_3800/shard-hsw7/8 : FAILURE
> CI_IGT_test runtime 316 seconds
> Rebooting shard-hsw7
> 
> from dmesg:
> <7>[ 4400.744449] [IGT] kms_vblank: starting subtest
> pipe-A-ts-continuation-dpms-suspend
> ...
> Last dmesg:
> <7>[ 4400.845869] [drm:sandybridge_pcode_write_timeout [i915]] warning:
> pcode (write of 0x00000011 to mbox 11) mailbox access failed for
> hsw_write_dcomp [i915]: -6
> <7>[ 4400.845922] [drm:hsw_write_dcomp [i915]] Failed to write to D_COMP
> <7>[ 4400.850952] [drm:intel_runtime_suspend [i915]] Device suspended

OOPS wrong bug
Comment 61 Jani Saarinen 2018-05-24 10:11:41 UTC
New FW in testing on CI now.
Comment 62 Lakshmi 2018-09-04 11:31:50 UTC
This issue occurs once/twice in a week with DRM/IGT/drmtip. Last time this was noticed 5 days ago. Note: This issue occurs only in KBL.
Comment 63 Lakshmi 2018-10-30 06:50:26 UTC
Still happening with latest FW 1.75 as well

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5047/shard-kbl2/igt@kms_mmap_write_crc.html
Comment 64 Swati Sharma 2018-12-04 13:29:14 UTC
Was able to reproduce part of the failure using i-g-t pm_rpm@module-reload. Kernel: 4.20 rc4-CI-CI_DRM_5212+

[  245.370760] [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5
[  245.445053] [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5
[  245.519201] [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5
[  245.593399] [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5
[  245.667656] [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5
[  245.667697] [drm:lspcon_write_infoframe [i915]] *ERROR* DPCD write failed at:0x5c0
[  245.667829] [drm:lspcon_write_infoframe [i915]] *ERROR* Failed to write AVI infoframes

Debug: WIP


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.