amdsmu: Diagnose S0i3 entry after resume
Needs ReviewPublic
Actions

Authored by obiwac on Mon, Sep 14, 6:31 PM.

Details

Reviewers

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.

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Skipped

Unit

Tests Skipped

Build Status

Buildable 76893
Build 73776: arc lint + arc unit

Event Timeline

obiwac created this revision.Mon, Sep 14, 6:31 PM

Herald added a subscriber: imp. · View Herald TranscriptMon, Sep 14, 6:31 PM

obiwac requested review of this revision.Mon, Sep 14, 6:31 PM

Harbormaster completed remote builds in B76892: Diff 186706.Mon, Sep 14, 6:31 PM

obiwac added a parent revision: D59672: acpi: Warn if no amdsmu(4) loaded after suspend-to-idle resume.Mon, Sep 14, 6:32 PM

only give IP block detail for Phoenix

Harbormaster completed remote builds in B76893: Diff 186707.Mon, Sep 14, 6:44 PM

obiwac edited the summary of this revision. (Show Details)Mon, Sep 14, 6:45 PM

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

Harbormaster completed remote builds in B76894: Diff 186708.Mon, Sep 14, 6:53 PM

obiwac mentioned this in D59674: amdsmu: Hints on what to do if IP block blocking S0i3.Mon, Sep 14, 6:56 PM

obiwac added a child revision: D59674: amdsmu: Hints on what to do if IP block blocking S0i3.Mon, Sep 14, 6:57 PM

Revision Contents
Changeset List

Path

Size

sys/

dev/

amdsmu/

amdsmu.h

1 line

amdsmu.c

44 lines

Diff 186707

View Options

sys/dev/amdsmu/amdsmu.h