Bug#600846: Problem also with linux-image-2.6.36-trunk-amd64, but another interesting detection

["hubba@online.de" <hubba@online.de>]

As expected, the problem also exists with linux-image-2.6.36-trunk-amd64 .

But before putting something into bugzilla I'd like to tell you about 
another
interesting detection I made now during testing:

For 6 times in follow the system showed the following absolute constant 
behavior:

After booting, the first Suspend-To-RAM allways worked very fine and the
second Suspend-To-RAM allways constantly hung.

And after the first Suspend-To-RAM there existed some additional 
processes in
the process list that did not exist after booting:

> root      3105     2  0 11:40 ?        00:00:00 [migration/1]
> root      3106     2  0 11:40 ?        00:00:00 [ksoftirqd/1]
> root      3107     2  0 11:40 ?        00:00:00 [watchdog/1]
> root      3108     2  0 11:40 ?        00:00:00 [kconservative/1]
> root      3109     2  0 11:40 ?        00:00:00 [radeon/1]
> root      3110     2  0 11:40 ?        00:00:00 [ext4-dio-unwrit]
> root      3111     2  0 11:40 ?        00:00:00 [ata/1]
> root      3112     2  0 11:40 ?        00:00:00 [crypto/1]
> root      3113     2  0 11:40 ?        00:00:00 [aio/1]
> root      3114     2  0 11:40 ?        00:00:00 [kondemand/1]
> root      3115     2  0 11:40 ?        00:00:00 [kblockd/1]
> root      3116     2  0 11:40 ?        00:00:00 [kintegrityd/1]
> root      3117     2  0 11:40 ?        00:00:00 [events/1]
> root      3119   500  0 11:40 ?        00:00:00 udevd --daemon
> root      3120   500  0 11:40 ?        00:00:00 udevd --daemon

For me it now looks like one (or some) of them might cause the problem.