I've another customer with a similar issue:
case: 13932013
- CFM device was in the middle of a video meeting  when the screen first went stripey (horizontal thick lines) and all the other participants' video streams went black; pictures
image of CFM display: https://drive.google.com/open?id=1dTO1aDky9oT6xDvbc9La6eBWFzbjuD7O
image of what attendees see via mobile: https://drive.google.com/open?id=19ezFvMA1MNdy_svb8wsh2LmMIDRF2vrY
network test: https://drive.google.com/open?id=0B01ZVp8vDQocNjRqcWhWZUhBNTg
customer info: https://drive.google.com/open?id=109rsjL6peqrVmqs3FC_RTBXcjmDUHKIMfwCfscpAr-0

Hi, any update on this case will be much appreciated. Please let me know if you need more information/data that will help you with the investigation so I can request it to the customer. Thanks everyone!

@mnilsson, can you help reassign this issue? Cfm camera (PTZ Pro) works fine in settings, but doesn't work in video meetings.

We have some additional details from customer mentioned in comment#1 
case: 13932013
PII protected log file and screenshot of the issue: https://drive.google.com/open?id=1ijhXnVmEYi4CfdbhZK8fdiNtG74DdnqF

Customer submitted a couple of feedback reports from the meeting: 
Report id 1: 7615011834220631 
Report id 2: 5775969441139377 

We have got fresh debug logs from customer: https://drive.google.com/open?id=1kr9W8YhK0wkFG0Rij_sNOR6btseVXkAv
And some additional detail on latest occurrence of the issue:
- The issue reoccurred during a meeting
- The issue was with the screen going completely blank, no UI at all 
- While gathering debug logs the screen went blank again and customer had to re-plug the HDMI cable in order to see the screen and enter the command 
- This issue happened with only one screen connected to the device 

Not sure if it is related to back screen in the above comment, but I can see a Chrome crashed at 10:44:46:

2017-11-10T10:44:46.465629+00:00 INFO crash_reporter[5821]: Log command "  echo "===i915/parameters===";   grep '' /sys/module/i915/parameters/* |     sed -e 's!^/sys/module/i915/parameters/!!';   for dri in /sy
s/kernel/debug/dri/*; do     echo "===$dri/i915_error_state===";     cat $dri/i915_error_state;     echo "===$dri/i915_capabilities===";     cat $dri/i915_capabilities;     echo "===$dri/i915_wa_registers===";  
   cat $dri/i915_wa_registers;   done" exited with 1
2017-11-10T10:44:46.465651+00:00 ERR crash_reporter[5821]: Error reading udev log info crash_reporter-udev-collection-change-card0-drm
2017-11-10T10:44:46.466949+00:00 WARNING kernel: [ 4571.390510] udevd[5820]: Process '/sbin/crash_reporter --udev=KERNEL=card0:SUBSYSTEM=drm:ACTION=change' failed with exit code 1.
....
2017-11-10T10:44:49.600133+00:00 WARNING crash_reporter[5844]: [user] Received crash notification for chrome[862] sig 6, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-11-10T10:44:49.610433+00:00 ERR session_manager[782]: [ERROR:object_proxy.cc(582)] Failed to call method: org.chromium.LibCrosServiceInterface.CheckLiveness: object_path= /org/chromium/LibCrosService: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
2017-11-10T10:44:49.791886+00:00 INFO session_manager[782]: [INFO:child_exit_handler.cc(77)] Handling 862 exit.
2017-11-10T10:44:49.791894+00:00 ERR session_manager[782]: [ERROR:child_exit_handler.cc(85)]   Exited with signal 6
2017-11-10T10:44:49.791900+00:00 INFO session_manager[782]: [INFO:session_manager_service.cc(267)] Exiting process is chrome.
2017-11-10T10:44:49.791904+00:00 INFO session_manager[782]: [INFO:browser_job.cc(149)] Terminating process group: Ensuring browser processes are gone.
2017-11-10T10:44:49.791907+00:00 INFO session_manager[782]: [INFO:system_utils_impl.cc(111)] Sending 9 to -862 as 1000
2017-11-10T10:44:49.791920+00:00 INFO session_manager[782]: [INFO:system_utils_impl.cc(111)] Sending 9 to 862 as 0
2017-11-10T10:44:49.792378+00:00 INFO session_manager[782]: 

@vkasatkin, #c7 and #c8 sounds like a completely different issue from the original description (preview shows green)...If the whole screen is blank and they had to re-plug HDMI cable, then the issue sounds like with HDMI output. Let me follow up on that issue separately.

kotah@, yes, this looks like a different issue. 
Also, I have just noticed same set of error messages in the initial debug logs from customer (https://drive.google.com/open?id=19UKP--rWXrPwoYqusWOakZvu_94bA4KX) :

chrome/chrome_20171017-101046

[13100:13100:1017/101047.051652:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s)
[13100:13125:1017/101047.242739:WARNING:name_value_pairs_parser.cc(55)] Key block_devmode already has value (error), ignoring new value: 0
[13135:13144:1017/101047.468591:VERBOSE1:drm_device_manager.cc(54)] Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1
[13135:13135:1017/101053.394175:ERROR:gles2_cmd_decoder.cc(15996)] Offscreen context lost via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
[13135:13135:1017/101053.394221:ERROR:gles2_cmd_decoder.cc(4291)]   GLES2DecoderImpl: Context reset detected after MakeCurrent.
[13135:13135:1017/101053.394252:ERROR:gpu_channel_manager.cc(188)] Exiting GPU process because some drivers cannot recover from problems.
[13135:13135:1017/101053.394289:ERROR:gpu_channel_manager.cc(188)] Exiting GPU process because some drivers cannot recover from problems.
[13219:13233:1017/101053.507069:ERROR:drm_gpu_display_manager.cc(142)] There is no display with ID 12863098231074816
............
[13219:13219:1017/101059.390935:ERROR:gles2_cmd_decoder.cc(1150)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_VALUE : glShaderSource: unknown shader
[13219:13219:1017/101059.391122:ERROR:gles2_cmd_decoder.cc(1150)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_VALUE : glCompileShader: unknown shader
...........
[13219:13219:1017/101059.392305:ERROR:gles2_cmd_decoder.cc(9074)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_OPERATION : glUniformMatrix4fv: wrong uniform function for type
[13219:13219:1017/101059.392359:ERROR:gles2_cmd_decoder.cc(9074)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_OPERATION : glUniform4fv: wrong uniform function for type
[13219:13219:1017/101059.392419:ERROR:gles2_cmd_decoder.cc(9074)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type
[13219:13219:1017/101059.392512:ERROR:gles2_cmd_decoder.cc(9100)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_OPERATION : glUniform1i: unknown location
[13219:13219:1017/101059.392570:ERROR:gles2_cmd_decoder.cc(9074)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_OPERATION : glUniformMatrix4fv: wrong uniform function for type
[13219:13219:1017/101059.392624:ERROR:gles2_cmd_decoder.cc(9074)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_OPERATION : glUniform4fv: wrong uniform function for type
[13219:13219:1017/101059.392672:ERROR:gles2_cmd_decoder.cc(9074)] [.DisplayCompositor-0xfe521a2e400]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type
[13219:13219:1017/101059.393079:ERROR:gles2_cmd_decoder.cc(15996)] Onscreen context lost via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
[13219:13219:1017/101059.393190:ERROR:gles2_cmd_decoder.cc(4291)]   GLES2DecoderImpl: Context reset detected after MakeCurrent.

messages:
2017-10-17T10:10:28.394244+02:00 INFO kernel: [200660.679308] [drm] stuck on bsd ring
2017-10-17T10:10:28.394274+02:00 INFO kernel: [200660.679327] [drm] GPU crash dump saved to /sys/class/drm/card0/error
2017-10-17T10:10:28.394796+02:00 INFO kernel: [200660.679340] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
2017-10-17T10:10:28.394807+02:00 INFO kernel: [200660.679356] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
2017-10-17T10:10:28.394831+02:00 INFO kernel: [200660.679372] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
2017-10-17T10:10:28.394836+02:00 INFO kernel: [200660.679388] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
2017-10-17T10:10:28.418473+02:00 INFO crash_reporter[12979]: Consent given - collect udev crash info.
2017-10-17T10:10:30.394172+02:00 INFO kernel: [200662.680911] [drm] RC6 on
2017-10-17T10:10:31.221300+02:00 INFO crash_reporter[12979]: Log command "  echo "===i915/parameters===";   grep '' /sys/module/i915/parameters/* |     sed -e 's!^/sys/module/i915/parameters/!!';   for dri in /s
ys/kernel/debug/dri/*; do     echo "===$dri/i915_error_state===";     cat $dri/i915_error_state;     echo "===$dri/i915_capabilities===";     cat $dri/i915_capabilities;     echo "===$dri/i915_wa_registers==="; 
    cat $dri/i915_wa_registers;   done" exited with 1
2017-10-17T10:10:31.221321+02:00 ERR crash_reporter[12979]: Error reading udev log info crash_reporter-udev-collection-change-card0-drm
2017-10-17T10:10:31.222186+02:00 WARNING kernel: [200663.510291] udevd[12978]: Process '/sbin/crash_reporter --udev=KERNEL=card0:SUBSYSTEM=drm:ACTION=change' failed with exit code 1.
2017-10-17T10:10:34.395216+02:00 INFO kernel: [200666.684155] [drm] stuck on render ring
2017-10-17T10:10:34.413822+02:00 INFO crash_reporter[13008]: Consent given - collect udev crash info.
2017-10-17T10:10:34.534591+02:00 WARNING crash_reporter[13016]: Received crash notification for chrome[656] user 1000 (called directly)
2017-10-17T10:10:36.394152+02:00 INFO kernel: [200668.686003] [drm] RC6 on
......
2017-10-17T10:10:46.671327+02:00 ERR cras_server[2081]: fetch err: -32 for b4d0001
2017-10-17T10:10:46.676257+02:00 ERR cras_server[2081]: fetch err: -32 for b4e0001
2017-10-17T10:10:46.680473+02:00 ERR cras_server[2081]: fetch err: -32 for 7100001
2017-10-17T10:10:46.689191+02:00 ERR cras_server[2081]: fetch err: -32 for b410000
2017-10-17T10:10:46.803225+02:00 ERR cras_server[2081]: fetch err: -32 for b430001
2017-10-17T10:10:46.807532+02:00 INFO session_manager[621]: [INFO:child_exit_handler.cc(77)] Handling 656 exit.
2017-10-17T10:10:46.807647+02:00 ERR session_manager[621]: [ERROR:child_exit_handler.cc(85)]   Exited with signal 6
2017-10-17T10:10:46.807708+02:00 INFO session_manager[621]: [INFO:session_manager_service.cc(280)] Exiting process is chrome.
2017-10-17T10:10:46.807755+02:00 INFO session_manager[621]: [INFO:browser_job.cc(149)] Terminating process group: Ensuring browser processes are gone.

we have fresh log from the c#1 customer:
case#  13476325
https://drive.google.com/open?id=1anJF6e_SfDKhALvMYQcL63ClZvXdsKpw
he was advised by Logitech to update the firmware of the PTZ, which he has done around 
179 | 2017-11-09 18:29:19 | Kernel Event | Clean Shutdown

Related SF Case#: 13476325
Customer is waiting for an update and ETA.
Tier 1 has requested a triage.

@mnilsson

Any news about this bug?
When will it be triaged?

Thank you.

This is NOT same as  crbug.com/789872 . We have two issues mixed up in this crbug:

Issue-1: is the original issue description and #c11. Cfm shows green icon where it should show sending video (https://drive.google.com/open?id=1x2VWwkY-OCjdYYfmk0x716FtZCAKD6-g).
Case#: 13476325

Issue-2: is GPU hang (#c1, #c6, #c8, #c10 in this bug). This is  crbug.com/789872 , which is fixed with M64.
Case#: 13932013

mpricone@, please file a separate bug again with the info in the original description and #c11 only, so we can clarify what the issue is. Then we should close this bug as dup of 789872. 

Closing this bug as requested. Marked as duplicate of 789872.
New bug for this issue is  crbug.com/794667