Gracefully recover from MS203X issues #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Multiple failure scenarios have been observed at COSCUP. Outline these here.
Fazantix was running with internal Hagibis and external
Bus 004 Device 016: ID 345f:2130 UltraSemi USB3 VideoAfter a while, the external capture (which had the camera connected to it) failed. Fazantix showed an orange blob, but did not crash itself.
Fazantix was stopped, and started:
usb_reset called on the device
The above was repeated a number of times, same result.
Tried a random ffmpeg command from the internets:
Video could be watched by a remote mpv client just fine.
ffmpeg process stopped, fazantix started, and all was well.
Conclusion: ffmpeg does something to the ms203X which revives it. Need to figure out what it is and to the same.
The "bad arguments" error on dequeue buffer is this in the v4l docs:
When it's in a hung state the metrics show that the requests for all sources keep increasing but the frames_read_total for the capture card stops increasing. There's no other output from fazantix telling something is going wrong except the orange fallback