On 2011-08-02 13:56, amyekut wrote:
>
> More explanation: each of the times this problem happened was after
> several weeks of working on the computer, with the system behaving
> consistently. I normally go to suspend-to-ram or to hibernate
> (suspend-to-disc) a few times a day, and almost never rebooting.
Like me.
> So, after weeks of smooth operation, all of a sudden the computer fails
> to recover from a suspend-to-disc. I did not take a note of the error
> messages (and I have no idea how to replicate the problem, i.e. to cause
> the failure again now). I tried to boot the system a few times (in
> regular and in safe modes, always SUSE – never windows), but it always
> showed a text login screen, which however did not actually pemit me to
> login (refused).
Pity you did not record the error.
Typically when the system crashes during hibernation or thawing, you get
corrupted filesystems on all opened partitions, thus on next boot you
suffer a long fsck session on all those partitions.
If the fsck fails, you get dumped into an emergency text recovery mode,
where you are expected to repair things and end with control-D to close and
reboot.
This said, there are two people that have reported here failure to suspend
after some recent updates. You could be a third person.
It is also possible that some important files got corrupted.
> Here are the numbers: I have 2.8 GB RAM, and 2.01 GB swap space on the
> disc. Are these good sizes?
You need 3 GiB, on the same partition. Only one is used for hibernation.
> By the way, I tried to upload photos of the system data, but the forum
> program refused the upload…
We have a pastebin for that purpose.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)