From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204227] Visual artefacts and crash from suspend on amdgpu
Date: Mon, 09 Sep 2019 11:07:15 +0000 [thread overview]
Message-ID: <bug-204227-2300-1pC48zFuTU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204227-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204227
--- Comment #11 from tones111@hotmail.com ---
Some good news. After a bios update to Lenovo's E485/E585 1.54 I no longer
need to provide additional boot arguments in order for the machine to come up
and the visual artifacts have gone away.
I would see issues with some fonts in Firefox that looked similar to your
screenshot. The easiest way for me to reproduce the problem was to resize my
terminal (Alacritty) or scroll around in gitk or gvim.
After a few days running on the new bios I haven't seen the artifacts, so this
bug looks to be resolved for me since kernel 5.2.11.
Thanks!
--
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 prev parent reply other threads:[~2019-09-09 11:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 22:49 [Bug 204227] New: Visual artefacts and crash from suspend on amdgpu bugzilla-daemon
2019-07-18 22:50 ` [Bug 204227] " 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 [this message]
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-1pC48zFuTU@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.