ususpend (s2disk) issues

saciel · 2007-12-31 00:26:39

I just switched from the old suspend2 stuff to the userspace suspend method described in the wiki. I use a custum kernel which I published on the AUR anyway, but I feel that it might be easier to maintain without the suspend2/tuxonice patching.

Yet, there are some issues I woner about. Is there any chance to stop ususpend from beeping on suspending and resuming?

When I used suspend2 there was a kernel boot parameter "noresume2" which prevented booting from resuming but invalidated the last suspension-image instead. Is there a way to do something like that with ususpend, too?

What will happen if some of my filesystems might have changed and I resume anyways? Suspend2 always warned that might severely damge the filesystems.

patroclo7 · 2007-12-31 11:02:25

Actually, s2disk does not beep here: may be some process you stop in the hibernate routine is beeping?

For the other two issues, I suggest to ask in the suspend-devel mailing list. I guess that the hibernate-cleanup service included in the hibernate-script package could be used also with ususpend, since it merely cleanup the swap partition, a simple action which should be independent of the hibernation method used.

Finally, just to be fair with people working on it, suspend2/tuxonice is not old at all, but still actively developed.

saciel · 2008-01-02 03:09:57

Don't get my wrong. By no means did I mean that suspen2/tuxonice is old-fashioned or outdated. For me it is some sort of the "old things" I have been using for quite while before trying uswsusp which seems to be newer. That's it.

It beeps twice when it is "Snapshotting the system", once at the beginning and once at the end. And than it beeps a last time which is partially muted by the computer turning off during the beep. It beeps again after resuming is performed.

Is cleanup really part of the hibernate-script package? I thought it was coming along with suspend2. Do you know how I could - if necessary - at least manually clear up the swapspace?

Then I have another problem which I noticed a while ago (when I was still using the not-so-old supsend2). I can't actually say when it first popped up but I can tell that it once was working fine. Changing to uswsusp seemes to have no effect on the issue. Unmounting the devices as I order it in /etc/hibernate/common.conf doesn't seem to work. I want all my external devices unmounted as it is unclear if they will be available or if they are disconnected next time. I mount one of the devices for example /dev/sdb1 then hibernate. After resuming I cannot access it anymore and all sdb devices are now sdc devices. It's just like if I was mounting it, then pulling the usb cable without unmounting and plugging it back. That has the same effect. Any idea on what to do there?h

patroclo7 · 2008-01-03 23:04:03

About the first problem with beeps, I think that you should report this to the suspend-devel mailing list.

About the hibernate-cleanup, it is part of the hibernate script. 'pacman -Q /etc/rc.d/hibernate-cleanup' can confirm this. However, it looks for a specific tuxonice signature and cleans swap only in the case it does not find it. I would say that if you run it your swap partition is always cleaned. But since it is run only if you are not resuming, then may be this is just what you want. Anyway you can just read it (it is a simple script) to see what it does (basically he swapoff the hibernate device, he remakes swap with mkswap, and it reactivates the swap with swapon).

The third problem seems to me not related to umounting, but to devices and then to udev. In fact the devices could be unmounted but the devices (the files in /dev) could be still there, so that after resuming new devices are created. I do not know if this could/should be fixed at the level of the hibernate-script or at a deeper level. I suggest to ask this on suspend-devel or suspend2-devel.

saciel · 2008-01-05 04:59:23

I don't think that it is some udev issue, because if I unmount them manually I do not get the new device files. As I said, it's just like pulling and replugging the cable. If something is mounted then there is trouble. If nothing is mounted, everything is fine.

Arch Linux

#1 2007-12-31 00:26:39

ususpend (s2disk) issues

#2 2007-12-31 11:02:25

Re: ususpend (s2disk) issues

#3 2008-01-02 03:09:57

Re: ususpend (s2disk) issues

#4 2008-01-03 23:04:03

Re: ususpend (s2disk) issues

#5 2008-01-05 04:59:23

Re: ususpend (s2disk) issues

Board footer