On Fri, 6 Jan 2006, Franck wrote: > I was suspending both paths since I can't suspend a device, if its > interfaces are not suspended. > > $ echo -n 3 > /sys/bus/usb/devices/2-2\:1.0/power/state > $ cat /sys/bus/usb/devices/2-2\:1.0/power/state > 3 > $ echo -n 3 > /sys/bus/usb/devices/2-2/power/state > $ cat /sys/bus/usb/devices/2-2\:1.0/power/state > 3 > > *** Remote wakeup *** > > $ cat /sys/bus/usb/devices/2-2\:1.0/power/state > 0 # <----- OK interface seems to be resumed > $ cat /sys/bus/usb/devices/2-2/power/state > 3 # <----- KO interface seems to be resumed > > could you just try to suspend your mouse ?
Okay, I just did it. After I pressed the mouse button and it sent a remote wakeup, both power/state values were 0. > > Also, what kernel version + patchset are you using? Right now I'm on > > 2.6.15 together with gregkh-all-2.6.15.patch (which no longer exists; the > > current gregkh-all patch is for 2.6.15-git1). > > 2.6.15 Try again after applying the gregkh-all patch. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
