From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204227] New: Visual artefacts and crash from suspend on amdgpu
Date: Thu, 18 Jul 2019 22:49:01 +0000 [thread overview]
Message-ID: <bug-204227-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=204227
Bug ID: 204227
Summary: Visual artefacts and crash from suspend on amdgpu
Product: Drivers
Version: 2.5
Kernel Version: 5.2.1
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: dolohow@outlook.com
Regression: No
Created attachment 283823
--> https://bugzilla.kernel.org/attachment.cgi?id=283823&action=edit
dmesg
After upgrading kernel from 5.1.14 to 5.2.1 I encountered many artifacts during
desktop session. Also when going from suspend state, external monitor is green
and kernel crashes. See dmesg
--
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:[~2019-07-18 22:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 22:49 bugzilla-daemon [this message]
2019-07-18 22:50 ` [Bug 204227] Visual artefacts and crash from suspend on amdgpu bugzilla-daemon
2019-07-19 19:16 ` bugzilla-daemon
2019-07-20 15:27 ` bugzilla-daemon
2019-08-26 23:42 ` bugzilla-daemon
2019-08-27 13:12 ` bugzilla-daemon
2019-08-27 18:07 ` bugzilla-daemon
2019-08-27 18:31 ` bugzilla-daemon
2019-08-28 0:47 ` bugzilla-daemon
2019-08-28 1:48 ` bugzilla-daemon
2019-09-09 8:29 ` bugzilla-daemon
2019-09-09 11:07 ` bugzilla-daemon
2019-09-09 11:14 ` bugzilla-daemon
2019-09-19 21:09 ` bugzilla-daemon
2019-09-19 21:11 ` bugzilla-daemon
2019-09-23 7:36 ` 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-204227-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).