How do I make changes to /proc/acpi/wakeup permanent?

Question

I had a problem with my Ubuntu 12.04 waking up immediately after going into suspend. I solved the problem by changing the settings in /proc/acpi/wakeup, as suggested in this question: How do I prevent immediate wake up from suspend and/or hibernation?.

After changing the settings, the system goes flawlessly into suspend and stays suspended, but after I wake it back up, the settings in /proc/acpi/wakeup are different from what I set them to.

Before going to suspend:

cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
SMB0      S4    *disabled  pci:0000:00:03.2
PBB0      S4    *disabled  pci:0000:00:09.0
HDAC      S4    *disabled  pci:0000:00:08.0
XVR0      S4    *disabled  pci:0000:00:0c.0
XVR1      S4    *disabled  
P0P5      S4    *disabled  
P0P6      S4    *disabled  pci:0000:00:15.0
GLAN      S4    *enabled   pci:0000:03:00.0
P0P7      S4    *disabled  pci:0000:00:16.0
P0P8      S4    *disabled  
P0P9      S4    *disabled  
USB0      S3    *disabled  pci:0000:00:04.0
USB2      S3    *disabled  pci:0000:00:04.1
US15      S3    *disabled  pci:0000:00:06.0
US12      S3    *disabled  pci:0000:00:06.1
PWRB      S4    *enabled   
SLPB      S4    *enabled

I tell the system to suspend, and it works as it should. But later after waking it up, the settings are changed to either:

USB0      S3    *disabled  pci:0000:00:04.0
USB2      S3    *enabled   pci:0000:00:04.1
US15      S3    *disabled  pci:0000:00:06.0
US12      S3    *enabled   pci:0000:00:06.1

or

USB0      S3    *enabled   pci:0000:00:04.0
USB2      S3    *enabled   pci:0000:00:04.1
US15      S3    *enabled   pci:0000:00:06.0
US12      S3    *enabled   pci:0000:00:06.1

Any ideas?

---

Thank you for your response. Unfortunately it did not solve my problem.

all of

/sys/bus/usb/devices/usb1/power/wakeup
/sys/bus/usb/devices/usb2/power/wakeup
/sys/bus/usb/devices/usb3/power/wakeup
/sys/bus/usb/devices/usb4/power/wakeup

as well as

/sys/bus/usb/devices/3-1/power/wakeup

are set to disabled, and the notebook still wakes up by itself right after going to sleep. The only thing it seems to react to are the settings in /proc/acpi/wakeup, which keep changing (resetting) every time i power off/restart my notebook.

Answer 1

I ran into this problem again on Ubuntu 12.10. The suggestions from user MTS unfortunately also did not work for me. However, you can write a script to automatically set the usb properties in /proc/acpi/wakeup right before every suspend.

The solution is based on creating a suspend hook (based on this Archwiki article). Save the following as /usr/lib/pm-utils/sleep.d/45fixusbwakeup, and make sure to make it executable (chmod +x /usr/lib/pm-utils/sleep.d/45fixusbwakeup).

#!/bin/bash
case $1 in
    hibernate)
            echo "Going to suspend to disk!"
            ;;
    suspend)
            echo "Fixing acpi settings."
            for usb in `cat /proc/acpi/wakeup | grep USB | cut -f1`;
            do
                    state=`cat /proc/acpi/wakeup | grep $usb | cut -f3 | cut -d' ' -f1 | tr -d '*'`
                    echo "device = $usb, state = $state"
                    if [ "$state" == "enabled" ]
                    then
                            echo $usb > /proc/acpi/wakeup
                    fi
            done
            echo "Suspending to RAM."
            ;;
    thaw)
            echo "Suspend to disk is now over!"
            ;;
    resume)
            echo "We are now resuming."
            ;;
    *)
            echo "Somebody is callin me totally wrong."
            ;;
esac

What this does is change the status of every USB device that is currently enabled to disabled. If you only want to change specific USB devices, change the for loop in the script. For example to change only USB1 and USB3 change

for usb in `cat /proc/acpi/wakeup | grep USB | cut -f1`;

to

for usb in 'USB1' 'USB3';

Hopefully this helps someone else who has the same problem. This approach solved the issue for me.

Answer 2

Perhaps http://forum.xbmc.org/showthread.php?tid=121158 will help?

This is what it says:

For those who are updating to the 3.2 kernel (which should be everyone due to the recent root exploit), you'll notice your USB wakeup is probably broken. They changed the default wakeup policy (http://www.spinics.net/lists/linux-usb/msg53661.html), so you'll need to make a couple of changes:

