From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109298] AMDGPU leaving DRI2 enabled causes white artifacting
Date: Fri, 11 Jan 2019 03:04:47 +0000 [thread overview]
Message-ID: <bug-109298-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2106 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109298
Bug ID: 109298
Summary: AMDGPU leaving DRI2 enabled causes white artifacting
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: tkdestroyer2+bugs-freedesktop@gmail.com
I am running:
Solus OS
Linux kernel 4.18.5
xorg-driver-video-amdgpu 18.1.0
xinit 1.4.0
xorg-server 1.20.3
VG248QE DisplayPort 1080@144
$ cat /sys/class/drm/card1/device/vbios_version
MS-V30823-F5
I have an MSI R9 390, one of the bugged ones. I can boot successfully using
cik_support=1 dpm=1 and dc=1.
The bug I am encountering is the following:
- Use default Xorg configuration
- Encounter white rectangles where there should be rendered content
ex: Desktop background is between 6 and 9 tenths white starting from the top
going down. Only the rest of the bottom strip is showing.
ex: Firefox shows white rectangles of white pixels where there should be
content. They vary in size and position and tend to show up after recent
renderings. Can be 'wiped' away using the mouse-highlight.
I have managed to reduce the impact of this bug by switching off DRI2 by
setting xorg configuration option AccelMethod to none. No other configuration
of options (as they appear in the manpages for amdgpu) will work in removing
these issues. This lets me utilize accelerated 3D graphics until I can get DRI2
up and running again.
It may be important to note that some applications will work, particularly when
they are small windows, like when first opening a PDF. Scrolling and everything
works normally, but when one maximizes the window to 1080p, the artifacts
appear. One application that worked is MineTest, which appears to be using 2D
rendering (poor performance with DRI2 off).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3410 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-11 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 3:04 bugzilla-daemon [this message]
2019-01-11 14:07 ` [Bug 109298] AMDGPU leaving DRI2 enabled causes white artifacting bugzilla-daemon
2019-01-11 19:21 ` bugzilla-daemon
2019-01-11 19:23 ` bugzilla-daemon
2019-01-11 19:24 ` bugzilla-daemon
2019-01-11 19:25 ` bugzilla-daemon
2019-01-11 20:46 ` bugzilla-daemon
2019-11-19 9:10 ` 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-109298-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.