Assigning P1 as this issue is blocking all adoption in this company as reliable docking is a crucial part of the use case.

They have also been in touch with Lenovo who point back to Google who point them back to Lenovo. So at the very least, we need to ensure we really understand where the source of the problem even if the fix is indeed up to Lenovo.

That's the GPU hang in the video stack that we've been getting for a bit

Does this only happen when using a docking station?

Also, is there a possibility we could ask if this still reproduces after going to about:flags, and flipping the flags for "WebRTC hardware video decoding" and "WebRTC hardware video encoding" please?

@posckiak, this happen with or without a docking station. 

@posciak I can try changing the flags: but it seems that one of them is already enabled:
WebRTC hardware video decoding  = Enabled
WebRTC hardware video encoding = Default

What should I set here?

@6: would you be able to try for each of the settings of "WebRTC hardware video decoding" please? The encoding flag should not have any effect in this case. Thank you.

The device in the feedback report from #0 is sentry.

is this b/35584255?

This is the log from #0.
[22461.762359] [drm] stuck on render ring
[22461.774556] [drm] GPU HANG: ecode 9:0:0xef9ffffd, in chrome [31558], reason: Ring hung, action: reset
[22461.774565] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[22461.774571] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[22461.774577] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[22461.774583] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[22461.774589] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[22461.776337] drm/i915: Resetting chip after gpu hang

The fix for b/35584255 was merged in m57 (https://bugs.chromium.org/p/chromium/issues/detail?id=684656). 

dskaram@ Can customer try m57 tot?