<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 2026-07-24 05:49, Sam Varshavchik
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:cone.1784893755.321675.480467.1000@ripper.email-scan.com">
<pre wrap="" class="moz-quote-pre">Raymond Burkholder writes:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">« HTML content follows »
I wrote up an article regarding this.
<a class="moz-txt-link-rfc1738" href="https://blog.raymond.burkholder.net/index.php?/archives/1360-NUT-USB-APC-BeagleBone.html"><font color="red"><b>MailScanner has detected a possible fraud attempt from "blog.raymond.burkholder.net" claiming to be</b></font> <URL:https://blog.raymond.burkholder.net/index.php?/archives/1360-NUT-USB-
APC-BeagleBone.html></a>NUT USB APC BeagleBone
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
Which kernel? I'm not seeing disconnects, but resets (also an APC unit, and </pre>
</blockquote>
<span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">$ uname -a</span><span
style="color:#000000;background-color:#ffffff;">
</span><br>
<span style="color:#000000;background-color:#ffffff;">Linux bb05
6.18.36-bone40 #1 SMP PREEMPT Sat Jun 20 01:32:11 UTC 2026
armv7l GNU/Linux</span><br>
</span>
<blockquote type="cite"
cite="mid:cone.1784893755.321675.480467.1000@ripper.email-scan.com">
<pre wrap="" class="moz-quote-pre">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.
</pre>
</blockquote>
<p>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?</p>
<p>Now that I've said that, maybe I should see if there is such an
animal which identifies what my own problem is.</p>
<p>Raymond<br>
<a class="moz-txt-link-freetext" href="https://blog.raymond.burkholder.net/">https://blog.raymond.burkholder.net/</a></p>
</body>
</html>