libusb_get_interrupt: Connection timed out

Bug #575573 reported by Andrew
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nut (Ubuntu)
Fix Released
Medium
Arnaud Quette

Bug Description

Binary package hint: nut

New problem with nut megatec_usb driver in Lucid.

/lib/nut/megatec_usb -u root -a belkin -DDDDD
Network UPS Tools - Megatec protocol driver 1.6 (2.4.3)
Serial-over-USB transport layer 0.10
   0.000000 debug level is '5'
   0.001687 Checking device (0665/5161) (002/003)
   0.017314 - VendorID: 0665
   0.017360 - ProductID: 5161
   0.017374 - Manufacturer: Cypress Semiconductor
   0.017388 - Product: USB to Serial
   0.017401 - Serial Number: unknown
   0.017414 - Bus: 002
   0.017426 Trying to match device
   0.017447 Device matches
   1.023463 libusb_get_interrupt: Connection timed out
   1.023517 get_data_phoenix: got so far []
   1.023542 get_data_phoenix: (8 bytes) => 00 00 00 00 00 00 00 00
   2.025464 libusb_get_interrupt: Connection timed out
   2.025516 get_data_phoenix: got so far []
   2.025545 get_data_phoenix: (16 bytes) => 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   2.025562 00 00
   3.026460 libusb_get_interrupt: Connection timed out
   3.026514 get_data_phoenix: got so far []
   3.026543 get_data_phoenix: (24 bytes) => 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   3.026564 00 00 00 00 00 00 00 00 00 00
   4.027463 libusb_get_interrupt: Connection timed out

My ups.conf:
[belkin]
  driver = megatec_usb
  port = auto
  lowbatt = 30
  mfr = Belkin
  model = F6C550-AVR

Note that I have had problems with nut in previous releases:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/209001

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nut 2.4.3-1ubuntu3.1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue May 4 22:41:04 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nut

Revision history for this message
Andrew (andrew-rw-robinson) wrote :
Revision history for this message
Andrew (andrew-rw-robinson) wrote :
Revision history for this message
Andrew (andrew-rw-robinson) wrote :
Revision history for this message
Andrew (andrew-rw-robinson) wrote :

How is this a duplicate of 572262, that bug is regarding the usbhid-ups driver, not the megatec_usb driver?

Revision history for this message
Nico Isenbeck (nico-isenbeck) wrote :

