Hello all,
While repeatedly setting up the system for tests figured out the problem in
other OS subsystem driver. Problem solved with the script. Thanks again for
your time
On Fri, Nov 9, 2012 at 6:13 PM, Arnaud Quette wrote:
>
>
> 2012/11/1 Jevgeni Jurtsenko
>
>> Hello all,
>>
>> Sorry for delay. I've been away for a while. Back to testing. I've tried
>> regular version 2.6.5-1 and patched. Main thing is that both versions work
>> until I reboot the OS, after that starting the nut fails with messages
>> below. To make it run again I've to re-plug the usb cable. Hard-resetting
>> the ups doesn't help either. Considering the fact to remotely monitor the
>> devices it is quite inconvenient. Suppose there is I power fault and ups is
>> drained out of power then the system won't come back online after power is
>> restored. I've tried searching for a working way to model the "usb cable
>> re-plug" on OS level with no luck. Any help would be appreciated.
>>
>> Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012
>> armv6l GNU/Linux
>>
>> *Version 2.6.5-1*
>> USB communication subdriver 0.21
>>0.00 debug level is '5'
>>0.008920 entering nutusb_open()
>>0.013091 device 004 opened successfully
>>0.015893 Can't claim POWERWARE USB interface: could not claim
>> interface 0: Device or resource busy
>>0.018484 Can't reset POWERWARE USB endpoint: could not clear/halt
>> ep 129: Device or resource busy
>>0.020807 device 004 opened successfully
>>0.021753 Can't claim POWERWARE USB interface: could not claim
>> interface 0: Device or resource busy
>>0.022617 Can't reset POWERWARE USB endpoint: could not clear/halt
>> ep 129: Device or resource busy
>>0.023750 device 004 opened successfully
>>0.024928 Can't claim POWERWARE USB interface: could not claim
>> interface 0: Device or resource busy
>>0.026070 Can't reset POWERWARE USB endpoint: could not clear/halt
>> ep 129: Device or resource busy
>>0.029099 device 004 opened successfully
>>0.029412 Can't claim POWERWARE USB interface: could not claim
>> interface 0: Device or resource busy
>>0.029714 Can't reset POWERWARE USB endpoint: could not clear/halt
>> ep 129: Device or resource busy
>>0.030193 send_to_all: SETINFO device.type "ups"
>>0.031387 send_to_all: SETINFO driver.version "2.6.4"
>>0.031855 send_to_all: SETINFO driver.version.internal "0.26"
>>0.032720 send_to_all: SETINFO driver.name "bcmxcp_usb"
>>0.033757 send_read_command: (4 bytes) => ab 01 31 23
>>0.034906 entering get_answer(31)
>>0.035409 get_answer: (0 bytes) =>
>>0.036298 send_read_command: (4 bytes) => ab 01 31 23
>>0.039485 entering get_answer(31)
>>0.040038 get_answer: (0 bytes) =>
>>0.040289 send_read_command: (4 bytes) => ab 01 31 23
>>0.041718 entering get_answer(31)
>>0.042514 get_answer: (0 bytes) =>
>>0.043435 send_read_command: (4 bytes) => ab 01 31 23
>>0.045095 entering get_answer(31)
>>0.045885 get_answer: (0 bytes) =>
>>0.046158 send_read_command: (4 bytes) => ab 01 31 23
>>0.050026 entering get_answer(31)
>>0.050552 get_answer: (0 bytes) =>
>>0.050785 Communications with UPS lost: Error executing command
>>0.051043 Could not communicate with the ups: Device or resource
>> busy
>>0.051271 CLOSING
>>
>> *Patched version*
>> 2.225863 => usb_interrupt_read -16
>>2.226680 => packet_loop (0, 0)
>>2.227534 => bytes_read (0)
>>2.227857 => usb_interrupt_read -16
>>2.228667 => packet_loop (0, 0)
>>2.229701 => bytes_read (0)
>>2.230028 => usb_interrupt_read -16
>>2.230809 => packet_loop (0, 0)
>>2.233160 => bytes_read (0)
>>2.234230 => usb_interrupt_read -16
>>2.234546 => packet_loop (0, 0)
>>2.234763 => bytes_read (0)
>>2.235573 => usb_interrupt_read -16
>>2.236373 => packet_loop (0, 0)
>>2.237285 => bytes_read (0)
>>2.237620 => usb_interrupt_read -16
>>2.238418 => packet_loop (0, 0)
>>2.239706 => bytes_read (0)
>>
>
> strange that a reboot causes this kind of issues!
> is this stable (i.e, reproduced upon each reboot)?
>
> I would need the following, after a reboot (i.e, reproducing the above
> issue):
> - lsusb -v -d0x0592:0x0002
> - grep usb /var/log/syslog
> - full trace, debug level 5, of the patched driver
> - ps -efl | grep bcm
>
> @Greg & Massimo: do you have the same behavior?
>
> cheers,
> Arnaud
> --
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.fr
>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuse
