random usb hub lockups with connect-debounce failed

[kerryh]

My USB IR device is connected to a fedora 9 system.
I tried updating to fedora 10 a while back, but when the device was plugged in it would not work and would get a log of the following messages in /var/log/messges
kernel: hub 2-0:1.0: connect-debounce failed, port 2 disabled
A reboot of the system would result in the system hanging while bios was detecting USB devices. The only way to get past this was to completely power down and cold boot.
Since this problem did not occur in fedora 9, I decided to put it on the back burner to look at later and went back to fedora 9.
The same thing happened when I tried fedora 11.
It has now started randomly happening in fedora 9. Previously the mythbox was running 24/7, but with the long hot summer, it now self boots to record things or we boot it when we want to watch something.
We are now seeing the connect-debounce message sometimes, corresponding with the remote not working, and some reboots are failing while bios is detecting usb devices.

I have thought about reflashing the device, but was unsure if that was wise.

igclient returns: get version: success: version=0x0102 get features: success: features=0x2

I am using version 0.97-1 of the software. The software will not upgrade via yum due to dependency issues with libusb. Similarly, the reflasher will not work without libusb 1.? Fedora 9 only has libusb 0.1.12 in the repository. I have compiled libusb version 1.0.6 from source on a differnt system so I can reflash from there. I have also compiled the latest iguanaIR code. However, if I reflash to the latest firmware, will I also have to upgrade the drivers on the mythbox?

[jdunn]

The connect debounce failed messages sound like either the firmware on the device is hanging, or a hardware fault. Since you say that it happens in Fedora 9 and did not before it seems unlikely that it would be a firmware problem, but it is worth a reflash to find out for certain. There is not specific dependency on libusb 1.0, but most people get better performance with it which is why we added a second driver. To avoid people getting the libusbpre1 driver and having the same problems we added a dependency on libusb 1.0. In reality, you should be able to install iguanaIR-1.0pre2 without installing libusb 1.0 using an rpm --nodeps option, but be certain that libusb1.0 is the only dependency you're avoiding. Also, our rpms are usually built against the latest fedora, and so may not run properly on old Fedora systems. You are welcome to build the package yourself from our source package, or try to install and run the reflasher on a fedora 10 or 11 machine.

In any case, if you reflash the device you will have to upgrade the drivers on the myth machine to something that supports the version of the firmware you flash to. From looking at our repository the current firmware version (0x306) was introduced with 1.0pre1 so I would suggest upgrading to at least that version. Ideally I would suggest upgrading to 1.0pre2 with libusb 1.0 because it fixes some rather irritating hangups users were experiencing.

[bluey]

We haven't seen any feedback on this ticket in 2 months. Please respond with an update or we will close the ticket.

Thank you,

Ben

[kerryh]

I tried to reflash on Fedora 10 and 11, but got the connect debounce straight away before I could reflash. I then tried compiling the latest driver on Fedora 9, and after a lot of dependency issues, got it compiled. However, it would not recognise the device so I could not reflash.

On a positive note, I removed the device from the system and the mysterious system hangs that I was getting disappeared. I had previously assumed that these were unrelated to the USB device.

I would conclude that this is probably a hardware problem with the device it's self.

Thanks.

[jdunn]

Agreed, and if you would like to coordinate a return/exchange please email me (jdunn) directly and we can get that taken care of. I'm closing this ticket as resolved since I'm fairly certain it is purely a hardware problem.