From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206393] New: amdgpu: garbled screen after resume
Date: Sun, 02 Feb 2020 20:42:14 +0000 [thread overview]
Message-ID: <bug-206393-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206393
Bug ID: 206393
Summary: amdgpu: garbled screen after resume
Product: Drivers
Version: 2.5
Kernel Version: 5.5.1-arch1, 5.5-arch1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: bjo@nord-west.org
Regression: No
Created attachment 287081
--> https://bugzilla.kernel.org/attachment.cgi?id=287081&action=edit
garbled screen
On a Thinkpad A275 with a Radeon R5/R6/R7 (verbose lspci attached) the screen
is garbled after resume. First a black screen appears and then more and more
white pixels appear from the border to the middle of the screen.
Restarting the X-session via SSH does not help, the VTs are also inaccessible.
--
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-02 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 20:42 bugzilla-daemon [this message]
2020-02-02 20:42 ` [Bug 206393] amdgpu: garbled screen after resume bugzilla-daemon
2020-02-02 20:43 ` bugzilla-daemon
2020-02-03 14:59 ` bugzilla-daemon
2020-02-03 15:04 ` bugzilla-daemon
2020-02-03 21:48 ` bugzilla-daemon
2020-02-04 13:34 ` bugzilla-daemon
2020-02-18 22:06 ` bugzilla-daemon
2020-02-25 21:33 ` bugzilla-daemon
2020-02-25 21:37 ` bugzilla-daemon
2020-02-28 18:08 ` bugzilla-daemon
2020-02-28 21:56 ` bugzilla-daemon
2020-03-01 10:01 ` 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-206393-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.