Bug#600846: Definitely: The problem started with kernel 2.6.32
please let upstream know the 2.6.36 trouble, so that they can work on it. On Wed, Nov 03, 2010 at 08:41:54PM +0100, hu...@online.de wrote: > 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 other datapoints would be 2.6.31-* and the first 2.6.32-[1-4]-amd64 linux packages. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103213937.gk15...@vostochny.stro.at
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. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd1bb02.7030...@online.de
