Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-08 Thread Florian Merz
Hi Bjørn, Those fixes seem to work. I could't reproduce the bug. Autosuspend uses D3cold now instead of D2. Thank for your help everyone. Florian Merz -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-07 Thread Florian Merz
Hi Bjørn, If I find the time, I'll try the fixes this evening. Thanks for the hint. Florian Merz > > This sounds terribly similar to the issues I had with linux-next a while > ago. And those issues are still present in mainline. Florian could try > the fixes available in > > > http://git.k

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-07 Thread Bjørn Mork
Alan Stern writes: > On Thu, 6 Sep 2012, Florian Merz wrote: > >> I've attached the dmesg (USB_DEBUG enabled) output from boot to >> enabling a usb port manually (380) until plugging in a device (404). > > I think the problem shows up in these lines: > > [3.520138] xhci_hcd :00:14.0: powe

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-07 Thread Florian Merz
> I think the problem shows up in these lines: > > [3.520138] xhci_hcd :00:14.0: power state changed by ACPI to D2 > [5.542872] ehci_hcd :00:1a.0: power state changed by ACPI to D2 > [5.642683] ehci_hcd :00:1d.0: power state changed by ACPI to D2 > > It may be that your host

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-07 Thread Alan Stern
On Thu, 6 Sep 2012, Florian Merz wrote: > I've attached the dmesg (USB_DEBUG enabled) output from boot to > enabling a usb port manually (380) until plugging in a device (404). I think the problem shows up in these lines: [3.520138] xhci_hcd :00:14.0: power state changed by ACPI to D2 [

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-06 Thread Alan Stern
On Fri, 7 Sep 2012, Ruslan Bilovol wrote: > Hi Florian, > > This is just a suggestion, but.. maybe you have a hub between a host > and a device? > In such case you need to enable remote wakeups for it. For example, > using your little script: > > for i in `find /sys/bus/usb/devices/*/power/wakeu

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-06 Thread Ruslan Bilovol
Hi Florian, This is just a suggestion, but.. maybe you have a hub between a host and a device? In such case you need to enable remote wakeups for it. For example, using your little script: for i in `find /sys/bus/usb/devices/*/power/wakeup`; do echo enabled > $i; done; -- Best regards, Ruslan Bi

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-06 Thread Florian Merz
Hi Alan, > Do you mean that if you plug in a new USB device, nothing happens? > > Or do you mean that some USB devices which were present during boot > don't get detected? > The first, when I plug in a new USB device. > Are the undetected devices attached to a USB-2 port or a USB-3 port? > I c

Re: When enabling usb autosuspend, new usb devices aren't recognized

2012-09-06 Thread Alan Stern
On Thu, 6 Sep 2012, Florian Merz wrote: > Hi, > > To enable usb autosuspend i use the following in a script after booting: > for i in `find /sys/bus/usb/devices/*/power/control`; do echo auto > $i; done; > for i in `find /sys/bus/usb/devices/*/power/autosuspend`; do echo 2 > $i; > done; > > Aft

When enabling usb autosuspend, new usb devices aren't recognized

2012-09-06 Thread Florian Merz
Hi, To enable usb autosuspend i use the following in a script after booting: for i in `find /sys/bus/usb/devices/*/power/control`; do echo auto > $i; done; for i in `find /sys/bus/usb/devices/*/power/autosuspend`; do echo 2 > $i; done; After this new usb devices aren't recognized anymore. Whether