Page MenuHomeFreeBSD

amdsmu: Diagnose S0i3 entry after resume
ClosedPublic

Authored by obiwac on Mon, Sep 14, 6:31 PM.
Tags
None
Referenced Files
F172579609: D59673.id187080.diff
Sat, Sep 19, 10:22 AM
F172499577: D59673.id187080.diff
Fri, Sep 18, 9:26 PM
Unknown Object (File)
Fri, Sep 18, 7:51 PM
Unknown Object (File)
Thu, Sep 17, 10:25 PM
Unknown Object (File)
Thu, Sep 17, 8:49 PM
Unknown Object (File)
Thu, Sep 17, 8:33 PM
Unknown Object (File)
Thu, Sep 17, 7:56 PM
Unknown Object (File)
Thu, Sep 17, 7:54 PM
Subscribers

Details

Summary

Print out diagnostic information after resuming from suspend-to-idle if
we failed to enter S0i3, i.e. the IP blocks that were blocking entry to
S0i3.

Don't give detailed IP block info for other SMUs than for Phoenix, as I
have not had a chance to test these yet and the SMU seems to be very
quirky.

Sponsored by: The FreeBSD Foundation

Test Plan

Purposely prevent S0i3 entry by e.g. not loading thunderbolt(4) or amdgpu and see if amdsmu(4) correctly reports the equivalent IP blocks after resuming from suspend-to-idle.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 76996
Build 73879: arc lint + arc unit

Event Timeline

only give IP block detail for Phoenix

IP block can have active time but not be blocking, actually

rebase & use new power_resume_check eventhandler

This revision is now accepted and ready to land.Fri, Sep 18, 7:34 AM
This revision was automatically updated to reflect the committed changes.