Package: linux-2.6
Version: 3.1.8-2
Severity: important
Dear Maintainer,
For the last several kernel releases, I have had an intermittent problem
suspending my Thinkpad X40. A high fraction of the time, after I
suspend (running pm-suspend), the system seems to go to sleep (the
screen goes off and the moon light comes on), then comes back by itself
a couple minutes later. Of course, the laptop is usually in my bag by
this point. Worse, pm-suspend returns a successful 0 exit status, so
there's no way I can sound an alert.
The logs aren't very helpful, but I hope you can make something of them
on at least point me to where I can get more help.
In this instance, I ran pm-suspend at 09:13:45, and the system came back
on its own at 09:15:22. Here is an excerpt from
/var/log/pm-suspend.log:
Mon Jan 23 09:13:45 PST 2012: performing suspend
KMS graphics driver is in use, skipping quirks.
Mon Jan 23 09:15:22 PST 2012: Awake.
Here is an excerpt from /var/log/kern.log:
Jan 23 09:13:46 apple kernel: [ 4407.572159] PM: Syncing filesystems ...
done.
Jan 23 09:13:46 apple kernel: [ 4407.574433] PM: Preparing system for mem
sleep
Jan 23 09:15:22 apple kernel: [ 4407.617900] Freezing user space processes
... (elapsed 0.01 seconds) done.
Jan 23 09:15:22 apple kernel: [ 4407.632227] Freezing remaining freezable
tasks ... (elapsed 0.11 seconds) done.
Jan 23 09:15:22 apple kernel: [ 4407.744205] PM: Entering mem sleep
...
Jan 23 09:15:22 apple kernel: [ 4408.352342] ACPI: Preparing to enter
system sleep state S3
Jan 23 09:15:22 apple kernel: [ 4408.552054] PM: Saving platform NVS memory
Jan 23 09:15:22 apple kernel: [ 4408.552127] Extended CMOS year: 2000
Jan 23 09:15:22 apple kernel: [ 4408.552127] ACPI: Low-level resume complete
...
Jan 23 09:15:22 apple kernel: [ 4411.122275] PM: Finishing wakeup.
Jan 23 09:15:22 apple kernel: [ 4411.122279] Restarting tasks ... done.
(I realize that the syslog timestamp just reflects when the message got
to syslogd, and the kernel timestamp isn't updated on resume.) There
are no messages indicating that anything went wrong. So I don't
understand why it woke up. The pattern of log messages is very similar
(just some small ordering differences) whether the resume was at my
command or not. Any ideas?
I don't have any automated wake-ups, such as wake-on-lan or rtcwake,
as far as I know.
Complete pm-suspend.log and kern.log from the failed suspend are
attached.
Andrew
-- Package-specific info:
** Version:
Linux version 3.1.0-1-486 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc version
4.6.2 (Debian 4.6.2-11) ) #1 Tue Jan 10 04:55:10 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-486
root=UUID=73cf35da-d145-4e4b-b662-3849f9a0ae64 ro
** Not tainted
** Kernel log:
[ 4409.648033] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[ 4409.648042] uhci_hcd :00:1d.0: restoring config space at offset 0xf (was
0x100, writing 0x10b)
[ 4409.648057] uhci_hcd :00:1d.0: restoring config space at offset 0x8 (was
0x1, writing 0x1821)
[ 4409.648073] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was
0x280, writing 0x281)
[ 4409.648085] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[ 4409.648091] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[ 4409.648099] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[ 4409.648106] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[ 4409.648114] uhci_hcd :00:1d.1: restoring config space at offset 0xf (was
0x200, writing 0x20b)
[ 4409.648129] uhci_hcd :00:1d.1: restoring config space at offset 0x8 (was
0x1, writing 0x1841)
[ 4409.648144] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was
0x280, writing 0x281)
[ 4409.648155] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[ 4409.648161] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[ 4409.648171] uhci_hcd :00:1d.2: restoring config space at offset 0xf (was
0x300, writing 0x30b)
[ 4409.648186] uhci_hcd :00:1d.2: restoring config space at offset 0x8 (was
0x1, writing 0x1861)
[ 4409.648201] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was
0x280, writing 0x281)
[ 4409.648223] ehci_hcd :00:1d.7: restoring config space at offset 0xf (was
0x400, writing 0x40b)
[ 4409.648244] ehci_hcd :00:1d.7: restoring config space at offset 0x4 (was
0x0, writing 0xd010)
[ 4409.648256] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was
0x290, writing 0x2900102)
[ 4409.648275] ehci_hcd :00:1d.7: power state changed by ACPI to D0
[ 4409.648282] ehci_hcd :00:1d.7: power state changed by ACPI to D0
[ 4409.648342] ata_piix :00:1f.1: restoring config space at offset 0x9 (was
0x0, writing 0x5000)
[ 4409.648358] ata_piix :00:1f.1: restoring config space at offset 0x1 (was
0x285, writing 0x287)
[ 4409.648409] snd_intel8x0
