From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101926] kabini amdgpu: LVDS not working after resume from suspend (works with radeon)
Date: Wed, 26 Jul 2017 12:34:37 +0000 [thread overview]
Message-ID: <bug-101926-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101926
Bug ID: 101926
Summary: kabini amdgpu: LVDS not working after resume from
suspend (works with radeon)
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: chithanh@gentoo.org
Using Linux 4.12.3 on a netbook with AMD A4-1200 Kabini APU and the amdgpu
driver:
Upon resuming from suspend-to-RAM, the LVDS display will become all while.
This situation will persist until a reboot, even after turning it off and on
again with xrandr.
Backlight control works fine at all times. External displays (VGA, HDMI) are
not affected. The radeon driver does not have this problem.
I noticed that in bug 42960 a very similar issue was fixed in radeon, but am
currently unsure whether the fix made it into amdgpu too.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2627 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
next reply other threads:[~2017-07-26 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 12:34 bugzilla-daemon [this message]
2017-07-26 12:38 ` [Bug 101926] kabini amdgpu: LVDS not working after resume from suspend (works with radeon) bugzilla-daemon
2019-11-19 8:20 ` bugzilla-daemon
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-101926-502@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;
as well as URLs for NNTP newsgroup(s).