Re: [REGRESSION] CyberPower LE1000DG (0764:0501) USB HID regression on x86

On 7/30/26 21:28, Jamie Stephens wrote:
> 
> Per the recommendation on Proxmox Bugzilla #7850, I’m reporting what
> appears to be a Linux USB/HID regression affecting a CyberPower
> LE1000DG UPS.

Thx for the report. No developer replied yet with an idea what's wrong.
Unless this changes I guess you need to run a git bisection to get
somebodies attention, as the root of the problem might be in one of
various kernel subsystems. The process is described in
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
or
https://docs.kernel.org/admin-guide/bug-bisect.html; if you follow the
latter you might want to first check if mainline (7.2-rc6) is still
affected.

Ciao, Thorsten

> Hardware
> 
> UPS
> 
> CyberPower LE1000DG
> USB VID:PID 0764:0501
> 
> Affected x86 platform
> 
> Intel Tiger Lake-H USB 3.2 Gen 2 xHCI Host Controller
> PCI ID: 8086:43ed
> 
> Problem
> 
> When connected to the x86 system, the UPS enumerates successfully and
> is bound by the kernel to hid-generic.
> 
> Kernel messages include:
> 
> usb 1-3: New USB device found, idVendor=0764, idProduct=0501
> 
> usb 1-3: Product: LE1000DG
> 
> hid-generic 0003:0764:0501.0001: hiddev0,hidraw0:
> 
> USB HID v1.11 Device [CPS LE1000DG]
> 
> However,
> 
> sudo lsusb -v -d 0764:0501
> 
> reports:
> 
> wDescriptorLength     504
> 
> Warning: can't get report descriptor, LIBUSB_ERROR_PIPE
> 
> cannot read device status, Resource temporarily unavailable (11)
> 
> As a result, usbhid-ups is unable to reliably communicate with the
> device and NUT cannot reliably monitor UPS status.
> 
> Kernels Tested
> 
> The issue reproduces on:
> 
> Proxmox VE kernel 7.0.14-5-pve
> Proxmox VE kernel 7.0.14-6-pve
> Ubuntu mainline 7.1.5-070105-generic
> 
> Reproducing the issue on an Ubuntu mainline kernel indicates the
> behavior is not specific to Proxmox and appears to exist in upstream
> Linux as well.
> 
> Comparison
> 
> The identical UPS, USB cable, and NUT configuration were moved to a
> Raspberry Pi 5 running:
> 
> Debian 13 (trixie)
> Linux 6.18.34+rpt-rpi-2712
> NUT 2.8.1
> 
> On the Raspberry Pi:
> 
> the device binds successfully to hid-generic
> usbhid-ups initializes successfully
> NUT communicates reliably
> upsc ups@localhost consistently returns complete UPS status, including
> charge, runtime, voltage, load, and other telemetry
> 
> This behavior has remained reliable through repeated testing and reboots.
> 
> For completeness, lsusb -v on the Raspberry Pi also reports the HID
> report descriptor as unavailable. Despite this, usbhid-ups
> communicates with the UPS reliably. The communication failure only
> occurs on the affected x86 platform.
> 
> Troubleshooting Performed
> 
> Tested multiple USB ports
> Tested USB 2.0 and USB 3.x ports
> Replaced the USB cable
> Tested NUT 2.8.1, 2.8.5, and current development master
> Tested as both root and the nut service user
> Verified udev permissions
> Verified USB VID:PID 0764:0501
> Reproduced the issue on Ubuntu mainline 7.1.5
> 
> A Proxmox developer suggested this may require a USB HID device quirk
> and requested that the issue be reported upstream.
> 
> Reference:
> 
> Proxmox Bugzilla #7850: https://bugzilla.proxmox.com/show_bug.cgi?id=7850
> 
> Please let me know if additional information would be helpful. I can
> provide complete dmesg, lsusb, and usbhid-upsdebug logs or perform
> additional testing if needed.
> 
> Thank you,
> Jamie Stephens
>