Thanks for the tip. I reran the debug again until communication stopped.
Backtrace is below. Thanks!
441.204990 upsdrv_updateinfo... (Driver stopped communicating)
Broadcast message from n...@golgotha.tklapp.com (somewhere) (Sat Oct 15 03:36:57
UPS nailbunny@localhost is unavailable
Program received signal SIGINT, Interrupt.
0x00007ffff76ec1c7 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
#0 0x00007ffff76ec1c7 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff7bd69e5 in ?? () from /lib/x86_64-linux-gnu/libusb-0.1.so.4
#2 0x000000000040659b in ?? ()
#3 0x0000000000405b32 in ?? ()
#4 0x0000000000404340 in ?? ()
#5 0x0000000000402c39 in ?? ()
#6 0x00007ffff762cb45 in __libc_start_main () from
#7 0x0000000000402e4d in ?? ()
From: Charles Lepple <clep...@gmail.com>
Sent: Friday, October 14, 2016 10:41 PM
To: Daniel Shields
Cc: nut-upsuser@lists. alioth. debian. org
Subject: Re: [Nut-upsuser] Data Stale at random intervals
On Oct 14, 2016, at 8:53 PM, Daniel Shields
Ran with gdb:
run -u nut -a nailbunny -x bus=010 -x vendorid=0764 -x productid=0501 -DDDDD
Same result as when I ran normally. Driver just stops communicating with no
errors or messages in the logs. Not sure where to go from here as I'm not
seeing anything to follow up on.
I still haven't had a chance to look at all of the logs, but if you press
Ctrl-C while running in gdb, and get a backtrace with "bt", where is it stopped?
Nut-upsuser mailing list