On Apr 8, 2015, at 2:04 PM, Eric Cobb <[email protected]> wrote:
The mailing list doesn't accept large attachments, so I attached a gzip'd copy of the log in case anyone else wants to take a look. It doesn't show timing information, or the content of the URBs, so it is hard to tell what the driver is trying to do at any given point. I recognize that it is a slight change of the experiment to remove upsdrvctl, but could you please start the driver directly in the init script with -DDD (path should be in the output of '/usr/sbin/upsdrvctl -D'), and redirect that output to a log file? (We had a reason for why upsdrvctl does not pass '-D' flags through to the driver, but the reason escapes me at the moment.) It would also be useful to have the output of dmesg (or at least the USB-related subset), in case it has additional information on why libusb_get_interrupt() is failing. -- Charles Lepple clepple@gmail |
tripplite_3005_CentOS_6.6_strace.log.gz
Description: GNU Zip compressed data
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