This is not a duplicate of Bug #572262.
I installed the patch from proposed (which fixes the #572262) but the bug still occurs.

I get exactly the same error message with nut 2.4.3-1ubuntu3.1 and PowerWalker VI800 UPS. Now I am using the karmic version of nut (http://packages.ubuntu.com/karmic/nut) which workes fine under lucid with the same configuration files.

Revision history for this message
Andrew (andrew-rw-robinson) wrote :

Confirmed as a regression. After installation of nut_2.4.1-3ubuntu2_i386.deb nut is able to pull the battery %

Chuck Short (zulcss)
Changed in nut (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Guy DESBIEF (guy-desbief) wrote :

I have the same problem, using a megatec_usb driver that worked fine in previous version
I will try Karmik package

Revision history for this message
Guy DESBIEF (guy-desbief) wrote :
Download full text (8.4 KiB)

I tried Karmik and get following message
even if the driver seems to work:
sudo /lib/nut/megatec_usb -u root -a infosec -DDDDD
[sudo] password for guy:
Network UPS Tools - Megatec protocol driver 1.6 (2.4.1)
Serial-over-USB transport layer 0.10
debug level is '5'
Checking device (0665/5161) (004/002)
- VendorID: 0665
- ProductID: 5161
- Manufacturer: Cypress Semiconductor
- Product: USB to Serial
- Serial Number: unknown
- Bus: 004
Trying to match device
Device matches
DTR=1, RTS=0
Starting UPS detection process...
Asking for UPS information [I]...
I => FAILED [short read]
I detail: (1 bytes) => 49
Asking for UPS status [Q1]...
get_data_phoenix: got so far [(235.2 2]
get_data_phoenix: (8 bytes) => 28 32 33 35 2e 32 20 32
get_data_phoenix: got so far [(235.2 234.7 234]
get_data_phoenix: (16 bytes) => 28 32 33 35 2e 32 20 32 33 34 2e 37 20 32
 33 34
get_data_phoenix: got so far [(235.2 234.7 234.7 034 5]
get_data_phoenix: (24 bytes) => 28 32 33 35 2e 32 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35
get_data_phoenix: got so far [(235.2 234.7 234.7 034 50.1 13.6]
get_data_phoenix: (32 bytes) => 28 32 33 35 2e 32 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35 30 2e 31 20 31 33 2e 36
get_data_phoenix: got so far [(235.2 234.7 234.7 034 50.1 13.6 25.0 00]
get_data_phoenix: (40 bytes) => 28 32 33 35 2e 32 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35 30 2e 31 20 31 33 2e 36 20 32 35 2e 30 20 30
 30
0]t_data_phoenix: got so far [(235.2 234.7 234.7 034 50.1 13.6 25.0 00001001
get_data_phoenix: (48 bytes) => 28 32 33 35 2e 32 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35 30 2e 31 20 31 33 2e 36 20 32 35 2e 30 20 30
 30 30 30 31 30 30 31 0d 30
Q1 => OK [(235.2 234.7 234.7 034 50.1 13.6 25.0 00001001]
Q1 VALUES => [235.2 234.7 234.7 34.0 50.1 13.6 25.0 00001001]
Asking for UPS status [Q1]...
get_data_phoenix: got so far [(234.7 2]
get_data_phoenix: (8 bytes) => 28 32 33 34 2e 37 20 32
get_data_phoenix: got so far [(234.7 234.7 234]
get_data_phoenix: (16 bytes) => 28 32 33 34 2e 37 20 32 33 34 2e 37 20 32
 33 34
get_data_phoenix: got so far [(234.7 234.7 234.7 034 5]
get_data_phoenix: (24 bytes) => 28 32 33 34 2e 37 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35
get_data_phoenix: got so far [(234.7 234.7 234.7 034 50.1 13.6]
get_data_phoenix: (32 bytes) => 28 32 33 34 2e 37 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35 30 2e 31 20 31 33 2e 36
get_data_phoenix: got so far [(234.7 234.7 234.7 034 50.1 13.6 25.0 00]
get_data_phoenix: (40 bytes) => 28 32 33 34 2e 37 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35 30 2e 31 20 31 33 2e 36 20 32 35 2e 30 20 30
 30
0]t_data_phoenix: got so far [(234.7 234.7 234.7 034 50.1 13.6 25.0 00001001
get_data_phoenix: (48 bytes) => 28 32 33 34 2e 37 20 32 33 34 2e 37 20 32
 33 34 2e 37 20 30 33 34 20 35 30 2e 31 20 31 33 2e 36 20 32 35 2e 30 20 30
 30 30 30 31 30 30 31 0d 30
Q1 => OK [(234.7 234.7 234.7 034 50.1 13.6 25.0 00001001]
Q1 VALUES => [234.7 234.7 234.7 34.0 50.1 13.6 25.0 00001001]
Asking for UPS status [Q1]...
get_data_phoenix: got so far [(234.7 2]
get_data_phoenix: (8 bytes) => 28 32 33 34 2e 37 20 32
get_data_phoenix: got so far [(234.7 235.2 234]
ge...

Read more...

Revision history for this message
Arnaud Quette (aquette) wrote :

Can you please test with the blazer_usb driver and report back?
This one has replaced megatec_usb officially since 2.4.3, but was already available in 2.4.1 (though not as mature).

cheers,
Arnaud

Revision history for this message
Arnaud Quette (aquette) wrote :

Dear all,

could you all please try blazer_usb, which has replaced megatec_usb for some time.
blazer_usb has improved a lot the situation, and many issues, like yours, have been fixed with it.

cheers,
Arnaud

Changed in nut (Ubuntu):
status: Confirmed → Fix Committed
assignee: nobody → Arnaud Quette (aquette)
Revision history for this message
Arnaud Quette (aquette) wrote :

we (NUT upstream) had a lot of success report with this specific type of units (USB 0x0665:0x5161) since this bug report, using blazer_usb instead of megatec_usb.

Considering the bug age, the lack of activity (feedback) and the existence of a solution, I'm thus closing this bug.
If you feel this issue still affects you, please reopen the present bug.

cheers
--- Arnaud

Changed in nut (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.