[Nut-upsuser] {Disarmed} Re: usbhid-ups flooding system log

[Raymond Burkholder]

On 2026-07-24 05:49, Sam Varshavchik wrote:
> 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
> Which kernel? I'm not seeing disconnects, but resets (also an APC unit, and
$ uname -a
Linux bb05 6.18.36-bone40 #1 SMP PREEMPT Sat Jun 20 01:32:11 UTC 2026 
armv7l GNU/Linux
> 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.

Dunno. If there existed something like a USBdump tool, or maybe debug 
level, or maybe really roll up sleeves and do kernel tracing to see what 
it is choking on to generate the reset messages?

Now that I've said that, maybe I should see if there is such an animal 
which identifies what my own problem is.

Raymond
https://blog.raymond.burkholder.net/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20260724/6b4ef94d/attachment.htm>