ube

Sure: ``` root@pve:~/liquidctl# ps -ef | grep liq root 5811 25202 0 12:57 pts/1 00:00:00 grep liq root@pve:~/liquidctl# python3 -m liquidctl.cli initialize -g [DEBUG] __main__: running liquidctl v1.4.2 (6dd4f3de3a18) [DEBUG]...

So, there's a lock up in the hid device itself? Since I don't have any other instances runnig now? Here are the full outputs: ``` root@pve:~/liquidctl# python3 -m liquidctl.cli initialize...

Actually, I might just do that. Get som new skills. :) Thanks.

Ran the following test for 5(!) hours (forgot to exit :D). `watch -n .3 "clear; python3 -m liquidctl.cli status"` and `watch -n .1 "python3 -m liquidctl.cli set fan2 speed 20...

Just got back in the office some 30 minutes ago. Had it running all day and night. After 8 hours is locked up with the following error ``` ERROR: Unexpected...

Tried reloading the hid module with no luck. However, I'd say this case with excessive reads and writes to the controller is not a real world scenario. So I'll suggest...

``` [DEBUG] liquidctl.driver.usb: writting report 0x00 with 64 bytes: 3f:88:14:00:ff:05:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:01:00:00:00:00:00:07:14:1a:1e:33:28:4c:2d:cc:32:f2:3c:ff:3c:ff:14:00:23:33:28:80:31:80:32:f2:3c:ff:3c:ff:00:00:00:00:00:18 [INFO] __main__: Could not write to device. Res: -1 Traceback (most recent call last): File "/root/liquidctl/liquidctl/cli.py", line 321, in main...

+1 on this one. Running Ansible 2.12 with infoblox.nios_modules collection v1.2.2. This goes for `nios_a_record` as well.

It's by design, it's virtually impossible to distinguish a hot reboot (reset) from a mode switch; so many things that differ between physical machines. But I'll update the documentation with...