search for: _usb_reap_async

..... 0.234375 upsdrv_updateinfo... 0.500000 Got 0 HID objects... 0.500000 Quick update... 0.500000 upsdrv_updateinfo... (... above repeated during normal operation - varying HID object count ...) (*** I pulled the cable here ***) 4.984375 libusb_get_interrupt: libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning. 4.984375 Got 0 HID objects... 4.984375 Quick update... 4.984375 upsdrv_updateinfo... 5.234375 Got 0 HID objects... 5.234375 Quick update... 5.250000 upsdrv_updateinfo... 5.406250 libusb_get_...

...5 Driver is malfunctioning if the UPS goes on-battery (quick test or otherwise). usbhid-ups - libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. (from event log) libusb_get_interrupt: libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning. 5D log attached. Disabling and re-enabling the LibUSB entry in device manager will get it back to normal without restarting NUT. Re-plugging the USB cord also works. Windows built-in driver works reliably,...