From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207899] New: AMDGPU large block noise in chrome, on streaming video pages. CS:GO freezes.
Date: Tue, 26 May 2020 16:36:37 +0000 [thread overview]
Message-ID: <bug-207899-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=207899
Bug ID: 207899
Summary: AMDGPU large block noise in chrome, on streaming video
pages. CS:GO freezes.
Product: Drivers
Version: 2.5
Kernel Version: 5.6.6-5.6.14
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: blake.lewis@gmail.com
Regression: No
Kernel 2.6.6 - 5.6.14
AMDGPU
video corruption/noise in blocks (Chrome) and freezes (CS:GO)
HP Elite Disk 705 G4 Micro
AMD Ryzen 5 Pro 2400GE w/ Radeon Vega Graphics
How reproducible:
Chrome: youtube.com or twitch.tv blocks on the screen get corrupted.
CS:GO play for a few minutes
In kernel 5.5.17, no corruption, CS:GO works video freeze.
Additional info:
Fedora 31 and 32
All kernels v5.6 that have been delivered to FC31 and FC32, <=5.6.14 tested
The first 3 kernels v5.6 broke graphics in FC31, so I upgraded to FC32
Kernel 5.5.17 works without video corruption in FC31 and FC32
I am willing to run any data collection needed.
--
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-05-26 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 16:36 bugzilla-daemon [this message]
2020-05-26 16:51 ` [Bug 207899] AMDGPU large block noise in chrome, on streaming video pages. CS:GO freezes bugzilla-daemon
2020-05-26 17:40 ` bugzilla-daemon
2020-05-26 18:00 ` bugzilla-daemon
2020-05-26 18:01 ` bugzilla-daemon
2020-05-26 18:01 ` bugzilla-daemon
2020-05-26 18:05 ` bugzilla-daemon
2020-05-26 18:12 ` 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-207899-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