From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206575] New: [amdgpu] [drm] No video signal on resume from suspend, R9 380
Date: Mon, 17 Feb 2020 16:28:39 +0000 [thread overview]
Message-ID: <bug-206575-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206575
Bug ID: 206575
Summary: [amdgpu] [drm] No video signal on resume from suspend,
R9 380
Product: Drivers
Version: 2.5
Kernel Version: 5.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: veox+kernel@veox.pw
Regression: No
Created attachment 287441
--> https://bugzilla.kernel.org/attachment.cgi?id=287441&action=edit
dmesg output for resume-from-suspend, linux 5.5.4
OS: Arch Linux
GPU: (MSI) Radeon R9 380
On `systemctl suspend` and subsequent resume, the monitors display "no signal".
The machine is responsive, commands can be typed on the keyboard, SSH'ing is
also possible.
Somewhat unexpectedly, resume from hibernation works fine (i.e. there is
signal).
This started happening a few weeks ago, seemingly when `linux` v5.5.2 was
installed. Was also present on v5.5.3 and v5.5.4 (current).
`linux-lts` v5.4.20 does not exhibit this behaviour; it's a regression.
--
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:[~2020-02-17 16:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:28 bugzilla-daemon [this message]
2020-02-17 16:29 ` [Bug 206575] [amdgpu] [drm] No video signal on resume from suspend, R9 380 bugzilla-daemon
2020-02-17 16:29 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:33 ` bugzilla-daemon
2020-02-17 16:38 ` bugzilla-daemon
2020-02-18 17:47 ` bugzilla-daemon
2020-02-18 21:33 ` bugzilla-daemon
2020-02-18 21:44 ` bugzilla-daemon
2020-02-18 22:06 ` bugzilla-daemon
2020-02-19 19:51 ` bugzilla-daemon
2020-02-21 0:42 ` bugzilla-daemon
2020-02-24 2:12 ` bugzilla-daemon
2020-03-16 9:39 ` bugzilla-daemon
2020-03-20 19:54 ` bugzilla-daemon
2020-03-20 20:15 ` bugzilla-daemon
2020-03-20 22:03 ` bugzilla-daemon
2020-03-23 5:06 ` bugzilla-daemon
2020-03-24 20:11 ` bugzilla-daemon
2020-04-10 8:35 ` bugzilla-daemon
2020-04-11 13:56 ` bugzilla-daemon
2020-04-11 13:59 ` bugzilla-daemon
2020-04-14 9:09 ` bugzilla-daemon
2020-04-14 13:28 ` bugzilla-daemon
2020-04-14 13:31 ` bugzilla-daemon
2020-04-14 14:10 ` bugzilla-daemon
2020-04-15 11:43 ` bugzilla-daemon
2020-04-15 11:44 ` bugzilla-daemon
2020-04-15 11:45 ` 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-206575-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 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).