If you have unsupported devices using DMA, you may have some problems. If your disk driver does not support suspend… IDE does , it may cause some problems, too. If you change kernel command line between suspend and resume, it may do something wrong. If you change your hardware while system is suspended… well, it was not good idea; but it will probably only crash.
System Sleeping States
- How to figure out how to fix hibernation? - Ask Ubuntu
I'm having a problem that previously occurred after the Creators update, which I "solved" simply by rolling back the update. Windows just updated again and I'm having the problem again. The problem is that when I hibernate, the system seems to be hibernating correctly, but then when I power it back up, it does a cold boot. It takes longer and my open programs aren't restored. I've found other threads about this on numerous fora, but none have ever offered a definitive solution. Here's one from this very same forum last year:. I have tried turning off Fast Start, but the problem still occurs.
Subscribe to RSS
Currently there are three methods of suspending available: suspend to RAM usually called just suspend , suspend to disk usually known as hibernate , and hybrid suspend sometimes aptly called suspend to both :. Using low level interfaces directly is significantly faster than using any high level interface, since running all the pre- and post-suspend hooks takes time, but hooks can properly set hardware clock, restore wireless etc. The most straightforward approach is to directly inform the in-kernel software suspend code swsusp to enter a suspended state; the exact method and state depends on the level of hardware support. See kernel documentation for details. The uswsusp 'Userspace Software Suspend' is a wrapper around the kernel's suspend-to-RAM mechanism, which performs some graphics adapter manipulations from userspace before suspending and after resuming.
Startup fails immediately and the first and only message I get is "Error: resume: No device specified for hibernation". Other cases in the forums mentioning this error cite problems with hibernation, not startup. In my case, Manjaro is completely failing to startup: no grub, no command prompt, just a dead screen with this error message. Manjaro was working great for a few months after dual-booting was using both systems , but one day got this message seemingly out of the blue. When I get this message, I can't type anything on screen and the message stays on the screen for as long as I leave it before restarting or shutting down.