Ubuntu

System goes to S3 sleep three times

Reported by Marc A. Donges on 2008-12-14
2
Affects Status Importance Assigned to Milestone
pm-utils (Ubuntu)
Undecided
Unassigned

Bug Description

Package: pm-utils
Version: 1.2.2.1-0ubuntu1

(Package is just a guess. The problem might well be in the Linux kernel.)

Short Description: After pressing the Fn+Sleep button once, the system goes to S3 sleep three times ([1], [2], [3]). It should do this only once.

Long Description:

Using Ubuntu jaunty (current) on an IBM Thinkpad x200s (amd64), when I press the Fn+Suspend button on the keyboard to put the system in S3 sleep, it falls asleep after a few seconds. While falling asleep, the “Sleep” LED blinks; when finished, the “Sleep” LED is lit permanently [1].

After a few minutes, I wake the system. It wakes up, the “Sleep” LED goes off, and I can see the gnome-screensaver lock screen appears. That should be all. [A] However, instead of nothing else happening, the lock screen disappears after about a second, the “Sleep” LED starts blinking again and the system successfully goes to sleep [2].

So, I wake the system up again, by pressing the power button. It wakes up, the “Sleep” LED goes off, and I can see the gnome-screensaver lock screen appear for about a second. Then the “Sleep” LED starts blinking again and the system successfully goes to sleep [3].

Now, when I wake the system again with the power button, it wakes up, shows the gnome-screensaver lock screen and this time stays in that state, as it already should have after [A].

From the kernel log (Lines containing "PM:"):

Dec 14 21:25:54 isis kernel: [33333.059940] PM: Syncing filesystems ... done.
Dec 14 21:25:54 isis kernel: [33333.287401] PM: Preparing system for mem sleep
Dec 14 21:25:54 isis kernel: [33333.288384] PM: Entering mem sleep
Dec 14 21:25:54 isis kernel: [33334.644146] PM: suspend devices took 1.356 seconds
Dec 14 21:25:54 isis kernel: [33337.980291] PM: resume devices took 2.812 seconds
Dec 14 21:25:54 isis kernel: [33337.980314] PM: Finishing wakeup.
Dec 14 21:26:06 isis kernel: [33344.014381] PM: Syncing filesystems ... done.
Dec 14 21:26:06 isis kernel: [33344.200250] PM: Preparing system for mem sleep
Dec 14 21:26:06 isis kernel: [33344.220556] PM: Entering mem sleep
Dec 14 21:26:06 isis kernel: [33345.568142] PM: suspend devices took 1.348 seconds
Dec 14 21:26:06 isis kernel: [33348.516046] PM: resume devices took 2.536 seconds
Dec 14 21:26:06 isis kernel: [33348.516071] PM: Finishing wakeup.
Dec 14 21:26:21 isis kernel: [33354.725428] PM: Syncing filesystems ... done.
Dec 14 21:26:21 isis kernel: [33354.900524] PM: Preparing system for mem sleep
Dec 14 21:26:21 isis kernel: [33354.901416] PM: Entering mem sleep
Dec 14 21:26:21 isis kernel: [33356.236142] PM: suspend devices took 1.336 seconds
Dec 14 21:26:21 isis kernel: [33359.504311] PM: resume devices took 2.748 seconds
Dec 14 21:26:21 isis kernel: [33359.504334] PM: Finishing wakeup.

(timestamps are all from after resume, the system was put to sleep at approx. 21:13)

kosh@isis:~$ uname -a
Linux isis 2.6.28-2-generic #3-Ubuntu SMP Thu Dec 4 21:49:26 UTC 2008 x86_64 GNU/Linux

System has 4GiB RAM, 5GB swap, / and /home are ext4, /boot is ext3.

Geir Ove Myhr (gomyhr) wrote :

Thank you for reporting this bug. I'm going to mark this as a duplicate of bug 306310 as it seems to be the exact same issue. If you find something in that bug that is not compatible with your behaviour, feel free to unmark it.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers