*** This bug is a duplicate of bug 693594 ***
https://bugs.launchpad.net/bugs/693594
I'm marking this a duplicate of #693594 but if you come across this here
are some Workarounds/Fixes:
1)do not move all tasks into a default cgroup
comment CREATE_DEFAULT=yes out and uncomment CREATE_DEFAULT=
I was seeing exactly the same symptoms as stgraber (first suspend
worked), and removing cgroup-bin indeed solved it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756499
Title:
cgroup-bin breaks sus
Right, in my case with current cgroup-bin, I observe the following:
1) Boot my laptop with cgroup-bin
2) Suspend
3) Resume
4) Works fine
5) Suspend
6) System freezes, unresponsive
So I can do an initial suspend/resume sequence before I get hit by the bug.
Removing cgroup-bin fixes the proble
Another report suggests this is not in fact fixed.
** Changed in: libcgroup (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756499
Title:
cgroup-bin
I believe this is fixed in current oneiric (and natty) packages. Please
re-open if I'm wrong about that.
** Changed in: libcgroup (Ubuntu)
Status: Triaged => Fix Released
** Changed in: libcgroup (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because y
** Changed in: libcgroup (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756499
Title:
cgroup-bin breaks suspend to RAM
--
ubuntu-bugs mailing list
ubuntu-bugs
Yes, that does the trick. Here's the new cgconfig.conf:
group sysdefault {
cpu {
cpu.rt_runtime_us = 50;
}
}
mount {
cpu = /dev/cgroup/cpu;
cpuacct = /dev/cgroup/cpuacct;
}
BTW the stock config file defined /mnt/cgroups as the root for cgroup
mounts. I think the defau
This sounds a lot like Debian bug #555711 [1]. Can you take a look at
that and see if the proposed fix solves your problem?
[1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555711
** Bug watch added: Debian Bug tracker #555711
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555711
--
Y
