4 ms·

I’ve killed a laptop by placing it in a backpack which failed to suspend. Based on the heat I assume parts of it cooked despite any thermal throttling. It’ll be

I’ve killed a laptop by placing it in a backpack which failed to suspend. Based on the heat I assume parts of it cooked despite any thermal throttling. It’ll be interesting to see the damage a bug like this might cause.

Szpadel 9mo ago
I had identical scenario that killed ssd drive. since then I always place laptop with vents on the top
Droobfest 9mo ago
I did too, it ran Linux.
- Joel_Mckay 9mo ago
  "suspend" was always fragile, and "hibernation" a liability at times. Close the lid button to shutdown... should be default behavior, as ssd/NVMe can boot a system so fast now it no longer makes sense to risk some fussy software glitching on resume. =3
  - fpoling 9mo ago
    With Debian 13 on ThinkPad X1 the hibernation is very reliable. Resuming from it while not instant still takes like 40 seconds. So I configured my laptop on lid close to sleep for 15 minutes and then hibernate. This way if I just to another room the wake-up is instant while longer pauses shuts the laptop down removing any security keys from the memory.
hugh-avherald 9mo ago
https://xkcd.com/1172/ https://xkcd.com/1172/
Tade0 9mo ago
Classic. My last Windows laptop cooked its screen like that. Meanwhile my work Windows laptop would just go full throttle during "sleep".
da_chicken 9mo ago
I've had a laptop in a bag that decided it should wake from modern standby to run updates. Except the update failed at the laptop froze during boot. It didn't kill the laptop fortunately. Then two months later, it did it again. And again three months after that. Sorry, Microsoft, you've lost your S3 privileges. I changed it to S0. Just because you're connected to a WiFi network you know doesn't mean you can turn on and do whatever you want.
- Macha 9mo ago
  This was a constant problem with late Intel Macs where I was working at the time, to the point that people started explicitly using shut down enough to the point that security complained it was slowing down their patch rollouts. Had some slack discussions with security about how their need for a green metric on patch deployment time doesn't entitle them to introduce a fire hazard to my personal residence...
  - da_chicken 9mo ago
    Yeah, the problem is that on Windows 10/11, if you have modern standby enabled and have fast boot enabled, then shutdown puts the system into standby.
    - vladvasiliu 9mo ago
      Do you have more info on this? It’s not at all the behavior I observe. After I shut down windows, which I do basically every time I use it since I usually use Linux on that machine, it is completely off. Turning the pc on boots Linux (it’s first in the boot order). It has modern standby and most of its other defaults, which I know because if it goes to sleep it doesn’t: the fan stays on and it never gets cold to the touch despite the blinking power led. The other day it randomly installed the windows update and rebooted because I found it waiting for the LUKS pin.
      - Telaneo 9mo ago
        Look up 'Fast Startup'. It's a thing since Windows 8. It's a curse onto humanity.

Szpadel 9mo ago

I had identical scenario that killed ssd drive. since then I always place laptop with vents on the top

Droobfest 9mo ago

I did too, it ran Linux.

Joel_Mckay 9mo ago
"suspend" was always fragile, and "hibernation" a liability at times. Close the lid button to shutdown... should be default behavior, as ssd/NVMe can boot a system so fast now it no longer makes sense to risk some fussy software glitching on resume. =3
- fpoling 9mo ago
  With Debian 13 on ThinkPad X1 the hibernation is very reliable. Resuming from it while not instant still takes like 40 seconds. So I configured my laptop on lid close to sleep for 15 minutes and then hibernate. This way if I just to another room the wake-up is instant while longer pauses shuts the laptop down removing any security keys from the memory.

hugh-avherald 9mo ago

https://xkcd.com/1172/ https://xkcd.com/1172/

Tade0 9mo ago

Classic. My last Windows laptop cooked its screen like that. Meanwhile my work Windows laptop would just go full throttle during "sleep".

da_chicken 9mo ago

I've had a laptop in a bag that decided it should wake from modern standby to run updates. Except the update failed at the laptop froze during boot. It didn't kill the laptop fortunately. Then two months later, it did it again. And again three months after that. Sorry, Microsoft, you've lost your S3 privileges. I changed it to S0. Just because you're connected to a WiFi network you know doesn't mean you can turn on and do whatever you want.

Macha 9mo ago
This was a constant problem with late Intel Macs where I was working at the time, to the point that people started explicitly using shut down enough to the point that security complained it was slowing down their patch rollouts. Had some slack discussions with security about how their need for a green metric on patch deployment time doesn't entitle them to introduce a fire hazard to my personal residence...
- da_chicken 9mo ago
  Yeah, the problem is that on Windows 10/11, if you have modern standby enabled and have fast boot enabled, then shutdown puts the system into standby.
  - vladvasiliu 9mo ago
    Do you have more info on this? It’s not at all the behavior I observe. After I shut down windows, which I do basically every time I use it since I usually use Linux on that machine, it is completely off. Turning the pc on boots Linux (it’s first in the boot order). It has modern standby and most of its other defaults, which I know because if it goes to sleep it doesn’t: the fan stays on and it never gets cold to the touch despite the blinking power led. The other day it randomly installed the windows update and rebooted because I found it waiting for the LUKS pin.
    - Telaneo 9mo ago
      Look up 'Fast Startup'. It's a thing since Windows 8. It's a curse onto humanity.