Logs: https://cloud.google.com/console/storage/chromiumos-test-logs/bugfiles/cr/850888/

This issue is reproduced in Hana.

Hi can anyone help triage this issue?

Can you provide the output of the "Video Capture" tab in chrome://media-internals/ ?
Does that camera work at 4K in other platforms?

Yes. 4k camera works fine in other platforms. 

Media internals is available in this link https://cloud.google.com/console/storage/chromiumos-test-logs/bugfiles/cr/850888/. 

Ping!

I will take a look at this.

Tested but no repro on the following config:
Board: guado
Chrome Version: 68.0.3440.15
ChromeOS Version: 10718.13.0
Camera: Logirech BRIO (046d:085e)

All resolutions up to 4k appear to work fine on https://webrtc.github.io/samples/src/content/getusermedia/resolution/.

vasanthakumar@: A common pitfall with the 4k USB cameras that leads to the reported symptoms is that when plugged into a USB2 instead of USB3 port, they tend to lose the ability to serve the higher resolutions. Could you double check to make sure that the camera is connected to a USB3 port?

@chfremer: Thanks for your information. This issue is specific to Hana device only and it has a single USB port and a USBC port. I used a converter from USBC to USB port [for camera]. This issue seem to reproduce in both the ports. 

Atleast one of them is 3.0 port as per the system configuration. Thank you!

I will try to get my hands on a hana to take a look.

Ping ! @vasant Please check its still possible to reproduce. 

@Ravi: Yes this issue is still reproducible in latest M69 69.0.3497.35 Hana. 

Elm device also has the exact issue. M69 69.0.3497.35

I got the Hana now and was able to successfully reproduce the issue. Will start investigating the cause now.

Analysis result:
What happens from the Chromium side is that the session for the higher resolution starts successfully, but without any frame having been delivered from the camera calls to V4L2 poll() time out, and Chromium eventually gives up and ends the video capture session with an error.

https://cs.chromium.org/chromium/src/media/capture/video/linux/v4l2_capture_delegate.cc?q=v4l2_capture_delegate.cc&dr&l=827

Could this be an issue in V4L2 for this camera/board?
Assigning to keiichiw@ for further triage.

Thanks for the analysis, chfremer@.
Let me investigate.

chfremer@, thanks for digging into this.

For low level camera issues, please assign to either jcliang@ (if there are no hints about the potential reason) or me (if there is a hint that it could be hardware/kernel related) for further triage. There is also a OS>Kernel>Camera label for this purpose.

I reproduced it on hana.
For each packet, I got the message "Marking buffer as bad (error bit set)" from
http://cs/chromeos_public/src/third_party/kernel/v3.18/drivers/media/usb/uvc/uvc_video.c?l=997&rcl=2638ccfbb3dabb3f2fbdd98e386fa4e3c2d18fae
This is not informative message though.

It would be good to test on other v3.18 non-mediatek devices (e.g. caroline, cyan).

I got caroline and tested on it.
Video feed from both FullHD and 4K works well.
So, it seems that mediatek drivers in v3.18 has some problem.

Yes I also tried it on Caroline and Cyan. This is not reproducible in either of the devices.