Re: Corrupted files after suspend to disk

[Andreas Hartmann <andihartmann@01019freenet.de>]

Jiri Kosina schrieb:
> On Wed, 7 Mar 2012, Andreas Hartmann wrote:
> 
>>> On my system kernel suspend *seems* to work.
>>> I've seen no corrupted files so far.
>>>
>>> But sometimes the resume is failing. (One out of 5 resumes fails).
>>> I was unable to get any kernel output.
>>>
>>> So I'm not sure whether this is the same issue
>>> or another one. :-\
>>
>> I'm pretty sure that this is the same issue. What you are telling
>> correlates with my research here.
>> I even got resumes where the machine came up again, but nothing could be
>> done (it wasn't possible to switch of the password secured screen saver
>> any more - login at the shell wasn't possible, too, because the started
>> bash crashed), 
> 
> This is happening to me as well. Something like 1 resume out of 5 goes 
> wrong this very same way. 
> 
> This is thinkpad x200s.
> 
> All the userspace is segfaulting all over the place (most frequently in 
> libselinux for some reason).
> 
> I am not able to verify the 'drop_caches' theory, as I can't invoke a 
> single command that wouldn't crash.

I'm checking after every resume for broken files (via md5sum check). If
you are lucky, only irrelevant files are damaged.

But you are right, with 3.2 (or was it 3.3?), the drop_caches theory
doesn't work at all for me (if it isn't by chance).


Regards,
Andreas