[Nut-upsdev] blazer_usb: compatibility with Ippon BackPro UPSes (Phoenix Power Co., Ltd usb-to-serial controller)
Alexey Loukianov
mooroon2 at mail.ru
Tue Jan 12 19:38:19 UTC 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
12.01.2010 22:17, Arjen de Korte wrote:
> Citeren Alexey Loukianov <mooroon2 at mail.ru>:
>
> Replugging will also, so I don't think this is something vital (we
> never got any reports to that matter either). What error will it
> return it when it is stalled? Post the output of the driver starting
> up a stalled device with debug level set to -DDD.
Errors may be different. I've seen EPIPE while been debugging, and now I've
forced the device to stall and get the following blazer_usb run log:
[lexa2 at lx2linux bin]$ sudo ./blazer_usb -u root -DDD -a ippon-ext-hdd1 -x
subdriver=ippon -x runtimecal=60,100,378,50 -x novendor
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.1-2240)
0.000000 debug level is '3'
0.000614 Checking device (1005/B113) (001/006)
0.002221 - VendorID: 1005
0.002231 - ProductID: b113
0.002235 - Manufacturer: USB
0.002240 - Product: FLASH DRIVE
0.002363 - Serial Number: B509112400001042
0.002372 - Bus: 001
0.002378 Trying to match device
0.002533 Device does not match - skipping
0.002610 Checking device (05E3/0608) (001/003)
0.004475 - VendorID: 05e3
0.004492 - ProductID: 0608
0.004496 - Manufacturer: unknown
0.004502 - Product: USB2.0 Hub
0.004507 - Serial Number: unknown
0.004511 - Bus: 001
0.004734 Trying to match device
0.004818 Device does not match - skipping
0.004832 Checking device (0AC8/3450) (001/002)
0.007496 - VendorID: 0ac8
0.007514 - ProductID: 3450
0.007519 - Manufacturer: A4 TECH Corp.
0.007525 - Product: A4 TECH USB2.0 PC Camera E
0.007529 - Serial Number: unknown
0.007727 - Bus: 001
0.007733 Trying to match device
0.007822 Device does not match - skipping
0.007941 Checking device (1D6B/0002) (001/001)
0.008027 - VendorID: 1d6b
0.008035 - ProductID: 0002
0.008040 - Manufacturer: Linux 2.6.26.8-57.fc8PAE ehci_hcd
0.008120 - Product: EHCI Host Controller
0.008202 - Serial Number: 0000:00:02.1
0.008210 - Bus: 001
0.008214 Trying to match device
0.008293 Device does not match - skipping
0.008374 Checking device (06DA/0003) (002/004)
0.012500 - VendorID: 06da
0.012512 - ProductID: 0003
0.012518 - Manufacturer: unknown
0.012523 - Product: unknown
0.012528 - Serial Number: unknown
0.012861 - Bus: 002
0.012868 Trying to match device
0.013039 Device matches
0.015499 Trying megatec protocol...
0.018490 send: error sending control message: Timer expired
0.018528 blazer_status: short reply
0.018550 Status read 1 failed
0.021484 send: error sending control message: Timer expired
0.021521 blazer_status: short reply
0.021547 Status read 2 failed
0.024493 send: error sending control message: Timer expired
0.024532 blazer_status: short reply
0.024553 Status read 3 failed
0.024577 Trying mustek protocol...
0.027585 send: error sending control message: Timer expired
0.027625 blazer_status: short reply
0.027649 Status read 1 failed
0.030498 send: error sending control message: Timer expired
0.030534 blazer_status: short reply
0.030559 Status read 2 failed
0.033492 send: error sending control message: Timer expired
0.033528 blazer_status: short reply
0.033553 Status read 3 failed
0.033574 Trying megatec/old protocol...
0.036485 send: error sending control message: Timer expired
0.036653 blazer_status: short reply
0.036673 Status read 1 failed
0.039718 send: error sending control message: Timer expired
0.039802 blazer_status: short reply
0.039839 Status read 2 failed
0.042493 send: error sending control message: Timer expired
0.042511 blazer_status: short reply
0.042517 Status read 3 failed
0.042521 No supported UPS detected
Corresponding entries from dmesg:
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 128 rq 6 len 255 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 128 rq 6 len 255 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -62
So, in case there's an EPIPE condition which can't be cleared using
usb_clear_halt(), or there's "Timer expired" condition (errno -62 - don't
remember what is the correct E-alias for it) - it might be worth try to do
usb_reset on device as a last resort (and then to re-enumerate the bus and
reopen the device). If it don't help then it is either something totally wrong
with the device or it's time to stand up and went to a place where the box
resides to replug the cable.
- --
Best regards,
Alexey Loukianov mailto:mooroon2 at mail.ru
System Engineer, Mob.:+7(926)218-1320
*nix Specialist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJLTM+rAAoJEPB9BOdTkBULbv0H/3a/lQsDRUnM7Exj7tIeKJ4u
KcjavU7IvSH2Ceco/Ix5rYQwyxyNFaVZtfabSK9NPNkMOJcIpWHjPwOsS1eF+55U
ez8LWFhlvginpupg6UANF2SN3xvQdRgZ6H+c8v64snMxqx7boyGXln6hYC1X8ab7
JBzmAB+ONhaw4Q8ErKD/T32KNP698SUV0Qa5ir9eCUyEL8qvoruthnLd0aMQe2To
rs+xKu7m32Dr+sxYvEx7dhfzmDg6Xp3VQTovS6dO8mF2w+l60qOejsb/RQPQMcey
Da4zklMPjxkwlVjbZhlqnY87LDDL2MSNbVZ0vmzdVPavlyrk+8zM6lod3o58cmg=
=Pdol
-----END PGP SIGNATURE-----
More information about the Nut-upsdev
mailing list