[Bug 263557] ACPI S3 doesn't resume on a MateBook X Pro 2021

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

--- Comment #13 from Peter Much <pmc@citylink.dinoex.sub.org> ---
My installation got the packages from the public repo as of this week. They
are:

drm-510-kmod 5.10.113_6
drm-kmod 20220907_1
gpu-firmware-kmod 20220511,1
gpu-firmware-*-kmod 20220511  // lots of them

When starting 'X' I can see these:

[drm] Unable to create a private tmpfs mount, hugepage support will be
disabled(-19).
[drm] Got stolen memory base 0x0, size 0x0
drmn0: successfully loaded firmware image 'i915/tgl_dmc_ver2_08.bin'
drmn0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_08.bin (v2.8)
sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
[drm] Initialized i915 1.6.0 20200917 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "fb".

When trying to suspend, the code in
sys/contrib/dev/acpica/components/hardware/hwsleep.c:AcpiHwLegacySleep() is
reached, and it suspends as soon as the SLP_EN bit is written to Pm1a/Pm1b
(which does not happen with debug.acpi.suspend_bounce=1).

Not by any means was I able to get it back from there. According to
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html, chapter 16.3, the processor
should then start from the Boot Vector and somehow arrive at the Waking Vector;
which doesn't seem to be the case.

I might now blame the firmware, but, as far as I could see, OpenBSD does
basically the same, and there it works.

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