> FWIW, I just tried shutting the lid on this netbook, to see what would happen. > > Disks went quiet quickly enough to assume it was sleep and not hibernate. > > I waited maybe a minute, then opened the lid. No response. On keyboard > activity, i could hear the disks spin up. > > Tried ssh from outside, but I had disabled password access and hadn't > copied the relevant tokens to the other box. Did get a Permission > denied (publickey, keyboard-interactive) response once, but a few > minutes later, there was no route to host. I woud guess it went back > to sleep and wouldn't wake up, except this time the disks did not go > quiet. > > Ended up with a long press on the power button.
Congratulations. You have a laptop that suspend/resume does not work on. It needs to be fixed. Back we were super active working on suspend/resume we asked EVERYONE TO TEST repeatedly. Many people did not test. Almost like they assumed others would do the testing. Even after lots of notice from us that suspend/resume is entirely undocumented BS. Also, like they didn't understand when a group of developers is super active, and asks for testing, that is because they are in the thick of it, understand almost all the pieces better, have enthusiasm, etc. That is the time to try to help. Later on, it is more difficult to get back into it. Since suspend/resume was highly functioning, lid suspend was turned on so that the remaining systems could be tested and we'd finally get reports. Hurray. We are finally getting reports. Eventually we'll collect enough information and make further advancements resolving these suspend/resume probblems. Maybe we'll even find someone out there pulling up their sleeves and providing more insight into the remaining issues.
