Debian Configuration :: Hibernation Fails With Invalidating Stale Software Suspend?
May 20, 2011
My hibernation was working out_off_the_box but now it has strange issue. This is debian testing with kernel 2.6.38.4 "hibarnation-disk" hibernate successfully ,with an error though ( seen from hibernate-disk -v2 --dry-run) hibernate-disk:Warning: Tuxonice binary signature file not found Anyhow , after executing the hibernation , on the next boot, the system boots from scratch and not from the resume image. During boot a message is displayed though Invalidating stale software suspend images I have done some google search but none of the solution work so far, including reinstalling the package itself.
I'm having problems with resume after suspend to RAM. The machine starts to wake up, but the screens (multi mon VGA and DVI setup) are black and the keyboard doesn't light up. After ~20 seconds there's some brief disk activity and then the computer reboots. 100% repeatable with affected kernel versions. My test method is simple, I boot the machine on the kernel's recovery option, log on as root and run "PM_DEBUG=1 pm-suspend". I haven't found anything in the logs after a failed resume.
Here's the situation: I have a SSD disk. To get TRIM support I have to use kernel 2.6.33 or later, which means that the standard kernel in Squeeze is too old.I have Nvidia graphics, and there was a change in 2.6.34 that breaks older versions of xserver-xorg-video-nouveau (version 0.0.15, used in Squeeze), I can't use Debian Squeeze with a kernel newer than 2.6.33.x.My machine (XFX GeForce 9300 motherboard) won't resume from suspend to RAM if I use a kernel newer than 2.6.36. There are no BIOS updates available.
My options: Install newer kernel from Squeeze backports (2.6.38.2 last time I tried). <--- Not doable b/c of resume problems. Upgrade to Wheezy, which uses kernel 3.0.x. <--- Not doable b/c of resume problems.Compile a vanilla kernel. So basically I'm forced to compile my own vanilla kernel, 2.6.33.x on Squeeze or 2.6.35.x on Wheezy. I won't be stuck with an unsupported kernel version in the near future, but so far I've failed miserably.
I know that the latest kernel version where everything works is 2.6.36.x (no longer maintained), 2.6.37.0 and later cause resume problems (I've tried 2.6.37, 38, 39 and 3.0.0, .0.1). I've tried doing a git bisect on the kernel, but didn't succeed, ended up on 2.6.36-rc5 which is weird considering that 2.6.36.4 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
I am running Squeeze on an older Compaq EVO laptop with radeon graphics.
A few months ago, after an upgrade, suspend and hibernate stopped working. The suspend or hibernate worked fine, but the resume just hung with a black screen. I finally got around to looking into it and found a workaround.
The workaround is to disable Kernel Mode Setting for the radeon. This can be done by adding the boot parameter "radeon.modeset=0" or by editing /etc/modprobe.d/radeon-kms.conf so that it includes the line "options radeon modeset=0".
If you are interested in the details, you can search for problem reports related to radeon kernel mode setting.
How to completely disable hibernation in Debian Squeeze (with KDE). If it's impossible to disable it for whole system, I want to hide button in KDE menu.
I have a laptop Acer Aspire 4551-2194. I've installed Debian Squeeze with XFCE and it works great. I have only one problem. I can go through hibernation / suspend, but when I push the power button, the computer hangs. It doesn't come back and I must reboot it.
ASUS P5Q Deluxe, Intel Core 2 Duo, GeForce 8800, 4GB RAM, USB keyboard and mouse never had problems with suspend and hibernation in Ubuntu. Until the latest version 10.10. Both before and after installing the proprietary Nvidia drivers, the system enters the sleep and hibernate but I can not wake up properly. Specifically, while it looks as it starts up, but not fires up the X server. Oddly - operate only CTRL + ALT + F1-12. You can switch to the text cosole, see the "incentive" to sign but other keys do not work and nothing can be entered. Not working CTRL + ALT + DEL as well, so you need to turn off the system power.
I just installed openSUSE 11.3 but cannot get hibernation (or suspend to disk) working. It does not go to hibernation but instead it just locks the screen. The relevant error in /var/log/pm-suspend.log looks like below.
According to /usr/lib/pm-utils/sleep.d/30s2disk-check '/dev/dm-1' must be the swap partition. What i don't understand is that why the error says swap partition is not active. There is no error for swap partition during boot time. Boot message says that swap partition is activated.
/usr/lib/pm-utils/sleep.d/06autofs hibernate hibernate:Shutting down automount ..done success. /usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate:INFO: checking for suspend-to-disk prerequisites... ERROR: resume partition '/dev/dm-1' not active, can not suspend
[code]...
Below is fdisk -l information for the disk which has swap partition.
/dev/dm-0p1 1 2089 16779861 82 Linux swap / Solaris Partition 1 does not start on physical sector boundary. /dev/dm-0p2 2090 3395 10482431+ 83 Linux
I am using Ubuntu 9.10 on an Acer Aspire 5050 (5052AWXMi model) and I am experiencing some problems of system Hibernation and Suspend.When I put my laptop to sleep mode (suspend) then after pressing a button system tries to open but what I get it is only a black screen.The same problem appears also when I am trying to hibernate my system. After opening my laptop again I am getting a message < waking up. Please wait > but then I get again a black screen.
Using 64Bit Ubuntu 10.04 on a VAIO VGN-FW373J. ATI Mobility Radeon HD 3650. This relates to Bug 451282. If I install the ATI 3D Drivers, the dimming problem goes away, but a host of other bugs crop up. After a resume from screen lock, suspend, or hibernation, the screen is reduced to graphical chaos. There are also hibernation errors. This bug is worse than the dimming bug, so I've uninstalled the 3d ATI drivers. If I can't find a workaround, I may have to look for a different Linux Distro or be content with Windows 7 on this particular laptop.
My suspend-to-disk and suspend-to-RAM stopped working months ago. I've grasped at straws about why ever since, but I really don't think it's a software problem, because I've reinstalled my system (MEPIS) repeatedly. What sort of hardware failures could cause this? What should I be looking for? I notice that at boot, Linux always says "no resume image found," even if I left the system in suspension or hibernation. I can post parts of the dmesg if someone tells me what to look for; I can't display the whole thing because it's too long to fit here.
For the sake of security, I want the screen to be locked after the system is resumed from suspend or hibernation. Now the only way I can do this is to check the options "Lock screen when screen saver is active." in the screensaver preference. But this method is annoying since I have to type the password to quit the screensaver. Is there other way to do this? Thanks.
Installed Debian 8.2 a while back, and I've been having issues with getting the machine to suspend correctly. If I try to put it to sleep when logged in to my regular user account the screen just goes black and then the computer hangs. However if I put it to sleep as root everything works fine. I do this by running this command (as root):
Code: Select allsystemctl suspend
What can I do about this? Worked fine on Debian wheezy..
Btw, just found this in the dmesg log. Connected perhaps..?
Code: Select all[ 6.863018] ACPI Warning: SystemIO range 0x00000000000018e0-0x00000000000018ff conflicts with OpRegion 0x00000000000018e0-0x00000000000018ef (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258) [ 6.863028] ACPI:
If an ACPI driver is available for this device, you should use it instead of the native driver
Suspend worked before I completely reinstalled Testing from scratch. Now it seems to suspend OK, but when it tries to wake up it fails. Details here: [URL]
I have installed squeeze on a HP notebook. I have one small problem though.It does not resume from suspend. If I shutdown -> suspend, or close the the lid, or shut downs (suspends) as expected, but whenower it backup up, the screen just stays black.Hibernate is working fine.
output of lspci (if needed) 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
I've been running 6.0.2 amd64 stable since release day and recently have noticed my suspend and hibernate do not work. Normally I have transmission running and have set it to not enter sleep mode while torrents are active. However today I have not had transmission and was wanting to see if the sleep mode options would kick in. So I have set my display to "sleep when inactive for" 5 mins (this works perfect) I have set "put computer to sleep when inactive for" 10 mins (this does not work at all)
When I try to manually test suspend my display flashes black for a few seconds but remains backlit, then asks me to log back in When I manually go into hibernate mode my display turns off, pops back on for a second and in a terminal says something about a usb device (something failed but it happens so fast I cannot read it)
So I have this laptop with a busted battery, I'm trying to get it into some kind of headless server, media topbox hybrid.
First thing I want to do is being able to leave it shut (powered on) in the corner without having to interact with it directly.
I've setup ssh and vnc so to login remotely and do task, transfer files and etc.
However there is a little issue with the laptop lid down upon turning it on, it immediately goes into suspend when getting to the display manager, which is 'lightdm'.
I suppose this is the default setting for Xorg and as such my custom configs for KDE only kick in after I login.
Question is: I never seen configuration for default power management stuff being done in Xorg, is there some way to disable automatic suspension on lid down?
Another question is: After the KDE kicks in does it always replace power options? I have setup a xorg.conf file specifying dpms options but these don't seem to remain.
System is a Dell E7440, with Jessie, I recently upgraded to kernel 4.2.5 due to issues with wireless that are supposed to be fixed. (The same issue exists with jessie stock kernel 3.16 and BPO tough)
When I close the lid it often does not work and I get this in dmesg
Code: Select all[ 567.104335] pci_bus 0000:01: Allocating resources [ 567.104349] pci_bus 0000:02: Allocating resources [ 567.104415] pci_bus 0000:03: Allocating resources [ 567.104428] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [ 567.105515] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [ 567.105540] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [ 567.105585] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[Code] ....
I suppose the i915 stuff is something I can ignore, However
Code: Select all[ 570.768020] acpi device:40: Cannot transition to power state D3hot for parent in (unknown)
seems to be the issue.. I don't even know what device:40 is.
in ls -l it shows as
Code: Select all lrwxrwxrwx 1 root root 0 Nov 2 12:28 device:40 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C6:00/device:40
The awkward thing is tough, software suspend by running "systemctl suspend" works perfectly and always.
Code: Select all [ 872.054627] PM: Syncing filesystems ... done. [ 872.091506] PM: Preparing system for sleep (mem) [ 872.092045] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 872.093377] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 872.094563] PM: Suspending system (mem) [ 872.094595] Suspending console(s) (use no_console_suspend to debug)
[Code] ....
So despite the mysterious issue with acpi device 40, how is real lid close different from "systemctl suspend"? And can I simply workaround the issue by making such a suspend when the lid closes?
Just curious if this is possible. What I want to do is setup a rsync job to backup my laptop to my personal file server(same LAN), but I want it do do this at 3AM while I'm sleeping. However I always close my laptop lid when I'm done using it which puts the laptop into suspend mode since that's how I configured my power options in gnome. Since I don't want to leave my laptop powered up all the time, I was wondering if it is possible to have a cron job scheduled that will wake the laptop up(out of suspend mode) and run my script/backup job, all without opening the lid of the laptop, and then put it back into suspend mode when it's done. Is this possible, and is it as easy as scheduling a cron job or is there some other scripting/configuration/trickery that I need to do to accomplish this?
Also, my laptop's BIOS has the option to power on at a scheduled time if needed, but I'm not sure if that would work with it being suspended(hibernation is not an option since my entire HD is encrypted with LUKS and I would have to be present to enter the password to boot the system.).
I have just joined the Debian community, for the past 2 years I have been using Linux Mint (ubuntu), I am now using Linux Mint Debian 64. I have a Lenovo A700 ideacentre with a Broadcom 4313 WiFi card. I manage to get the card working, now I have a new problem. If I suspend the machine the WiFi will not connect on resume. Is there a simple command I can use to getting the connection restarted, or better yet a work around so it will restart on its own?
I've tried editing .xinitrc to contain ck-launch-session and dbus-launch to no avail. Console kit is installed. I'm using Sid without a login manager, and xfce's suspend and hibernate work fine on my Wheezy computer. Xfce4-session and consolekit are installed. Is this a problem with permissions?
I have installed the latest virtualbox 4.1 on my desktop and laptop. It hosed suspend and hibernate.
The laptop is A Dell D630 with Intel Core2 Duo CPU, the desktop is an AMD based ASUS M3N78-VM mobo with Athlon II x2 250 CPU. Debian Testing 32-bit (same results with the 2.6.39 and the 3.0 kernels). Both have nvidia cards though - the desktop an integrated 8200, the laptop a NVS 135M. But suspend/hibernate was working before with the 4.0 series virtualbox.
The workaround is to clear the vboxpci vboxnetadp vboxnetflt vboxdrv modules from the memory before suspend/hibernate. I added the
service vboxdrv stop rmmod vboxpci vboxnetadp vboxnetflt vboxdrv
lines to my sleep script (i dont use power managers, just the acpi powerbutton/lid scripts modified). Everything is ok now.
My system is hanging on screen suspension... And its not the usual hang on "sleep" or others similars, it will happen by only having the screen on stand-by ( eg xset +dpms)...
If I leave for a while the screen will shutdown as expected but computer will completely hang after an indefinite time, it will not respond to outside connections and the will be spinning faster than usual...
Only workaround is to have the screen power save option disabled, in my case, on the KDE settings...
I have tried the most common solution to have "nomodeset" as a kernel option to disable mode setting, but this doesn't seem to work...
Also tried to forcebly reproduce the issue with Code: Select allxset force dpms standby/suspend/off but nothing happens like that...
This issue also only appears with the fglrx driver, open-source works well.
I'm trying to lower consumption of my server/HTPC. After wakeup from pm-suspend server/HTPC is ready to use in 1 or 2 seconds .For example if I suspend it while watching movie in KODI, after resume movie starts playing instantly. But some services (SSH and SAMBA) are not running. I thought it was network problem so I change configuration to static (not DHCP). SAMBA and SSH starts like 15 seconds after wakeup.
I have Debian Squeeze x64 on ThinkPad T61p with standard 2.6.32-5-amd64 kernel. thinkpad_acpi loaded as module, suspend to RAM works fine from menu in KDE as well as by closing the lid, however machine doesn't appear to react on pressing Fn+F4 which should put it to sleep as well. I've read through thinkpad_acpi documentation and asked Google but so far can't find the solution. Can anyone, point me in correct direction?
Lately I upraded my Debian using aptitude update/aptitude upgrade - including installing a new kernel (3.0). Since this upgrade I have strange problem with networking. When I suspend my computer and resume it, I do not have connectivity with network:
$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
I have 12Gb of ram, a 24Gb swap partition (which appears active in the system monitor). When trying to hibernate, the screen turns off for 5 seconds, then immediately awakens and brings me to the login screen.
Here is my /var/log/pm-suspend.log :
Code: Initial commandline parameters: Sun Jun 13 11:28:30 PDT 2010: Running hooks for hibernate. /usr/lib/pm-utils/sleep.d/000kernel-change hibernate hibernate:success. /usr/lib/pm-utils/sleep.d/00logging hibernate hibernate:Linux ubuntu-beast 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux code....
I decided to upgrade my Asus Eee 900 from Lenny to Squeeze, to fix some issues that I was having. I did a fresh install using the beta1 netinstall cd image, and now my system is mostly working as I'd like it. Overall it seems quite good, and it even boots much faster than it did with Lenny.
I've encountered a problem, though. The suspend key doesn't work. I installed the package 'hibernate', and now the system can suspend via a command (which seems to work properly, although I haven't tested it extensively). I've noticed that the squeeze system doesn't have a command that my other Lenny systems do, 's2ram'. And I've noticed also that a package, uswsusp, which seems to be related to this kind of thing, can't be installed because it's not in the repositories: Package uswsusp is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'uswsusp' has no installation candidate
