[Bug 280028] S3 suspend of Thinkpad x270 stopped working after freebsd-update to 14.1-RELEASE-p1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028

            Bug ID: 280028
           Summary: S3 suspend of Thinkpad x270 stopped working after
                    freebsd-update to 14.1-RELEASE-p1
           Product: Base System
           Version: 14.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: misc
          Assignee: bugs@FreeBSD.org
          Reporter: freebsd.org@fydagy.netizen.se

After upgrading to 14.1-RELEASE-p1, S3 suspend only works once. Any second
attempt will shutdown network et.c. but only completely suspend after
requesting a system shutdown.

My apologies if the description is imprecise. I am reporting this issue without
really understanding how to debug it, as recommended on #freebsd, due to the
behaviour being fully reproducible.

The relevant output of `bectl list` is:

    14.1-RELEASE_2024-06-03_190500    N      /          74.9M 2024-06-03 19:05
    14.1-RELEASE_2024-06-20_090922    -      -          1.12G 2024-06-20 09:09
    default                           R      -          51.7G 2023-11-06 23:19

If booting into 20240603, suspend and resume works perfectly as expected, with
both kernels 14.0-RELEASE-p6 and 14.1-RELEASE. However booting into any of the
later two breaks suspend, regardless of kernel 14.0-RELEASE-p6 or 14.1-RELEASE.

To elaborate on the broken behaviour; running `acpiconf -s 3` once works. It is
first when running the same command a second time that suspend fails to
complete. Interestingly enough though, if (hours later) running `halt` the
system actually suspends. (On resume from that, it completes the shutdown.)

I did generate a zfs-diff between the boot environments, but the output is
huge. My only idea of going forward is to manually stop services once in the
broken state, to see if that might allow the suspend to happen.

-- 
You are receiving this mail because:
You are the assignee for the bug.