On Thu, 21 Jun 2007, Mattia Dongili wrote: > > The log shows suspicious behavior on the part of the Sony UMH-U09 > > device, the first one in your ehci-only list above. When it was > > suspended it apparently disconnected itself from the USB bus, thereby > > triggering a wakeup signal. If at all possible, try unplugging the USB > > cable to that device and then see what happens when you suspend. > > wow, spotted! > > This device is an express card (SD/MMC reader). Do you have any > suggestion to make suspend work without any workarounds? You mean, do I have any suggestion about how to make the card reader behave properly? No. That needs more than a software change... :-) > I mean, all of this started by enabling wakeup on the ehci controller > USB1 S3 disabled pci:0000:00:1d.0 > USB2 S3 disabled pci:0000:00:1d.1 > USB3 S3 disabled pci:0000:00:1d.2 > USB4 S3 disabled pci:0000:00:1d.3 > USB7 S3 enabled pci:0000:00:1d.7 > > and this was triggered when trying to understand if enabling wakeup by > default on PCI devices was good or not (and the patch itself was > responsible or not for problems). > So, from my POV it's either not good or there has to be some way of > dealing with disconnecting devices on suspend. There _is_ a way: Disable wakeup on that USB controller. > Just to simplify, in this situation, if I had an usb mouse attached to > this usb controller and removed the mouse while suspended, would the > laptop wakeup? If the USB controller was enabled for wakeup and was working correctly, it would wake up the laptop. USB wakeup events are defined as: new connection, disconnection, overcurrent, plus any wakeup requests received from devices on the USB bus. > If so that's not what I most probably want. :) Maybe we should change the kernel so that the default wakeup setting for USB controllers is disabled. Then people would have to enable wakeup explicitly if they wanted to be able to start up their system by typing on a USB keyboard, for instance. > > You also ought to be able to prevent this immediate resume by disabling > > wakeup on the EHCI controller. For example: > > > > echo disable >/sys/bus/usb/devices/usb5/power/wakeup > > echo disable >/sys/bus/usb/devices/usb5/../power/wakeup > > that doesn't seem to work very well (on -rc5 at least): > $ echo disable > /sys/bus/usb/devices/usb2/power/wakeup > echo: write error: invalid argument > > The only value that seems to be accepted is 0 but reading the value > gives always "enabled". Whoops, yes, it should be "disabled" instead of "disable". And of course you have to use the correct USB bus number in the path -- I wrote usb5 because that was the bus number of the EHCI controller in your log. Alan Stern _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
