Ubuntu – Ubuntu wakes up immediately after suspend when USB mouse is connected

suspendusbwakeup

I have the problem that my Ubuntu wakes up immediately after suspend, not every time, but when I connect my USB 3.0 mouse.

When I start Ubuntu, it doesn't detect my mouse, so I must plug/unplug it few times, maybe suspend Ubuntu and wake it up. But when mouse is connected and works, then suspend doesn't work.

I tried editing the wakeup file and disabling some S3 lines, but after that, when I suspended Ubuntu, it turned off the screen, but the PC was still running, so it seems that isn't the right way to handle it.

How can I fix this properly?

Best Answer

This problem happens on my Ubuntu system as well. When it does, log in again, open a terminal, and run

$ ps aux | grep suspend

If you have the same problem I do, you will see a failed/hanging suspend process. That's what causes the system to start right again, because the suspend isn't finishing itself.

If in the same terminal you try this

$ sudo /sbin/shutdown -h now

you will get a refusal from the system, with a message saying something like that's a destructive transaction, that's the system d's way of saying that as long as that suspend process is hung, you aren't shutting down.

The only fix I know of is to kill the suspend process

$ kill -9 nnnnnn

where nnnnnn is the number of the hanging suspend process you see in the ps aux output.

I tried to track discussion of this in forums on the kernel and drivers, but it is pretty tough going. Some people claim it is being solved by kernel updates, say into the latest 4.6 and 4.8 editions, but I don't see any benefit. My problem, I'm pretty sure, links back to commercial Nvidia drivers that don't always get out of the way.

Related Solutions

Ubuntu – Immediate wake up from suspend caused by USB 3.0 devices

Firstly, it was not obvious to me that the XHC listing in the wakeup output was a USB 3.0 device.

XHC       S0    *enabled   pci:0000:00:14.0

However, even disabling the wakeup status of this device does not solve the problem.

sudo bash -c "echo disabled > \
    /sys/devices/pci0000:00/0000:00:14.0/power/wakeup"  # Problem persists.

The only working solution I have found is to unbind and bind the device driver using the following commands:

sudo bash -c ' \
  echo -n "0000:00:14.0" > /sys/bus/pci/drivers/xhci_hcd/unbind && \
  echo -n "0000:00:14.0" > /sys/bus/pci/drivers/xhci_hcd/bind;'

I must do this every time between connecting a USB 3.0 storage device and suspending the computer but it works consistently.

It should be noted that the xhci_hcd component of the path is only valid for USB 3.0 devices. This part of the path will need to be varied depending on the type of bus that needs to be reset, and might be one of uhci_hcd, sdhci-pci or ehci-pci for other types of storage device.

Ubuntu – Laptop wakes up by itself a few seconds after suspend or lidclose

August 8, 2018 Update

Kernel 4.15.0-30 has been released. The resume immediately after suspend problem persists. Kernel 4.13.0-36 still works reliably.

Additional steps to try

I have the same problem on 4.15.0-29-generic. I had just installed nVidia driver 384.130 and assumed it was related to that. I went through all your steps plus I modified:

$ paste <(ls /sys/bus/usb/devices/*/power/wakeup) <(cat /sys/bus/usb/devices/*/power/wakeup) | column -s $'\t' -t
/sys/bus/usb/devices/1-1.4.3/power/wakeup  disabled
/sys/bus/usb/devices/1-1.4/power/wakeup    disabled
/sys/bus/usb/devices/1-1/power/wakeup      disabled
/sys/bus/usb/devices/1-4/power/wakeup      disabled
/sys/bus/usb/devices/1-5/power/wakeup      enabled
/sys/bus/usb/devices/1-9/power/wakeup      disabled
/sys/bus/usb/devices/usb1/power/wakeup     disabled
/sys/bus/usb/devices/usb2/power/wakeup     disabled
/sys/bus/usb/devices/usb3/power/wakeup     disabled
/sys/bus/usb/devices/usb4/power/wakeup     disabled

USB 1-5 is the WiFi / Bluetooth card:

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 007: ID 1bcf:2b8c Sunplus Innovation Technology Inc. 
Bus 001 Device 005: ID 0cf3:e301 Atheros Communications, Inc. 
Bus 001 Device 003: ID 187c:0528 Alienware Corporation 
Bus 001 Device 008: ID 413c:9016 Dell Computer Corp. 
Bus 001 Device 006: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 001 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

You can check this as well.

Unplug everything

Intel recommends unplugging everything-- All USBs, Network cable, etc to debug suspending. There are other things to try listed in Intel's article.

Kernel `4.13.0-36` works!

I recompiled my nvhda.ko under kernel 4.13.0-36-generic and discovered that suspend through the menu at least works now.

If you have an older kernel version like 4.15.0-24 in your Advanced Grub menu boot with that.
If you have 4.13.0-36 boot with that.
If you don't have an older version you can install it with sudo apt install linux-image-4.15.0-24*
If you use DKMS you also need to use sudo apt install linux-headers-4.15.0-24*
I don't see kernels 4.15.0-25 through 4.15.0-28 available in the repository.