https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|12.1 suspending computer |12.1(encrypted lvm / & |pm-hibernate : resuming is |swap) suspending computer |new boot, not using the |pm-hibernate : resuming is |suspended image |new boot, not using the | |suspended image -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c1 Richard Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |RBrownCCB@opensuse.org --- Comment #1 from Richard Brown 2011-11-07 16:22:18 UTC --- I am not able to reproduce this as reported but I have noticed the following interesting behaviour (on my Lenovo X220, Intel graphics, i7 CPU, etc) Setup has encrypted LVM with / and swap in the LVM group. Hibernating from tty with pm-hibernate HIBERNATE seems to fire up splashy and hangs, machine never hibernates Removing splashy also removes the branding and suspend packages pm-hibernate HIBERNATE then works, but resume fails, hanging at 'Restarting tasks... done' However, Hibernating from GNOME, using the GNOME Hibernate menu option works perfectly, every time.... There's something weird going on here but from my tests it seems to suggest a problem with how pm-hibernate is doing its thing, not hibernate in general. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c3 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bruno@ioda-net.ch --- Comment #3 from Ludwig Nussel 2011-11-08 17:23:32 CET --- suspend package not installed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c4 --- Comment #4 from Bruno Friedmann 2011-11-08 22:03:47 UTC --- Ludwig exactly, it was removed when I decide to remove splashy (due to crash) as splashy if installed bug and get the system unable to suspend. So now I've locked uninstall splashy and push suspend zypper --no-refresh in suspend Loading repository data... Reading installed packages... Resolving package dependencies... Problem: suspend-1.0-11.1.x86_64 requires libsplashy.so.1()(64bit), but this requirement cannot be provided uninstallable providers: splashy-0.3.13-30.2.x86_64[factory-oss] Solution 1: do not forbid installation of splashy-0.3.13-30.2.x86_64[factory-oss] Solution 2: do not install suspend-1.0-11.1.x86_64 Solution 3: break suspend by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): 3 Resolving dependencies... Resolving package dependencies... The following NEW package is going to be installed: suspend 1 new package to install. Overall download size: 91.0 KiB. After the operation, additional 395.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving package suspend-1.0-11.1.x86_64 (1/1), 91.0 KiB (395.0 KiB unpacked) Retrieving: suspend-1.0-11.1.x86_64.rpm [done] Installing: suspend-1.0-11.1 [done] Additional rpm output: Recreating all initial ramdiscs. This could take a while. (Touch /var/lib/no_initrd_recreation_by_suspend to prevent.) Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-3.1.0-1-desktop Initrd image: /boot/initrd-3.1.0-1-desktop Root device: /dev/vgsys/lvsuse (mounted on / as ext4) Resume device: /dev/vgsys/lvswap enabling LUKS support for /dev/md1 (cr_md1) modprobe: Module kernel not found. WARNING: no dependencies for kernel module 'kernel' found. Kernel Modules: thermal_sys thermal processor fan dm-mod dm-crypt dm-snapshot raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 linear arc4 ecb sha256_generic cbc Features: acpi dm block usb md lvm2 luks resume.userspace resume.kernel Bootsplash: hardDrive (1920x1080), hardDrive (800x600) Kernel image: /boot/vmlinuz-3.1.0-rc9-1-desktop Initrd image: /boot/initrd-3.1.0-rc9-1-desktop Root device: /dev/vgsys/lvsuse (mounted on / as ext4) Resume device: /dev/vgsys/lvswap enabling LUKS support for /dev/md1 (cr_md1) modprobe: Module kernel not found. WARNING: no dependencies for kernel module 'kernel' found. Kernel Modules: thermal_sys thermal processor fan dm-mod dm-crypt dm-snapshot raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 linear arc4 ecb sha256_generic cbc Features: acpi dm block usb md lvm2 luks resume.userspace resume.kernel Bootsplash: hardDrive (1920x1080), hardDrive (800x600) I will retry tomorrow morning if that works. Then change the needinfo flag -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c6 --- Comment #6 from Bruno Friedmann 2011-11-09 08:34:54 UTC --- okay forget : even if powersave -U work (run as root) doing a pm-hibernate HIBERNATE crash cat /var/log/pm-suspend.log redirecting to systemctl /etc/pm/sleep.d/99at hibernate hibernate: success. Running hook /usr/lib/pm-utils/sleep.d/99info hibernate hibernate: /usr/lib/pm-utils/sleep.d/99info hibernate hibernate: success. Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate: /usr/lib/pm-utils/sleep.d/99video hibernate hibernate: success. Wed Nov 9 09:26:35 CET 2011: performing hibernate INFO: using built-in quirks database from HAL. INFO: S2RAM_OPTS from HAL quirks: ' '. Now I've rebooted, and the swap is normally mounted ... (becoming crazy :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c8 Michal Vyskocil changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mvyskocil@suse.com |hmacht@suse.com --- Comment #8 from Michal Vyskocil 2011-11-11 12:48:06 UTC --- pm-utils is not guilty as there was no big change in pm-utils between 11.4 and Factory (only small unrelated fix in /usr/bin/powersave). It uses suspend package to perform the actions with a fallback to kernel, so one of those methods caused a regression. In openSUSE is pm-utils configured to use s2ram/s2disk/s2both first and as I see a big version update (0.8->1.0) + changes in patches there I suspect it. See /usr/lib/pm-utils/module.d/uswsusp for details how it's called from pm-utils. If those binaries are not available, then kernel methods are used as a fallback (there's tuxonice module, but not usable with standard SUSE kernels). In case of kernel mode, the following code (see /usr/lib/pm-utils/pm-functions for details) is executed 307 if [ -z "$HIBERNATE_MODULE" ] && \ 308 [ -f /sys/power/disk ] && \ 309 grep -q disk /sys/power/state; then 310 HIBERNATE_MODULE="kernel" 311 do_hibernate() 312 { 313 [ -n "${HIBERNATE_MODE}" ] && \ 314 grep -qw "${HIBERNATE_MODE}" /sys/power/disk && \ 315 echo -n "${HIBERNATE_MODE}" > /sys/power/disk 316 echo -n "disk" > /sys/power/state 317 } 318 fi HIBERNATE_MODE is "shutdown" by default Not sure what about Gnome - don't it use upower for it? In this case /usr/bin/powersave might work as well, because it calls upower via D-BUS API. What might be useful for suspend maintainer * what's in /etc/suspend.conf and in /var/lib/s2dick.conf? * is there anything special in /etc/pm/config.d? * if you changed /usr/lib/pm-utils/defaults, please show it as well * run the s2disk and/or kernel mode from command line and report the results -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c10 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com --- Comment #10 from Bruno Friedmann 2011-11-13 11:00:11 UTC --- Okay after running 30 times the suspend/resume process on two different laptop here where I am. Good news the 2 laptops react exactly the same : powersave -U work pm-hibernate fail if splash=y in active. You get the splashy suspend screen and then nothing more. Hitting the poweroff button create the powerdown button and then systemd try to poweroff the computer, there's a loop at that time, and a lot of message are created on console about some /proc/ readonly ... The computer poweroff, and when you restart it, it try to resume and failed with fsck (sometimes 2/5 with warning about last date time write on fs are in future). This is the same even if you change the theme for another than openSUSE splashy_config --set-theme default for example. But note also the splashy error -10 at startup and suspend time. if you comment splash=n and then issue pm-hibernate the process goes smoothly. At wake-up the grub pick correctly the action, (in my case, the passphrase to unlock crypted lvm or raid is shown, and work) and the system state is correctly restored. To notice, even with splash=n in config, at wake up splashy analyse the commandline and try to start splashy image theme which appear during 1 seconde then it replaced by the normal bootsplash theme. My conviction is that we should get rid off splashy & bootsplash in the next run for 12.2 to avoid those kind of wrong interaction. ps : I add fcrozat in CC just for information about the interaction with systemd. (not sure there's something to change directly in systemd, but the "war" between splashy and bootsplash should be fixed or unified if we don't change for another system (plymouth?) About the -10error https://bugzilla.novell.com/show_bug.cgi?id=664793 https://bugzilla.novell.com/show_bug.cgi?id=715967 About wrong branding https://bugzilla.novell.com/show_bug.cgi?id=730050 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c12 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bruno@ioda-net.ch | --- Comment #12 from Bruno Friedmann 2011-11-16 19:13:31 UTC --- Hoger I just remade a test. powersave -U with or without splashy finish correctly the shutdown process. and you get a safe boot wake up after. The only things that happen is if you have splashy=y then you saw during 1/10sec the splashy image, and next to that the splashy_start... error=-10 and you saw the suspend process in console storing ram image on disk. If you know which log or part of log you need, I will attach them here -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c14 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bruno@ioda-net.ch | --- Comment #14 from Bruno Friedmann 2011-11-19 20:38:55 UTC --- s2disk /dev/vg0/lvswap with splashy=y in /etc/suspend.conf = failure the theme image is shown but nothing happen (I stop the computer with power button to initiate a full powerdown) with splashy = n s2diks just work like a charm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728656 https://bugzilla.novell.com/show_bug.cgi?id=728656#c17 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #17 from Bruno Friedmann 2012-01-22 19:32:10 UTC --- And forget to change the status :D -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.