On Fri, Jun 26, 2026 at 11:03:28PM -0400, [email protected] wrote:
> >Synopsis: Bay Trail laptop fails to wake from S0ix suspend
> >Category: amd64
> >Environment:
> System : OpenBSD 7.9
> Details : OpenBSD 7.9-current (GENERIC.MP) #42: Fri Jun 26 21:28:40
> EDT 2026
>
> [email protected]:/home/john/lenovo-80r2/src/sys/arch/amd64/compile/GENERIC.MP
>
> Architecture: OpenBSD.amd64
> Machine : amd64
> >Description:
> I'm unable to wake my Bay Trail Lenovo 80R2 (IdeaPad 100S-11IBY)
> after entering S0ix suspend. The last messages from syslog
> during suspend show that it does attempt to use S0:
>
> Jun 26 21:52:05 humilitas apmd: system suspending
> Jun 26 21:52:05 humilitas apmd: battery status: CRITICAL. external power
> status: not connected. estimated battery life 0%
> Jun 26 21:52:06 humilitas /bsd: acpi0: S3 unavailable, using S0
> Jun 26 21:52:07 humilitas /bsd: drm : [drm] i915 raw-wakerefs=1 wakelocks=1
> on cleanup
> Jun 26 21:52:08 humilitas dhcpleased[36124]: bpf_receive: read: Input/output
> error
> Jun 26 21:52:08 humilitas dhcpleased[60085]: deconfigure_interface: cannot
> find interface 3
> Jun 26 21:52:08 humilitas slaacd[40417]: delete_address: cannot find
> interface 3
> Jun 26 21:52:08 humilitas slaacd[40417]: delete_address: cannot find
> interface 3
> Jun 26 21:52:08 humilitas slaacd[40417]: failed to send route message: No
> such process
> Jun 26 21:52:09 humilitas /bsd: urtwn0 detached
> Jun 26 21:52:10 humilitas /bsd: video0 detached
> Jun 26 21:52:10 humilitas /bsd: uvideo0 detached
> Jun 26 21:52:11 humilitas /bsd: uhub1 detached
>
> After this, my only option is to hard-reset the system.
>
> Note that the dmesg doesn't report an S0ix sleep state.
> Apparently there's no _S0 package in the ACPI tables. Maybe
> that's a quirk of early "modern standby" systems, I'm not sure.
> It seems like it's just a cosmetic issue.
I suspect that is related to this being a "hardware reduced" ACPI.
from FADT:
Hardware Reduced (V5) : 1
Low Power S0 Idle (V5) : 1
> >How-To-Repeat:
> Close the lid or run `zzz'. The display turns off and the system
> drops off the network. Wait a few seconds and open the lid,
> press the power button or keys. The display does not turn on and
> there is no indication that the system has woken up.
> >Fix:
> The patch below allows bytgpio(4) controller interrupts to wake
> the system when any of its pins is listed in the controller's
> _AEI. This mirrors what's been done in amdgpio(4). With this
> patch I'm able to wake the system by opening the lid.
thanks, committed
