Bug#600846: Suspend-To-RAM not works for some months, Suspend-To-Disk not works since last update

[Jonathan Nieder <jrnieder@gmail.com>]

hubba@online.de wrote:

> So the problem module should be one of the remaining 60 modules attached as
> "lsmod21.txt" .
> But now I do not know how to unload them cause I always get the message
> "module is in use" - even when system is started in recovery mode.
> Especially the "radeon" module which might be a good candidate cannot be
> unloaded.
> Could you please give me some instructions how to do this?

The radeon module seems like a good place to start.

I would suggest trying hibernation from the minimal recovery shell provided
by the initramfs, as described in the initramfs-tools(8) manpage.  It works
roughly like this:

	1. Pass "break=modules" on the kernel command line.
	2. From the initramfs shell, load enough modules to have a usable
	   swap partition (that means "modprobe sata_sil" and "modprobe
	   sd_mod", at least.  Enable swap with swapon -a.
	3. Load whatever set of modules you want to try (i.e., none, for the
	   first try).
	4. Hibernate (twice, I guess?).

Let me know if you have any questions.

> What I would like to mention again (as earlier in bugzilla) is the strange
> behaviour that the first suspend to ram always works perfectly fine and the
> second one always causes a system hangup

Yes, that is weird but definitely believable.  Does suspend to disk behave
the same way?

Thanks, these test results are great.  Looking forward to learning the
culprit.

Regards,
Jonathan