Thanks Mike. It didn't even occur to me that I could use the LED blinker like that!
I'm going to have to give this a shot. On 3 May 2018 16:43:09 BST, Mike Larkin <[email protected]> wrote: >On Thu, May 03, 2018 at 09:56:52AM +0100, Edd Barrett wrote: >> Hi, >> >> On Fri, Jan 12, 2018 at 11:40:31AM +0000, Edd Barrett wrote: >> > For the month or so I've had it (usually updating my snapshot every >week >> > or so) suspend has been a bit flaky. Often it does zzz and wake >fine, >> > but occasionally (say 1 time out of 5), something goes wrong. >Either: >> >> Sorry to dig up an old thread. Just wanted to mention that my 5th >> generation X1 is still frequently failing to wake from suspend on >newer >> snapshots. >> >> Cheers >> >> -- >> Best Regards >> Edd Barrett >> >> http://www.theunixzoo.co.uk >> > >You can help diagnose this yourself. > >If the machine has a visual indicator of sleeping/waking (like a >blinking led), >move the SST_WAKING acpi_indicator calls around in the resume path so >you >can see where it's getting stuck. > >If you get to the point that it's resuming devices and can't figure out >which >device is broken, you can turn a "hang" into a "reset" by placing calls >to >cpu_reset in various places, to let you know where it gets to. If it >resets, >you know you got that far and can move the reset to later devices. that >way >you can narrow down the area where it's hanging. > >You can also use the vPro serial-over-lan and output messages there if >your >machine supports that. > >These sorts of techniques are what I used when diagnosing things when >we were >first implementing suspend and hibernate, when the console is >nonresponsive or >black or unavailable. > >-ml -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
