Bugzilla Bug 197630

cat: /sys/power/tuxonice/: Is a directory
ABORTING: /sys/power/tuxonice/ did not return a valid result.
hibernate: Aborting.

I'm using the fileallocator, I remember a similar problem with the 1.96
version.. but I'm not sure about this.

Please paste the output of hibernate runs with --verbosity=4
Thanks.

Created an attachment (id=134805) [edit]
hibernate-script-1.97-suspend2.patch

Please try this patch.

Created an attachment (id=134812) [edit]
hibernate verb=4, patched suspend2

Using your patch the hibernate script dies with:

You haven't specified a resume=/resume2= parameter on your kernel command line

Your GRUB or LILO config should have something like resume=swap:/dev/hdaX
where /dev/hdaX is your swap partition. You will then need to either reboot
after doing so or set it manually (this time only) using:
    echo swap:/dev/hdaX > /sys/power/tuxonice/resume
hibernate: Aborting.

This is wrong because I'm using firewriter and my cmdline is correct

Created an attachment (id=134813) [edit]
hibernate verb=4, original (1.97) suspend2

This is the output of "hibernate --verbosity=4" using the original suspend2
file shipped with the 1.97 version

Created an attachment (id=134937) [edit]
suspend2.patch

This is a simple patch as suggested by Pat Double on the suspend2-users
mailing-list.

Using this patch the problem disappears but I receive:

# hibernate
/bin/echo: write error: Device or resource busy

Created an attachment (id=134938) [edit]
debug-busy

These are the debug messages with the previously attached patch

Oops my bad! The patch doesn't solve the problem :( 

I forgot I added "VerifyFilewriterResume2 no" to my suspend2.conf for
testing (it seems to skip the problem "is a directory" but hibernate script
still not work).

You are trying to use sysfs and not suspend2 (DoSysfsPowerStateSuspend).
Please disable suspend emulation in suspend2 kernel configuration.

(In reply to comment #8)
> You are trying to use sysfs and not suspend2 (DoSysfsPowerStateSuspend).
> Please disable suspend emulation in suspend2 kernel configuration.

What do you mean? I tried to disable "Suspend to RAM and standby" and "Replace
swsusp by default" but same "is directory" issue here.

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_UP_POSSIBLE=y
# CONFIG_SUSPEND is not set
CONFIG_HIBERNATION_UP_POSSIBLE=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_TOI_CORE=y

#
# Image Storage (you need at least one allocator)
#
CONFIG_TOI_FILE=y
# CONFIG_TOI_SWAP is not set

#
# General Options
#
CONFIG_TOI_CRYPTO=y
CONFIG_TOI_USERUI=y
CONFIG_TOI_USERUI_DEFAULT_PATH="/sbin/tuxoniceui_fbsplash"
# CONFIG_TOI_KEEP_IMAGE is not set
# CONFIG_TOI_REPLACE_SWSUSP is not set
CONFIG_TOI_CHECKSUM=y
CONFIG_TOI_DEFAULT_WAIT=25

Can you please apply my patch again? (attachment#134805 [edit])

1. Paste the output of:
cat /sys/power/tuxonice/resume

2. Execute:
hibernate --config-file=/etc/hibernate/suspend2.conf --verbosity=4

Thanks.

I re-emerged hibernate-script and applied your patch.

The /sys/power/tuxonice/resume was empty so I tried to use resume= instead of
resume2= in my cmdline and now the suspend process seems to work (it seems I
need to add --config-file=/etc/hibernate/suspend2.conf otherwise hibernate
script dies with the "/bin/echo: write error: Device or resource busy" error)
but the resume process *doesn't start* (the system boots normally) and there
isn't any suspend/tuxonice message in dmesg.

I've just emerged sys-kernel/genkernel-3.4.9_pre6 and used it to build both
kernel and initrd image.

See bug#197244 for genkernel patch.

After you have working system, we determine why it was not detected
automatically.

Ok using both your patch (suspend2 and genkernel) now I am able to suspend and
resume my laptop using tuxonice ;) Many thanks!

I reported the hibernate script bug upstream too and a patch slightly different
from your was submitted, please take a look here
http://bugzilla.tuxonice.net/show_bug.cgi?id=339

Now I'd like to know why the hibernate script doesn't recognize my shining
tuxonice capable system :)

# cat /etc/hibernate/hibernate.conf 
TryMethod suspend2.conf
TryMethod disk.conf
TryMethod ram.conf

Please paste a new debug log, with suspend2.conf and without.

Created an attachment (id=135085) [edit]
debug-with -F/etc/hibernate/suspend2.conf

Created an attachment (id=135087) [edit]
debug-without

This time it worked without the -F/etc/hibernate/suspend2.conf too

So, can we close this bug?
Or you can reproduce a none working scenario?

I think so. I will eventually reopen this bug if I'll find a new non-working
scenario.