• you no longer need to enable wakeup in /proc/acpi/wakeup, it's enabled by default
• you need to enable wakeup for the USB hub in addition to the device in /sys/bus/usb/devices/*/power/wakeup

So, this:

echo USB1 > /proc/acpi/wakeup
echo enabled > /sys/bus/usb/devices/3-1/power/wakeup

Becomes:

echo enabled > /sys/bus/usb/devices/usb3/power/wakeup
echo enabled > /sys/bus/usb/devices/3-1/power/wakeup

Hopefully this saves others from troubleshooting the same problem.

Answer 3

For Ubuntu 15+, you must use systemd instead of rc.local. You may google "Creating a systemd service" and follow the instructions, but note that redirecting output to /proc/acpi/wakeup is tricky. To get it to work correctly, you must do something like:

/bin/sh -c '/bin/echo XHC > /proc/acpi/wakeup'

Example output for the service file (e.g., /etc/systemd/system/suspendfix.service):

[Unit]
Description=fix to prevent system from waking immediately after suspend

[Service]
ExecStart=/bin/sh -c '/bin/echo XHC > /proc/acpi/wakeup'
Type=oneshot
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

Or here in this gist

Answer 4

The preferred way to do this is by creating a service with systemd.
Adding script in rc.local is the deprecated way.

1. Create a script file wherever you wish. Ex: ~/scripts/disable-devices-as-wakeup.sh.

#!/bin/bash

declare -a devices=(USB0 USB2 US12 US15) # <-- Add your entries here
for device in "${devices[@]}"; do
    if grep -qw ^$device.*enabled /proc/acpi/wakeup; then
        sudo sh -c "echo $device > /proc/acpi/wakeup"
    fi
done

2. Test it by executing it from the terminal.

3. If everything is okay then let's make a service.

$ touch ~/scripts/disable-devices-as-wakeup.service

~/scripts/disable-devices-as-wakeup.service -

[Unit]
Description=Disable devices as wakeup

[Service]
ExecStart=/home/username/scripts/disable-devices-as-wakeup.sh
Type=oneshot

[Install]
WantedBy=multi-user.target

4. Copy or move the service to /etc/systemd/system/.

$ sudo cp ~/scripts/disable-devices-as-wakeup.service /etc/systemd/system/

5. Enable the service.

$ systemctl enable disable-devices-as-wakeup.service

6. Restart the OS and check the status.

$ systemctl status disable-devices-as-wakeup.service

Detailed explanation found on https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/chap-managing_services_with_systemd

Answer 5

Based on @Hrishikesh Kadam's answer, but with more details and some improvements. 🤗

Disable the computer from waking up using the keyboard, mouse and others

List devices that can wakeup the system

List devices that can wakeup the system (they are as "*enabled")...

cat /proc/acpi/wakeup

Find out which device is

To find out which device is...

EXAMPLE

""" Device S-state Status Sysfs node [...] XHC S3 *disabled pci:0000:00:14.0 [...] """

... write down the device "node" - which in the example above is "00:14.0" - and use "lspci" utility to see which device it is...

EXAMPLE

lspci | grep "00:14.0"

PLUS: The cat /proc/bus/input/devices command also displays information about devices.

Configure the bash script

Knowing which devices are, configure the bash script below in the indicated location...

EXAMPLE

read -r -d '' FILE_CONTENT << 'HEREDOC'
BEGIN
#!/bin/bash

declare -a devices=("XHC" "RP05" "RP09" "RP13" "AWAC") # <<<--- ADD YOUR DEVICES HERE!
for device in "${devices[@]}"; do
    if grep -qw ^$device.*enabled "/proc/acpi/wakeup"; then
        echo "$device" > "/proc/acpi/wakeup"
    fi
done

END
HEREDOC
echo -n "${FILE_CONTENT:6:-3}" > "/usr/local/bin/disable-devices-as-wakeup.bash"

NOTE: The code above will create the file "/usr/local/bin/disable-devices-as-wakeup.bash".

... and make the script executable...

chmod +x /usr/local/bin/disable-devices-as-wakeup.bash

Create service file

Create a file to configure and run the created script as a service...

read -r -d '' FILE_CONTENT << 'HEREDOC'
BEGIN
[Unit]
Description=Disable devices as wakeup

[Service]
ExecStart=/usr/local/bin/disable-devices-as-wakeup.bash
Type=oneshot

[Install]
WantedBy=multi-user.target

END
HEREDOC
echo -n "${FILE_CONTENT:6:-3}" > "/etc/systemd/system/disable-devices-as-wakeup.service"

NOTE: The code above will create the file "/etc/systemd/system/disable-devices-as-wakeup.service".

Enable the "disable-devices-as-wakeup" service

Enable the "disable-devices-as-wakeup" service...

systemctl enable disable-devices-as-wakeup.service

Restart the OS and check the "disable-devices-as-wakeup" service status

Restart the OS and check the "disable-devices-as-wakeup" service status...

systemctl status disable-devices-as-wakeup.service

... and list devices that can wakeup the system...

cat /proc/acpi/wakeup

...to check if the expected result happened.

[Ref(s).: https://askubuntu.com/a/1316641/134723 , https://tecadmin.net/run-shell-script-as-systemd-service/ ]

FURTHER

I would like a more secure and accurate method to effectively identify what each device in the "/proc/acpi/wakeup" file is. I was not able, for example, to identify and disable my notebook's built-in keyboard to wakeup (I don't even know if this is possible) my syste. I was able to disable only the USB external keyboard, the USB mouse and the touchpad.

This is too basic a problem for us to have to resort to strategies like these in Linux. I see it as something that should have been solved simply and a long time ago in Linux... 🙄