5 ms·
I dislike the forced disablement of hibernation. That should have been something you could opt out of with a kernel command line parameter.
by josephcsible 5y ago
I dislike the forced disablement of hibernation. That should have been something you could opt out of with a kernel command line parameter.
- nitinreddy88 5y agoHonestly hibernation never worked out perfectly in Linux. I have desktops to laptops running with different hardware, every once in a while the hibernation goes for toss and need to reboot
- juancampa 5y agoWorks fine for me. I believe the only time I've seen issues is when I upgrade the kernel, forget to restart, and then hibernate the old (running) kernel. But it just ignores the image and boots like normal
- juancampa 5y agoWorks fine for me. I believe the only time I've seen issues is when I upgrade the kernel, forget to restart, and then hibernate the old (running) kernel. But then it just ignores the image and boots like normal
- dgan 5y agoi had hibernation problem with one specific network card,i guess atheros,it would make the whole system hang
- Galanwe 5y agoI don't think it's really annoying in practice. First, most Linux servers don't care about hibernation, so the issue really just happens for desktops/laptops. Second, there are at least 3 or 4 suspend states that Linux can offer, hibernation happens to be the most efficient one, but downgrading to a slightly less power efficient suspend state that keeps power in the RAM shouldn't make that much difference. See https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/pm/sleep-states.html https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/pm/sle... for more information.
- R0b0t1 5y agoBack when I checked it's a massive, multi-hour difference.
- chrismorgan 5y ago“Shouldn’t make that much difference?” It utterly kills various perfectly reasonable use-cases. Here are a few that I’ve personally experienced and seen others experience: 1. Laptop that can sleep for a week or ten days, and you’re going on holiday for a fortnight and leaving your laptop behind, and don’t want to leave it plugged in unattended (fire hazard) but don’t want to lose your session. 2. You’re off-grid for days on end (e.g. cycling tour with mostly tent camping, which I’ve done several times), and want to be able to use your laptop occasionally without its battery having been drained by being asleep instead of off, and want to keep using the same session. 3. You’re using a device with no battery (desktop computer or laptop with dud battery so that it dies as soon as you unplug it), but you need to move it from point A to point B without losing your session. These are all straightforward examples where hibernate is essential.
- josefx 5y agoOn the one hand hibernate could just zero out the secret memory instead of storing it, which would be trivial to detect by an application by checking if guard values were set to zero. On the other hand using hibernate significantly increases the risk of leaking parts of the secret that might temporarily end up on the stack or other less protected memory regions. So the tradeoff in program complexity might not be worth it, of course at that point you could still disable hibernate system wide.
- ddalex 5y ago> just zero out the secret memory Or pipe in /dev/urandom for that matter
- user-the-name 5y ago> which would be trivial to detect by an application by checking if guard values were set to zero. if(data->guard != 0) { // Hibernation happens here. process(&data); }
- josefx 5y agoYou would have to check the guard after process and throw away the result if guard changed. Edit: I think something similar is used to avoid time related system calls, the values are just mapped into the application address space and the kernel updates time and guard values concurrent to the application.