Page MenuHomeFreeBSD

amdsmu: Diagnose S0i3 entry after resume
ClosedPublic

Authored by obiwac on Mon, Sep 14, 6:31 PM.
Tags
None
Referenced Files
F173740117: D59673.diff
Mon, Sep 28, 1:40 AM
F173732769: D59673.id186909.diff
Mon, Sep 28, 12:37 AM
F173715681: D59673.id187080.diff
Sun, Sep 27, 10:07 PM
F173712870: D59673.id186707.diff
Sun, Sep 27, 9:43 PM
F173707152: D59673.diff
Sun, Sep 27, 8:53 PM
F173705241: D59673.id186708.diff
Sun, Sep 27, 8:39 PM
F173656656: D59673.id186706.diff
Sun, Sep 27, 12:42 PM
Unknown Object (File)
Sun, Sep 27, 5:58 AM
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 76892
Build 73775: 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.