Hacker News new | ask | show | jobs
by washadjeffmad 488 days ago
This space is problematic enough that you could reliably segfault 2017-2019 Intel MacBooks by closing the lid before unplugging HID peripherals, preventing suspend (and cooking it in your bag on the commute home).

It also plagues Windows on custom PC builds, even when there are vendor drivers. Not every component plays nicely with suspend states, ASPM, C-sates, load line calibration, etc. And while often the capability exists natively to address issues (in BIOS, Linux, etc), how many people know how to start looking?
2 comments
janderson215 488 days ago
Hmm I thought that was a feature, not a bug. I used to leave everything plugged and close the lid if I wanted big downloads to keep going or wanted an even quicker start up.
link
c-hendricks 488 days ago
The computer staying awake when there's a monitor / keyboard/ other HID connected is one thing

The computer locking up when said devices are removed and not properly going to sleep then is a different (much worse) issue

link
burnte 488 days ago
My custom-build desktop had an issue with the previous AM4 motherboard I had where if you told Windows to hibernate, the entire machine would shut down as normal, but then a few seconds later it'd wake back up by itself and unhibernate. I had to turn off the PSU power switch during those few moments to keep it in hibernate mode. New mobo and that's gone now. BIOS updates never helped. Really odd.
link
iamtedd 488 days ago
Probably no help to you now, but if someone has a Windows machine that keeps waking up by itself, you can see what triggered the wake by running

    powercfg /lastwake
in a command window as admin.
link
burnte 487 days ago
True, and that helps if it won't go to sleep. This was some weird bug in either the board or the bios.
link