[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 1410 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

            Bug ID: 104888
           Summary: DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB &
                    agd5f's drm-next-4.17-wip
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: robink@creosotehill.org

Hello-
    I'm currently running a kernel directly based upon agd5f's
drm-next-4.17-wip (commit aa876beccdd9d6694df78ebbb395eb206d4cb84e at the time
of writing this) (I've applied a couple of EFI fixups and tweaked the
.gitignore, but none of my cherry-picked commits should be dinking with the
DRM/KMS/AMDGPU code).
    The system boots, and brings up the AMDGPU driver and FB with no issue, but
the display (a Samsung S27C650 attached via DisplayPort) fails to sleep.  I've
tried forcing it into sleep mode via setterm, to no avail.  There is no
error/warning (or info of any kind) logged to the kernel console.  If someone
could suggest a kernel command-line boot option to increase the verbosity of
the AMDGPU driver, I would be very appreciative.  Thank you in advance.

        -Robin K.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2723 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 376 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

--- Comment #1 from Harry Wentland <harry.wentland@amd.com> ---
You can try amdgpu.dc_log=1 and drm.debug=4.

Does the display blank out and then wake right back up or do you see no change
at all on the display when trying to enter dpms?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 513 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

--- Comment #2 from Robin Kauffman <robink@creosotehill.org> ---
(In reply to Harry Wentland from comment #1)
> You can try amdgpu.dc_log=1 and drm.debug=4.

Thanks, I'll try both of these and report back.
> 
> Does the display blank out and then wake right back up or do you see no
> change at all on the display when trying to enter dpms?

I see no change whatsoever.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1476 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 578 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

--- Comment #3 from Harry Wentland <harry.wentland@amd.com> ---
Curiously enough this is the first time I've heard of setterm. I'm not sure if
it's really supported but I tried amdgpu, non-amdgpu (i.e. vbios), and an Intel
platform and on neither I can get setterm --powersafe on/off to do anything, no
matter whether in a VT or in X (seems like it's intended for VT).

We do support "xset -display :0.0 dpms force off" when you're in X.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1442 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 1021 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #4 from Alex Deucher <alexdeucher@gmail.com> ---
I believe setterm uses vesa vbi calls (i.e., calls into the legacy vesa real
mode vbi interface) to blank the screen which only works on boards with a
legacy vbi interface (i.e., won't work UEFI systems).  Doing that goes behind
the driver's back and touches the hw directly.  Additionally, vbi support for
multiple displays is pretty much non existent so even if your board supports
vbi, it's not likely to work if you have multiple displays or are using a
display configuration different from what came up at boot.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2630 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

--- Comment #5 from Robin Kauffman <robink@creosotehill.org> ---
(In reply to Harry Wentland from comment #3)
> Curiously enough this is the first time I've heard of setterm. I'm not sure
> if it's really supported but I tried amdgpu, non-amdgpu (i.e. vbios), and an
> Intel platform and on neither I can get setterm --powersafe on/off to do
> anything, no matter whether in a VT or in X (seems like it's intended for
> VT).
> 
> We do support "xset -display :0.0 dpms force off" when you're in X.

Huh, interesting.  I can't (yet) test 'xset -display :0.0 dpms force off',
since in still having issues bringing X/Wayland up, but that's a separate bug.

No useful output from amdgpu.dc_log=1 and drm.debug=4 set yet, but I'm trying
agd5f's latest push to drm-next-4.17-wip, which has a commit that looks like it
may contain a fix, so we'll see.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2004 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 578 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

Robin Kauffman <robink@creosotehill.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTABUG                     |---

--- Comment #6 from Robin Kauffman <robink@creosotehill.org> ---
Reopening since the DPMS timeout (that *used to* work) still isn't working.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2150 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 382 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

Robin Kauffman <robink@creosotehill.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|XOrg git                    |unspecified

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1125 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104888] DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB & agd5f's drm-next-4.17-wip

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 924 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104888

Robin Kauffman <robink@creosotehill.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|REOPENED                    |RESOLVED

--- Comment #7 from Robin Kauffman <robink@creosotehill.org> ---
Works with current-ish drm-next-4.18-next commit
(52132fd03504140b4cc58c01b19e82929a03af7a), most recent issue was an omission
on my part (failing to put consoleblank=600 (or some other non-zero integer
value) in the kernel commandline).  Don't know which commit fixed things, as I
haven't bisected my way through a few (at least) weeks of commit history.  I
can have a go at it if someone really wants me to.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2555 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel