Suspend to disk fails after working for several cycles (may be related to cifs?)

Hello all,

Hope this is the right place for this. I’ve been struggling with suspend to disk (hibernate if you prefer) for a while, it works after a fresh boot and for several days’ worth of overnight hibernation as I go about my work, but eventually it stops working - it gets to the splash screen but the bar only makes it a little way to the left before stopping, and then after a timeout the system just returns to the “session locked” screen - no real error messages.

I’ve done my best to try to find out what’s causing it to break but I’m really struggling, the suspend process doesn’t appear to write anything helpful to the dmesg log or the /var/log/pm-suspend.log - the only thing that I’ve seen at about the right point in time is cifsd, but I can’t be sure that it’s a problem with cifs as hibernate continues to work immediately after mounting windows shares with cifs.

Can anyone point me at a better way to debug what’s stopping suspend to disk from working?

System:
Phenom-II X3
4Gb ram
OpenSUSE 11.1
KDE 4.2
Kernel still the original 2.6.27.7-9-default

Thanks in advance for any advice!

Cheers,

Olly

How big is your swap?

Swap partition is ~4GiB, the image size being created when hibernate failed was about 1.7GiB. Don’t know how much swap was in use at that point - will check that next time it fails.

I noticed that the hibernate process prints out the swap and image sizes when it succeeds… when it fails it never gets to that point.

Thanks!

Olly

How much RAM? 2 gig maybe??

Also what ver of Suse and which Desktop

1.7 gig seems a bit large but I don’t know if Suse includes caches in the image or your usage patterns.

:slight_smile:

Does seem a bit big but I had three KDevelop sessions open, plus some firefoxen, ~10 shells, Folding@Home… not that I’m a RAM hog or anything!

ttfn,

Olly

I have about the same problem.
After a fresh start I can hybernate (to disk) only once, the second time I fall back into a password screen after a few seconds.
(this is repeatedly the same for weeks now)

However when I format the swap-partition before suspend to disk I can hibernate to disk without a problem the second time.
I cannot find any significant problem in my pm-suspend.log the main differences are

  • RET=16 (after not succeeded hibernate)
  • RET=0 (after succesful hibernating)
    don’t know what that means however.
    Suse 11.1
    I have 2 Gb mem and 5.6 Gb swap

frits

Funkster wrote:

>
> Hello all,
>
> Hope this is the right place for this. I’ve been struggling
with
> suspend to disk (hibernate if you prefer) for a while, it works
after
> a fresh boot and for several days’ worth of overnight
hibernation as I
> go about my work, but eventually it stops working - it gets to
the
> splash screen but the bar only makes it a little way to the
left
> before stopping, and then after a timeout the system just
returns to
> the “session locked” screen - no real error messages.
>
> I’ve done my best to try to find out what’s causing it to break
but
> I’m really struggling, the suspend process doesn’t appear to
write
> anything helpful to the dmesg log or the /var/log/pm-
suspend.log - the
> only thing that I’ve seen at about the right point in time is
cifsd,
> but I can’t be sure that it’s a problem with cifs as hibernate
> continues to work immediately after mounting windows shares
with cifs.
>
> Can anyone point me at a better way to debug what’s stopping
suspend
> to disk from working?
>
> System:
> Phenom-II X3
> 4Gb ram
> OpenSUSE 11.1
> KDE 4.2
> Kernel still the original 2.6.27.7-9-default
>
> Thanks in advance for any advice!
>
> Cheers,
> –
> Olly
>
>
same problem here.
Error message says not enough swap space available(something like
only 500K free iirc) and says it needs 1.4gig (or so). Of course
my swap is 2gb and before trying hibernation free shows it pretty
much empty. This is a recent problem, must be due to a kde
upgrade - am currently running from the unstable repo.


openSuse 11.2 x64bit, KDE4.4, Opera weekly

Hi all,

System has been behaving itself recently but has thrown this error up again today, and I’ve had a closer look at image sizes etc. Firstly, it doesn’t matter if I choose suspend to disk from the kpowersave menu or via pm-suspend as root, it still fails. Here’s the relevant bit of pm-suspend.log:


2010-04-28 18:12:12.640881611: done running hibernate/hibernate hooks.
+ /usr/sbin/s2disk --config /var/lib/s2disk.conf
+ RET=255
+ set +x
2010-04-28 18:12:33.366241651 +0100: running 'hibernate'/'thaw'/'reverse' hooks.

It never gets as far as snapshotting, so it doesn’t print out the image size and available swap so I checked them manually. Here’s the contents of s2disk.conf:


resume device = /dev/sda1
image size = 1748708352
# parameters taken from /etc/suspend.conf:
splash = n

and the output from free:


             total       used       free     shared    buffers     cached
Mem:       3794940    2135228    1659712          0     217424     740872
-/+ buffers/cache:    1176932    2618008
Swap:      4192956    1553300    2639656

Looks pretty safe to me!

Anyone know what RET=255 means in s2disk terms? Or at least where to look in the source code for what values it returns?

Thanks!

Olly