Josh Grosse <[email protected]> wrote: > On Mon, Feb 14, 2022 at 05:58:37PM +0100, Dirk-Wilhelm Peters wrote: > > "Theo de Raadt" <[email protected]> wrote: > > > > > > OpenBSD 7.0-current (GENERIC.MP) #325: Thu Feb 10 12:26:12 MST 2022 > > > > > > Your subject says "current snapshot". But then you show a 4-day old > > > kernel. > > > > > > You can do better. > > > > Yes. Kernel #334 is also silent after returning from suspend mode. > > I have the same X220 hardware. Bisecting the kernel indicates this > commit caused the regression. Tested on the X220 with GENERIC.MP. > > commit ad814436a071b6401bfaf527a709138b9bf992e2 (refs/bisect/bad) > Author: deraadt <[email protected]> > Date: Tue Feb 8 17:25:10 2022 +0000 > > The suspend/resume code is a sticky mess of MI, MD, and ACPI sequencing. > This splits out the MI sequencing, backing it with per-architecture helper > functions. Further steps will be neccesary because ACPI and MD are too > tightly coupled, but soon we'll be able to use this code for more > architectures > (which depends on figuring out the lowest-level cpu sleeping method) > ok kettenis
I was meticulous about keeping the order-of-operations the same as before, but something very subtle has happened. We need to recall that suspend/resume on some machines has never behaved perfectly. Maybe some heisenbug has moved around. I've been re-reading all morning and I still can't see any reason.
