From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111122] 2500U: Graphics corruption on kernel 5.2
Date: Thu, 08 Aug 2019 08:43:58 +0000 [thread overview]
Message-ID: <bug-111122-502-pV897RiZNL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111122-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111122
--- Comment #7 from Wiktor Kaczor <wiktoraleksanderkaczor@gmail.com> ---
I have the same problem using the Lenovo 530S-14ARR with Ryzen 5 2500U.
The XFCE4 compositing makes the system immediately freeze as soon as I log in
on Manjaro with the 5.2.4-1 kernel.
On the 5.3rc2 kernel, I can enable it and it doesn't immediately hang without
recovery. That said, the compositing doesn't work and we have a lot of
corruption as soon as anything updates on screen.
The "iommu=pt" option didn't do anything for me in regards to reducing the
corruption.
I didn't know which logs to include so I didn't. Send reply with the names and
hopefully, approximate path of any logs to include.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1618 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-08 8:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 6:56 [Bug 111122] 2500U: Graphics corruption on kernel 5.2 bugzilla-daemon
2019-07-13 6:57 ` bugzilla-daemon
2019-07-13 7:03 ` bugzilla-daemon
2019-07-14 4:59 ` bugzilla-daemon
2019-07-15 16:42 ` bugzilla-daemon
2019-07-22 7:45 ` bugzilla-daemon
2019-07-22 12:30 ` bugzilla-daemon
2019-08-02 13:28 ` bugzilla-daemon
2019-08-08 8:43 ` bugzilla-daemon [this message]
2019-08-08 9:30 ` bugzilla-daemon
2019-08-08 13:47 ` bugzilla-daemon
2019-08-09 3:30 ` bugzilla-daemon
2019-08-09 7:21 ` bugzilla-daemon
2019-08-09 10:06 ` bugzilla-daemon
2019-08-10 17:46 ` bugzilla-daemon
2019-08-12 8:19 ` bugzilla-daemon
2019-08-12 14:49 ` bugzilla-daemon
2019-08-13 8:15 ` bugzilla-daemon
2019-08-15 9:26 ` bugzilla-daemon
2019-08-15 19:15 ` bugzilla-daemon
2019-08-16 22:15 ` bugzilla-daemon
2019-08-18 2:18 ` bugzilla-daemon
2019-08-18 10:22 ` bugzilla-daemon
2019-08-19 23:31 ` bugzilla-daemon
2019-08-21 9:21 ` bugzilla-daemon
2019-08-26 10:14 ` bugzilla-daemon
2019-08-26 15:53 ` bugzilla-daemon
2019-08-26 18:27 ` bugzilla-daemon
2019-08-26 18:28 ` bugzilla-daemon
2019-09-19 9:32 ` bugzilla-daemon
2019-09-20 1:39 ` bugzilla-daemon
2019-09-23 17:31 ` bugzilla-daemon
2019-11-19 9:32 ` 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-111122-502-pV897RiZNL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox