Post by Charles A Daniels
Closing the lid on the T430 causes OpenBSD to suspend, as per my
setting for machdep.lidaction=1. This usually works as expected, but
occasionally I take my laptop out of my bag to find it sitting on the
xenodm login screen, not suspended, with the lid closed, having lost
power and rebooted at some point after being suspended.
I would like to collect further information so a bug report can be
filed, but I feel that the above description alone is insufficient to
constitute a useful bug report. To that end, I would like to solicit
advice on what information can be collected and what debugging steps
can be taken so that I can write a useful bug report.
I'm running the 6.4 release, and I have run fw_update and syspatch
periodically since install.
I previously asked for help on r/openbsd, but still have not been
able to either resolve the problem or gather sufficient information for
a bug report.
I have a similar issue with the X220, the problem is a watchdog timer,
that I suspect is in the Intel ME. It expires without being reset and
forces the machine to restart. Or at least that is the cause of that
happening on my X230's. I've ripped a few of them apart and analyzed
their guts and found only the CPU and a few other chips are active
during suspend. I've probed all the buses of those other chips and none
make a peep when the machine reboots, the only chip left active is the
Intel ME chunk of the CPU, and for obvious reasons, I have no idea what
it is doing, so I suspect it is the culprit.
I gave up on the work a few months ago since it seemed easier to just
accept that suspend isn't going to work and just use suspend-to-disk or
just shut the machine down completely. If you want to do more, and have
access to a Windows machine, you can try pulling apart the Lenovo
drivers to see what the Lenovo-specific ACPI driver is doing when the
machine goes into suspend.