Further to this, I have found the relevant debug message at the time of
error. Paste here: https://pastebin.com/BzCvXbWj
The first unexpected log is this:
106432.128011 [D3] read: Overflow (-8)
The below commands can be run while the driver is running, so a
workaround for this case may be to run them preemptively.
I expect this to not be the fault of Nut, however given that the host
did not change between UPS replacement, this may be a new behaviour of
Salicru units that might need to be handled?
Thank you for the insight,
On 19/04/2025 09:35, S Shaikh via Nut-upsuser wrote:
I have run DMESG during the disconnect and there were no messages
during the time of disconnection. I ran: dmesg -w -T to follow the
output.
However resetting the USB device worked, so at least now I can now
save a reboot:
$ echo 0 | sudo tee /sys/bus/usb/devices/1-4/authorized
0
$ echo 1 | sudo tee /sys/bus/usb/devices/1-4/authorized
1
I am yet to try a new port/cable (the host is offsite).
On 11/04/2025 22:04, Greg Troxel via Nut-upsuser wrote:
You really need to look at kernel-level messages.
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
