Need /proc/acpi/wakeup tweaks to enable mousepad and USB to wake up from suspend

Bug #109446 reported by Miles Lane
112
This bug affects 21 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

Binary package hint: acpi-support

I have a HP Pavillion dv1240us. I am running Ubuntu 7.04 (devel packages). I find that if I suspend my laptop by selecting System --> Quit --> Suspend, events from the Synaptics mouse and from the USB ports fail to wake the system. After tracking this down with the ACPI developers, I eventually determined that the necessary flags weren't set in /proc/acpi/wakeup. I would very much like to see updates to the various Ubuntu versions that caused the needed flags to be enabled by default.
I don't know if this bug should be assigned against acpi-support, powersaved, acpid or some other package.

On my machine, I get:
# cat /proc/acpi/wakeup
Device Sleep state Status
PCIB 5 disabled
 LAN 5 disabled
PS2K 3 disabled
PSM1 3 disabled
USB0 3 disabled
USB1 3 disabled
USB2 3 disabled
USB7 3 disabled

If I run:
# echo PSM1 > /proc/acpi/wakeup
# echo USB0 > /proc/acpi/wakeup
# echo USB1 > /proc/acpi/wakeup
# echo USB2 > /proc/acpi/wakeup
# echo USB7 > /proc/acpi/wakeup
then, when I plug in a USB device, the system wakes up.
This also causes my Synaptics mousepad to wake up the machine if I touch the mousepad or click one of the buttons.

After running these commands, "cat /proc/acpi/wakeup" gives me:
Device Sleep state Status
PCIB 5 disabled
 LAN 5 disabled
PS2K 3 enabled
PSM1 3 enabled
USB0 3 enabled
USB1 3 enabled
USB2 3 enabled
USB7 3 enabled

Revision history for this message
Paul Sladen (sladen) wrote :

This bug is hard to process because it's a policy issue (a question) that needs to be decided:

 * Should USB insertion or Mouse movement cause wake-up on a suspended/hibernated system?

If there are other ways of resuming the laptop (eg. opening the lid, pressing the power or Fn button), then this issue really a bug, but a need to answer the above question.

* * * * *

End of Policy issue, my own views:

Personally (this is my own view and may not be correct), is that USB wakeup by default would be a bad idea (a faulty USB device, or one that resets itself, or a USB device that is unplugged and replugged at the power-source would cause wakeup).

Mouse/keyboard, I'm not so sure about. Many people have 'cats'.

Revision history for this message
Miles Lane (miles-lane) wrote : Re: [Bug 109446] Re: Need /proc/acpi/wakeup tweaks to enable mousepad and USB to wake up from suspend

On 4/29/07, Paul Sladen <email address hidden> wrote:
> This bug is hard to process because it's a policy issue (a question)
> that needs to be decided:
>
> * Should USB insertion or Mouse movement cause wake-up on a
> suspended/hibernated system?

Yes.

> If there are other ways of resuming the laptop (eg. opening the lid,
> pressing the power or Fn button), then this issue really a bug, but a
> need to answer the above question.

The use case I am describing is a suspend that is triggered by
initiating suspend from the System --> Suspend menu. The lid of
the laptop isn't closed in this instance. However, if I suspend and
then close the lid and reopen it, the machine does resume.
Obviously, this is suboptimal.

> End of Policy issue, my own views:
>
> Personally (this is my own view and may not be correct), is that USB
> wakeup by default would be a bad idea (a faulty USB device, or one that
> resets itself, or a USB device that is unplugged and replugged at the
> power-source would cause wakeup).

I suspect that issues from faulty devices can all be resolved.
In fact, this is a non-issue, because David Brownell has already
submitted patches that cause USB to "just work" with wake-from-suspend.

> Mouse/keyboard, I'm not so sure about. Many people have 'cats'.

Wake-from-suspend as a result of keyboard and mousepad events
is the default behavior for Windows XP. It is the expected behavior for
standard users. We should provide the same, imho.

Matthew Garrett (mjg59)
Changed in acpi-support:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Jud Leonard (leonard-tlw) wrote :

My 2 cents --
I just installed Jaunty on an old Athlon, and I've spent the afternoon trying to figure out why it wouldn't wake up for the keyboard or mouse. All my Macs and PCs do. Maybe there should be an option for those whose cats wander, but the default should be to wake on mouse or keyboard activity.

Revision history for this message
Jud Leonard (leonard-tlw) wrote :

acpitool seems to have worked to enable keyboard and usb control.

Revision history for this message
Sam Brightman (sambrightman) wrote :

It seems to me quite clear that waking up on keyboard/mouse is pretty standard behaviour. More generally, options for power management are very limited (I've often gone to the power options and thought... "wow, that's it? can't fix it here then"). So on the policy issue I'm suggesting wake on kb/mouse as default, but configurable (along with e.g. lid options, USB devices, WOL etc.).

From my point of view the current status is: sub-optimal default, no GUI options. The choice of installing acpitool or even acpitoolgui has been presented here and in http://brainstorm.ubuntu.com/idea/21747 (don't know why this is closed). This seems to be a bit of an anti-solution: same default, unnecessarily large number of options available from command-line package/after installing from .deb.

The first solution from http://brainstorm.ubuntu.com/idea/21747 of enhancing the standard GUI a bit to deal with some common use-cases (and persist settings) seems like it could be incorporated elegantly. Is there still a policy issue? What are the objections to providing a simple UI to enable/disable wake settings?

Revision history for this message
Anders (andersja+launchpad-net) wrote :

I concur with Sam - I would have expected more of these options in gnome-power-manager - if it allows me to set expected behaviour when shutting the lid - why not allow me to set expected behaviour when opening the lid?

I've added a comment to http://brainstorm.ubuntu.com/idea/21747/ to include a link to this feature request.

Revision history for this message
Martin G Miller (mgmiller) wrote :

I am running Natty final on an Atom nettop connected as a HTPC. This is a badly needed feature. I finally figured out the commands to change /proc/acpi/wakeup for USB0, et al, and it now works, but this should be enabled "out of the box", or at least a GUI in gnome-power-manager.

Revision history for this message
Anders (andersja+launchpad-net) wrote :

@Martin - would you care to share your successful reciepe?

Revision history for this message
Rykel from Singapore (rykel98) wrote :

I am running Ubuntu 10.10 with kernel 3.0.6 and found that none of my USB and Bluetooth devices can wake up my system from Suspend. This is annoying and I do not know how I can set the laptop to resume at the press of a Bluetooth mouse button or USB keyboard key - much like it does in Windows and more notably, Mac.

Revision history for this message
Miles Lane (miles-lane) wrote : Invitation to connect on LinkedIn

Bug,

I'd like to add you to my professional network on LinkedIn.

- Miles

Miles Lane
Volunteer Open Source Software Tester at Ubuntu, Fedora, Linux Kernel
Raleigh-Durham, North Carolina Area

Confirm that you know Miles Lane:
https://www.linkedin.com/e/-2w0w8s-guqga0ez-4g/isd/4833797099/OeWqM4NX/?hs=false&tok=3pwqdgkcj_U4Y1

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-2w0w8s-guqga0ez-4g/vea6bY1HkfSVwT0Tqa8tDAKHxxDn9llZH10bSBe/goo/109446%40bugs%2Elaunchpad%2Enet/20061/I1681107989_1/?hs=false&tok=3UhgDfhTT_U4Y1

(c) 2011 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.