My theory is that this issue occurs on some combination of SOC (system-on-chip) hardware and kernel versions. I have experienced USB issues with ODroid before (even with USB 2.0) and it was due to kernel issues. It could be some hardware issue in the board itself, or kernel issue, or a combination of both. Power is usually the first culprit when such unstable operations are encountered but if power is ruled out, then in my opinion, it's SOC+Kernel issue.
what did you update, kernel or some packages?
The kernel of these ARM boxes are not updated often.
For packages, you can easily find out which one are related to usb like libusb
I'm running an Intel compute stick amd64 SOC running full Ubuntu 16.04lts desktop. So doing a
sudo apt-get update && sudo apt-get upgrade does everything.
My Asus tinker board in armh and as you say the kernel is not upgraded very often.
NanoPC T4
USB3 port -> USB2.0 cable -> CEM60 Hub -> USB2.0 Cable -> ASI290 mini
USB2 port1 -> PL2302 USB to COM -> CEM60 com
USB2 port2 -> USB3.0 cable -> ASI290MC Pro
Capture 200S X 12, -12C, with guiding on, works good.
So I can give the result that:
Only true USB 3.0 connection will cause problem.
The USB2.0 cable will not lead to USB3.0 driver working, even on the USB3.0 port.
The MC Pro camera with non-power USB hub will cause problem.
The problem is complexity, it may be some memory leak of the USB3.0 driver, and also the MC Pro camera is sensitive to the USB power.