From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108575] amd-staging-drm-next, R4 Mullins hdmi monitor wont wake up from S3 - *ERROR* REG_WAIT timeout 1us * 80000 tries - dce_abm_immediate_disable
Date: Sat, 23 Feb 2019 14:06:06 +0000 [thread overview]
Message-ID: <bug-108575-502-vhTiBjtjsL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108575-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 995 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108575
Przemek <soprwa@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #5 from Przemek <soprwa@gmail.com> ---
As for today's git pull everything (suspend/hibernate/resume) seems to work
just fine.
I have connected SAMSUNG TV to HDMI output and it wakes up properly.
The problem occurs only on hdmi -> vga display adapter which I'm using to
connect my old PHILIPS 170C lcd monitor. (VGA connector is not implemented on
amdgpu).
I'm closing this bug report as FIXED, but still wondering why adapter has to be
replugged to make monitor wake up/being discovered by amdgpu driver, tough.
Thank you very much.
Przemek
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2752 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-02-23 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 10:29 [Bug 108575] amd-staging-drm-next, R4 Mullins hdmi monitor wont wake up from S3 - *ERROR* REG_WAIT timeout 1us * 80000 tries - dce_abm_immediate_disable bugzilla-daemon
2018-11-25 8:11 ` bugzilla-daemon
2018-12-16 20:45 ` bugzilla-daemon
2018-12-16 20:59 ` bugzilla-daemon
2019-02-16 9:31 ` bugzilla-daemon
2019-02-23 14:06 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108575-502-vhTiBjtjsL@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox