Bug#600846: Definitely: The problem started with kernel 2.6.32
I downloaded three versions of the 2.6.30 kernel from snapshot.debian.org
and installed them on my notebook - without doing any other changes to
the system.
And the Suspend-To-RAM of all of the three 2.6.30 kernels worked
perfectly well !
So from my point of view the problem started definitely with the 2.6.32
kernel version.
The 2.6.30 kernel packages were:
linux-image-2.6.30-1-amd64_2.6.30-1_amd64.deb
linux-image-2.6.30-2-amd64_2.6.30-7_amd64.deb
linux-image-2.6.30-2-amd64_2.6.30-8squeeze1_amd64.deb (the latest I found)
With the 2.6.30 kernel there is the same effect of additional processes
coming up
after the first Suspend-To-RAM . These are:
> root 3092 2 0 20:22 ? 00:00:00 [migration/1]
> root 3093 2 0 20:22 ? 00:00:00 [ksoftirqd/1]
> root 3094 2 0 20:22 ? 00:00:00 [watchdog/1]
> root 3095 2 0 20:22 ? 00:00:00 [kconservative/1]
> root 3096 2 0 20:22 ? 00:00:00 [ata/1]
> root 3097 2 0 20:22 ? 00:00:00 [crypto/1]
> root 3098 2 0 20:22 ? 00:00:00 [aio/1]
> root 3099 2 0 20:22 ? 00:00:00 [kondemand/1]
> root 3100 2 0 20:22 ? 00:00:00 [kblockd/1]
> root 3101 2 0 20:22 ? 00:00:00 [kintegrityd/1]
> root 3102 2 0 20:22 ? 00:00:00 [events/1]
> root 3103 718 0 20:22 ? 00:00:00 udevd --daemon
> root 3104 718 0 20:22 ? 00:00:00 udevd --daemon
As can be seen the 2 processes
> root 3109 2 0 11:40 ? 00:00:00 [radeon/1]
> root 3110 2 0 11:40 ? 00:00:00 [ext4-dio-unwrit]
coming up in kernel 2.6.32 are missing.
Reply to: