From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 197851] New: Resume from suspend sometimes results in black screen on Radeon R5
Date: Sat, 11 Nov 2017 20:01:38 +0000 [thread overview]
Message-ID: <bug-197851-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=197851
Bug ID: 197851
Summary: Resume from suspend sometimes results in black screen
on Radeon R5
Product: Drivers
Version: 2.5
Kernel Version: 4.14.0-041400rc8-generic
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: sonarsoundapplications@gmail.com
Regression: No
As stated in the description, resuming from suspend will occasionally result in
the screen remaining black until hard reset. I have pressed all of the keys,
clicked the mouse, and even held the power button for varying lengths of time.
It isn't just limited to screen lid closing either. Screen timeouts and manual
suspend also feature this issue. I saw a similar bug for a rx480 but figured
since it's a different GPU, it may need its own bug report. Feel free to merge
the issues if you think I am incorrect.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-11-11 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 20:01 bugzilla-daemon [this message]
2017-11-13 15:15 ` [Bug 197851] Resume from suspend sometimes results in black screen on Radeon R5 bugzilla-daemon
2017-11-13 20:52 ` bugzilla-daemon
2017-12-11 22:42 ` bugzilla-daemon
2017-12-14 15:32 ` bugzilla-daemon
2017-12-15 0:13 ` 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-197851-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.