Comment 343 for bug 88746

Definetly, the Toby Dickerson's suggest works on NFORCE2 chipsets (tested on 5 different mobo/distro, kernels 2.6.22, 2.6.25 and 2.6.27)

3 steps:

1.- Find all devices created yet with autosuspend

# find /sys/ -name "autosuspend"
/sys/devices/pci0000:00/0000:00:02.0/usb1/power/autosuspend
/sys/devices/pci0000:00/0000:00:02.1/usb2/power/autosuspend
/sys/devices/pci0000:00/0000:00:02.2/usb3/power/autosuspend
/sys/devices/pci0000:00/0000:00:02.2/usb3/3-2/power/autosuspend
/sys/module/usbcore/parameters/autosuspend

and check his values

# cat `find /sys/ -name "autosuspend"`
2
2
2
2
2

2.- Change all of this values to -1

# echo -1 > /sys/devices/pci0000:00/0000:00:02.0/usb1/power/autosuspend
# echo -1 > /sys/devices/pci0000:00/0000:00:02.1/usb2/power/autosuspend
# echo -1 > /sys/devices/pci0000:00/0000:00:02.2/usb3/power/autosuspend
# echo -1 > /sys/devices/pci0000:00/0000:00:02.2/usb3/3-2/power/autosuspend
# echo -1 > /sys/module/usbcore/parameters/autosuspend

3.- Test again all of those are -1

# cat `find /sys/ -name "autosuspend"`
-1
-1
-1
-1
-1

All my usb sticks, HDD and printers works with 2.0 specs without any fault.

I could better make a script, but this more understantable for fixing

Someone can try this with another "bugged" chipset?

All credits to Toby Dickerson!

PD: Sorry about my poor english!