[Nut-upsuser] usbhid-ups flooding system log

[Sam Varshavchik]

Raymond Burkholder writes:

> « HTML content follows »
> I wrote up an article regarding this.  
>
> <URL:https://blog.raymond.burkholder.net/index.php?/archives/1360-NUT-USB- 
> APC-BeagleBone.html>NUT USB APC BeagleBone
>
> For some reason, USB devices 'disconnect' and reconnect. When the device  
> reconnects, a new DeviceID is assigned to the USB device. This breaks the  
> usbhid-ups drivers supplied by NUT the packages. That is, usbhid-ups no  
> longer sees the APC USB device.

Which kernel? I'm not seeing disconnects, but resets (also an APC unit, and  
this one's running apcupsd, not nut) that started popping up after updating  
to kernel 7.1. In my case it appears to be harmless (device ID unchanged),  
but this might be further evidence of a USB stack regression in kernel 7.1.

I was actually working on something else (a lightning hit the tree next to  
the house frying a bunch of gear inside, no really), when I thought I found  
something else that needs looking into, in the form of reset messages.

But the all-mighty, all-powerful, all-seeing AI traced the resets to before  
the fateful event, reconciled it with a new kernel getting installed. It's a  
fun reading, if you have a few spare moments!

https://chatgpt.com/share/6a62358d-1710-83ea-ac20-dcb62a7dc7fd

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20260724/fa11aa4e/attachment.sig>