Random/Unexpected Hub Reset - Re-powers ALL ports when only one was commanded. about uhubctl HOT 4 CLOSED

Please read this FAQ item https://github.com/mvp/uhubctl?tab=readme-ov-file#power-comes-back-on-after-few-seconds-on-linux

Long story short, by bar most reliable way to fix this is to upgrade your host to Linux kernel 6.x.

from uhubctl.

Thanks for the link, but I don't think that this applies in my case.

Mostly my automation script is able cycle the power as required, as seen in the grep of syslog previously the ttyACMs came back on-line with gap between. In the (occasional) reset case, the hub appears to enable them together and they are quickly enumerated.

I'm not sure whether this is a code or hardware problem, it could even be the Pico glitching and getting stuck...

from uhubctl.

It is most likely Linux kernel USB and/or USB serial driver doing something unexpected. Not likely that uhubctl can fix that. But, that said, for kernel 6.x, uhubctl is using different method to control USB power compared to older kernels - main difference being that for kernel 6.x uhubctl makes use of explicit power off control provided by kernel itself, whereas in older kernels this is not as well defined - power off is sent directly to the hub, anf kernel doesn't explicitly know current power state, which sometimes makes it sporadically trigger device reset.

from uhubctl.

Closing this as not actionable by uhubctl

from uhubctl.