Page MenuHomeFreeBSD

amdsmu: Hints on what to do if IP block blocking S0i3
ClosedPublic

Authored by obiwac on Mon, Sep 14, 6:56 PM.
Tags
None
Referenced Files
F172355656: D59674.diff
Thu, Sep 17, 10:24 PM
F172336498: D59674.id186928.diff
Thu, Sep 17, 7:53 PM
Unknown Object (File)
Thu, Sep 17, 8:02 AM
Unknown Object (File)
Thu, Sep 17, 5:46 AM
Unknown Object (File)
Thu, Sep 17, 1:22 AM
Unknown Object (File)
Thu, Sep 17, 12:53 AM
Unknown Object (File)
Wed, Sep 16, 8:41 AM
Unknown Object (File)
Tue, Sep 15, 2:33 PM
Subscribers

Details

Summary

Sponsored by: The FreeBSD Foundation

Test Plan

Same as D59673

This is what the output looks like if I don't load thunderbolt(4):

amdsmu0: failed to enter S0i3 during last suspend; battery drain will be excessive
amdsmu0: IP blocks that blocked S0i3 entry:
amdsmu0:   CPU (active for 3865335 us)
amdsmu0:     hint: this can happen due to other IP blocks
amdsmu0:   USB3_0 (active for 3865335 us)
amdsmu0:     hint: load tb to allow this block to suspend
amdsmu0:     hint: see thunderbolt(4)
amdsmu0:   USB3_1 (active for 3865335 us)
amdsmu0:     hint: load tb to allow this block to suspend
amdsmu0:     hint: see thunderbolt(4)
amdsmu0:   MPM (active for 3865335 us)
amdsmu0:     hint: this can happen due to other IP blocks

Diff Detail

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

Event Timeline

better hints & truly ignore IP blocks meant to be ignored

more help for CPU and MPM IP blocks

olce added inline comments.
sys/dev/amdsmu/amdsmu.c
355–359

Inverting the test makes for more compact code, but that's fine.

This revision is now accepted and ready to land.Fri, Sep 18, 7:35 AM