** 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 than about 40 seconds the machine
  always hangs on resume. I verified this behaviour several times:
  
  - suspend -> wait a few seconds - resume -> fine!
  - suspend -> wait 60 seconds - resume -> hang!
  
  Tonight, I tried to find out more by following the guide on
  https://wiki.ubuntu.com/DebuggingKernelSuspend. With interesting
  results:
  
  - "sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force" -> wait
  2 minutes - resume - fine!!!
  
- Again, I verified this several times: it works every time. I also
- verified that the behaviour does not depend on using the "sleep.sh"
- script for suspend instead of the gnome-power-manager:
- 
- - "/etc/acpi/sleep.sh force" -> wait 1 minute - resume - hang!
+ Again, I verified this several times: it works every time.
  
  In short: the error does not occur when I use the debugging procedure!
  So how can I find out what's going on???
  
  I know that I could just use Suspend-To-RAM with tracing turned on...
  but it messes with my hardware clock and I would like to help to get rid
  of this bug completely, too.
  
  Any ideas?

** Tags added: acpi resume suspend

** 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 than about 40 seconds the machine
  always hangs on resume. I verified this behaviour several times:
  
  - suspend -> wait a few seconds - resume -> fine!
  - suspend -> wait 60 seconds - resume -> hang!
  
  Tonight, I tried to find out more by following the guide on
  https://wiki.ubuntu.com/DebuggingKernelSuspend. With interesting
  results:
  
  - "sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force" -> wait
  2 minutes - resume - fine!!!
  
  Again, I verified this several times: it works every time.
  
- In short: the error does not occur when I use the debugging procedure!
- So how can I find out what's going on???
+ In short: the error does not occur when I turn on tracing! So how can I
+ find out what's going on???
  
  I know that I could just use Suspend-To-RAM with tracing turned on...
  but it messes with my hardware clock and I would like to help to get rid
  of this bug completely, too.
  
  Any ideas?

** 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 than about 40 seconds the machine
  always hangs on resume. I verified this behaviour several times:
  
  - suspend -> wait a few seconds - resume -> fine!
  - suspend -> wait 60 seconds - resume -> hang!
  
  Tonight, I tried to find out more by following the guide on
  https://wiki.ubuntu.com/DebuggingKernelSuspend. With interesting
  results:
  
  - "sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force" -> wait
  2 minutes - resume - fine!!!
  
  Again, I verified this several times: it works every time.
  
- In short: the error does not occur when I turn on tracing! So how can I
- find out what's going on???
- 
- I know that I could just use Suspend-To-RAM with tracing turned on...
- but it messes with my hardware clock and I would like to help to get rid
- of this bug completely, too.
+ In short: the error does not occur when I turn on tracing! So how can I find 
out what's going on???
+ Of course, I could just use Suspend-To-RAM with tracing turned on... but it 
messes with my hardware clock and I would like to help to get rid of this bug 
completely, too.
  
  Any ideas?

** 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 than about 40 seconds the machine
+ don't wait too long. If I wait longer than about 40 seconds, the machine
  always hangs on resume. I verified this behaviour several times:
  
  - suspend -> wait a few seconds - resume -> fine!
  - suspend -> wait 60 seconds - resume -> hang!
  
  Tonight, I tried to find out more by following the guide on
  https://wiki.ubuntu.com/DebuggingKernelSuspend. With interesting
  results:
  
  - "sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force" -> wait
  2 minutes - resume - fine!!!
  
  Again, I verified this several times: it works every time.
  
  In short: the error does not occur when I turn on tracing! So how can I find 
out what's going on???
  Of course, I could just use Suspend-To-RAM with tracing turned on... but it 
messes with my hardware clock and I would like to help to get rid of this bug 
completely, too.
  
  Any ideas?

** 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 than about 40 seconds, the machine
- always hangs on resume. I verified this behaviour several times:
+ always hangs on resume. I verified this behaviour several times. It's
+ always the same:
  
  - suspend -> wait a few seconds - resume -> fine!
  - suspend -> wait 60 seconds - resume -> hang!
  
  Tonight, I tried to find out more by following the guide on
  https://wiki.ubuntu.com/DebuggingKernelSuspend. With interesting
  results:
  
  - "sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force" -> wait
  2 minutes - resume - fine!!!
  
  Again, I verified this several times: it works every time.
  
  In short: the error does not occur when I turn on tracing! So how can I find 
out what's going on???
  Of course, I could just use Suspend-To-RAM with tracing turned on... but it 
messes with my hardware clock and I would like to help to get rid of this bug 
completely, too.
  
  Any ideas?

** Attachment added: "uname-a.log"
   http://launchpadlibrarian.net/10345910/uname-a.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 Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to