Bug 316801

(In reply to comment #0)
> Also see bug 246713, which may be related to this bug. I have booted kernel
> 2.6.22.9-91 with the usbcore.autosuspend=0 option.

Zero means suspend with no delay. To disable, use usbcore.autosuspend=-1

Thanks! The system is now running stable since I used usbcore.autosuspend=-1.

Is -1 the default value? (I.e. do I need to put this boot option into grub.conf,
anyways?)

(In reply to comment #2)
> Thanks! The system is now running stable since I used usbcore.autosuspend=-1.
> 
> Is -1 the default value? (I.e. do I need to put this boot option into grub.conf,
> anyways?)

-1 is not the default.

Would it be possible to try Rawhide kernel? I want to know if the new
"hub-only" autosuspend in it works ok.

The kernel can be found in
http://download.fedora.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/
(or i386/ if you have a 32-bit system). Keep in mind though, it would prevent
normal updates with yum from taking place, because it's "newer" than fc7.
So just do rpm -i, test, rpm -e.

I misspoke in comment #3: usbcore.autosuspend=-1 is the default in Fedora 7. So
this problem was caused by setting autosuspend to 0 (which we should just reject
anyway, it makes no sense to set it to that.)

(In reply to comment #4)
Pete, I have tried kernel-2.6.23-0.224.rc9.git6.fc8 (i686) from Rawhide, without
the autosuspend option being set. After about 30 hours of uptime, the error
appeared again.

First:

Oct 12 05:55:43 monique kernel: hub 5-8:1.0: activate --> -110
Oct 12 05:55:43 monique kernel: hub 5-8:1.0: hub_port_status failed (err = -108)
Oct 12 05:55:43 monique last message repeated 3 times

Then repeatedly until reboot (about every two seconds):

Oct 12 05:55:46 monique kernel: hub 5-8:1.0: activate --> -108
Oct 12 05:55:46 monique kernel: hub 5-8:1.0: hub_port_status failed (err = -108)
Oct 12 05:55:46 monique last message repeated 3 times

This weekend I will test the latest F7 production kernel without the autosuspend
option. According to Chuck in comment #5, it should work as reliable as with
autosuspend=-1.

kernel-2.6.22.9-91.fc7 is also working stable without autosuspend option. Which
means that the bug occured because I was messing with the kernel options. I am
sorry for the noise.

The bug reoccured today with kernel 2.6.23.1-10.fc7 without autosuspend option.
It happened again after about 30 hours uptime.

Nov 10 04:17:47 monique kernel: hub 5-8:1.0: activate --> -110
Nov 10 04:17:47 monique kernel: hub 5-8:1.0: hub_port_status failed (err = -108)
Nov 10 04:17:47 monique last message repeated 3 times

Then every two seconds:

Nov 10 04:17:50 monique kernel: hub 5-8:1.0: activate --> -108
Nov 10 04:17:50 monique kernel: hub 5-8:1.0: hub_port_status failed (err = -108)
Nov 10 04:17:50 monique last message repeated 3 times

What is the reason for this error? And is there a way to fix it for good?

Unfortunately the Fedora 8 autosuspend changes leaked into the Fedora 7 kernel.
This controls autosuspend by device classes, and apparently doesn't work. Looks
like it should go back to being disabled completely by default.

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Closing as per previous comment. Please re-open if this is still an issue for you.