2012/3/26 Martin Mokrejs <mmokrejs@xxxxxxxxxxxxxxxxxx>: > Elric Fu wrote: >> 2012/3/26 Martin Mokrejs <mmokrejs@xxxxxxxxxxxxxxxxxx>: >>> Elric Fu wrote: >>>> 2012/3/26 Martin Mokrejs <mmokrejs@xxxxxxxxxxxxxxxxxx>: >>>>> Hi, >>>>> I tried one of the "stable" kernels with my Dell Votro 3550 laptop >>>>> with a USB2.0 hub connected to its eSATA/USB2.0 port. Is this a known >>>>> issue? Aside from removing USB suspend from the kernel, is there any >>>>> other way to get rid of this? >>>> >>>> The kernel is too old. The power management implementation for USB3 >>>> was supported from 2.6.37. You should use the lastest kernel. >>> >>> Ah, thanks. So how about disabling CONFIG_USB_SUSPEND altogether >>> for USB3.0 in those old kernels? I mean really to disable it in the xHCI >>> driver only. >>> >>> But the message I reported here is a USB2.0 connection through an >>> internal eSATA/USB2.0 connector on the laptop. So are we talking about >>> the same? >> >> Maybe you can write a negative number to /sys/bus/usb/[dev bus name]/ >> power/autosuspend. The negative value of autosuspend means disabling >> autosuspend. > > # ls -la /sys/bus/usb/devices/3-0\:1.0/power/ > total 0 > drwxr-xr-x 2 root root 0 Mar 26 15:24 . > drwxr-xr-x 4 root root 0 Mar 26 15:24 .. > -rw-r--r-- 1 root root 4096 Mar 26 15:24 wakeup > # > # ls -la /sys/bus/usb/devices/3-0\:1.0/power/ > total 0 > drwxr-xr-x 2 root root 0 Mar 26 15:24 . > drwxr-xr-x 4 root root 0 Mar 26 15:24 .. > -rw-r--r-- 1 root root 4096 Mar 26 15:24 wakeup > # find /sys/bus/usb/devices/ -name autosuspend > # find /sys/bus/usb/devices/ -name autosuspend > # gzip -dc /proc/config.gz | grep SUSPEND > CONFIG_ARCH_SUSPEND_POSSIBLE=y > CONFIG_SUSPEND=y > CONFIG_SUSPEND_FREEZER=y > CONFIG_USB_SUSPEND=y > # uname -a > Linux vostro 2.6.32.59-default #2 SMP Mon Mar 26 01:15:46 MEST 2012 x86_64 Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz GenuineIntel GNU/Linux > # echo -n -1 > /sys/bus/usb/devices/3-0\:1.0/power/autosuspend > -su: /sys/bus/usb/devices/3-0:1.0/power/autosuspend: No such file or directory > # > > What am I doing wrong? ;) What you do is correct. Actually, I don't know why the USB3 bus don't have the autosuspend file. Anyway, I don't think it is a issue. The "-2" is -ENOENT. It is a returned value when the hcd_bus_suspend() identify hcd->driver->bus_suspend is NULL. As I said, the kernel can't support bus suspend/resume. So I think you just need to shutdown the CONFIG_USB_DEBUG. Then the syslog doesn't show the messages. Best Regards, Elric Fu > Thanks, > Martin -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html