This bug was fixed in the package ec2-hibinit-agent - 1.0.0-0ubuntu9.1
---
ec2-hibinit-agent (1.0.0-0ubuntu9.1) focal; urgency=medium
* Disable suspending the system (LP: #1898087)
* Always set resume device by PARTUUID instead of by device name.
Based on patch by Francis
** Changed in: ec2-hibinit-agent (Ubuntu)
Assignee: (unassigned) => ubuntu18 (sudana)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898087
Title:
Please disable suspend when the package is
Thanks, marking Bionic and Xenial as won't fix. Please reopen the bug
against those releases if the SRU becomes needed.
** Changed in: ec2-hibinit-agent (Ubuntu Xenial)
Status: Incomplete => Won't Fix
** Changed in: ec2-hibinit-agent (Ubuntu Bionic)
Status: Incomplete => Won't Fix
Just a comment to make sure we're all on the same page: this fix is only
required in focal for now, because systemd in bionic and xenial does not
have sleep.conf and does not recognize AllowSuspend=no.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verified 1.0.0-0ubuntu9.1 on Focal:
ubuntu@ip-172-31-1-183:~$ dpkg -l ec2-hibinit-agent | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Hello Balint, or anyone else affected,
Accepted ec2-hibinit-agent into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ec2
-hibinit-agent/1.0.0-0ubuntu9.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
I've uploaded the fix for Focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898087
Title:
Please disable suspend when the package is installed
To manage notifications about this bug go to:
@arighi, thanks for the info.
Is the deadlock observed on Bionic/Xenial, too?
Systemd in Bionic/Xenial does not support AllowSuspend=, etc., just
SuspendMode=, HibernateMode=, HybridSleepMode= and SuspendState=,
HibernateState=, HybridSleepState=.
Setting *Mode=hibernate would probably work.
** Changed in: ec2-hibinit-agent (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: ec2-hibinit-agent (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package ec2-hibinit-agent - 1.0.0-0ubuntu11
---
ec2-hibinit-agent (1.0.0-0ubuntu11) groovy; urgency=medium
* Disable suspending the system (LP: #1898087)
* Always set resume device by PARTUUID instead of by device name.
Based on patch by Francis
** Description changed:
[Impact]
- * TODO
-
+ Enabling CONFIG_SUSPEND in the kernel exposes a potential deadlock on
+ Xen instance types on AWS during hibernation, so it has been disabled in
+ the linux-aws kernel as an extra safety measure to prevent this problem
+ from happening.
@rbalint about the robustness problem: enabling CONFIG_SUSPEND exposes a
potential deadlock on Xen instance types on AWS during hibernation, so
it has been disabled in the AWS kernel as an extra safety measure to
prevent this problem from happening.
Setting "AllowSuspend=no" would be a reasonable
** Changed in: ec2-hibinit-agent (Ubuntu)
Status: In Progress => Incomplete
** Changed in: ec2-hibinit-agent (Ubuntu Focal)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@fginther Could you please fill the [Impact] part? I do understand how
having sleep enabled is not desired, but I don't have much information
about the robustness problem.
Suspend seems to be disabled on AWS kernels, but not on OEM ones which
can also be installed on EC2 instances.
--
You
** Description changed:
- From LP: #1892728
- We also need to set "AllowSuspend=no" in /etc/systemd/sleep.conf (or a .d
file) as CONFIG_SUSPEND has been disabled in the kernel to improve the
robustness of hibernation.
+ [Impact]
+
+ * TODO
+
[Test Case]
Try to suspend the system as
Should this be back-ported to Bionic and Xenial, too?
** Also affects: ec2-hibinit-agent (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ec2-hibinit-agent (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ec2-hibinit-agent (Ubuntu Bionic)
** Description changed:
From LP: #1892728
We also need to set "AllowSuspend=no" in /etc/systemd/sleep.conf (or a .d
file) as CONFIG_SUSPEND has been disabled in the kernel to improve the
robustness of hibernation.
+
+ [Test Case]
+
+ $ /lib/systemd/systemd-sleep suspend
+ Sleep mode
17 matches
Mail list logo
