in the /proc/acpi/wakeup file
changing XHC from "enabled" to disabled does resolve this.
To disable ‘XHC’, do:
echo 'XHC' > /proc/acpi/wakeup
with superuser privilege.
Documented here >>
https://ubuntu-mate.community/t/ubuntu-wakes-up-immediately-after-suspend-how-to-fix-it/26848
--
You
I have a similar issue, maybe the same. But I found out I can suspend my
notebook by disabling bluetooth. If bluetooth is enabled, trying to
suspend will immediately (2 - 3 seconds) make the notebook wake up
again.
--
You received this bug notification because you are a member of Kernel
@Ole and @Feng.
The normal methodology of `echo XHC > /proc/acpi/wakeup` had no effect
whether `enabled` or `disabled`. By default `enabled` and all others are
`disabled`.
I also have `tlp` defaults which is probably USB_AUTOSUSPEND.
I could go into console mode and type `pm_suspend` (it's set
You can also try applying USB_QUIRK_DISCONNECT_SUSPEND to USB device one by one.
Boot with kernel parameter `usbcore.quirks=vid:pid:m` to apply the quirk.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Might be connected to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776266
Might a hardware issue. Sometimes the cable that connects the keyboard
and touchpad to the mainboard is flaky. This causes the devices to stop
working (see mentioned bug) or wake up the laptop (this bug).
If the workaround works for your system, that means some USB devices
connected to the xHC wakes up the system during suspend.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774994
Title:
@@Kai-Heng Feng (kaihengfeng) Everything seems to be fixed for both this
old bug and for new problems I was having over last few days.
I found a bug report from 2010 (link in script below) and used this:
#!/bin/bash
# Original script was using /bin/sh but shellcheck reporting warnings.
# NAME:
@Kai-Heng Feng (kaihengfeng) just an update...
Suddenly my suspend totally broke down (wakes immediately from suspend)
using same kernel I had for a few months (outdated `4.13.0-36-generic`).
In order to update to newer kernels I had to install libssl1.1 to side-
step linux-header installation
> I presume you want me to try the 9 rc's in the `4.15` kernel chain? I
assume the 8 to 9 rc's in `4.13`, 4.14`, `4.16`, `4.17`, `4.18` and `4.19`
rc's don't have to be installed?
Try 4.14 first. If it's bad, then the regression starts in one of the v4.14-rc*
kernel.
If it's good, then the
Hi
Kai-Heng Feng,
I presume you want me to try the 9 rc's in the `4.15` kernel chain? I
assume the 8 to 9 rc's in `4.13`, 4.14`, `4.16`, `4.17`, `4.18` and `4.19`
rc's don't have to be installed?
Also would it make sense to try the LTS kernel `4.14.78` first and see if
it's already been fixed?
Would it be possible for you to do a kernel bisection?
First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$
It's a kernel issue.
Using Ubuntu 16.04.5 LTS with the 18.04.1 LTS's kernel `4.15.0-36` when
you try to suspend it resumes after a dozen seconds or so. If you use
kernel `4.13.0-36` the suspend/resume cycle is normal. I believe
`4.13.0-36` was released for Ubuntu 17.10 which I've never installed
I've experienced similar situations for years where when resuming from
suspend, the system immediately completes uncompleted sleep and then
wakes up. More of an annoyance and loss of a second or two of life than
anything else.
Today however the cycle has changed with advent of nVidia drivers. Now
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17
15 matches
Mail list logo
