Public bug reported:
Binary package hint: linux-image-2.6.22-14-386
I am running Gutsy i386 on an NForce4 based board (Gigabyte GA-K8N Pro-
SLI) with an Athlon X2 3800+-.
Resuming from Suspend-To-RAM (ACPI S3) works fine -- but only when I
don't wait too long. If I wait longer than about 40 seco
** Description changed:
Binary package hint: linux-image-2.6.22-14-386
I am running Gutsy i386 on an NForce4 based board (Gigabyte GA-K8N Pro-
SLI) with an Athlon X2 3800+-.
Resuming from Suspend-To-RAM (ACPI S3) works fine -- but only when I
don't wait too long. If I wait longer
** Attachment added: "version.log"
http://launchpadlibrarian.net/10345911/version.log
--
Resume from ACPI S3 does not work -- when waiting too long
https://bugs.launchpad.net/bugs/162320
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10345916/lspci-vvnn.log
--
Resume from ACPI S3 does not work -- when waiting too long
https://bugs.launchpad.net/bugs/162320
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/10345913/dmesg.log
--
Resume from ACPI S3 does not work -- when waiting too long
https://bugs.launchpad.net/bugs/162320
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
This is probably caused by dynamic clock change aka Cool'n Quiet (on AMD
processors). If the processor hasn't got much to do, the kernel will
clock it down in order to save energy. Try to run some CPU-intensive
task and meanwhile check /proc/cpuinfo again: it should report the
expected cpu MHZ.
--
** Attachment added: "dmidecode.log"
http://launchpadlibrarian.net/10351237/dmidecode.log
--
Resume from ACPI S3 does not work -- when waiting too long
https://bugs.launchpad.net/bugs/162320
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
The fact that resume always works when PM tracing is turned on (which
just manipulates the RTC state to store the debug info) brought me to me
the idea that the problem might be related to the RTC.
So I changed the /etc/acpi/sleep.sh script:
# Generic preparation code
. /etc/acpi/prepare.sh
if
Thanks for your reply.
Unfortunately, I don't have a "hpet" Clock Event Device (I attached the
output of "cat /proc/timer_list").
As you seem to know something about this problem, do you have any more
ideas / related information?
Thanks in advance.
** Attachment added: "timer_list.txt"
http:
