All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111122] 2500U: Graphics corruption on kernel 5.2
Date: Sat, 13 Jul 2019 06:56:39 +0000	[thread overview]
Message-ID: <bug-111122-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1778 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111122

            Bug ID: 111122
           Summary: 2500U: Graphics corruption on kernel 5.2
           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: andreaskem@web.de

Created attachment 144771
  --> https://bugs.freedesktop.org/attachment.cgi?id=144771&action=edit
Kernel log

Arch Linux
Lenovo E485 (16 GiB RAM)
AMD Ryzen 2500U

xorg-server 1.20.5-2
mesa 19.1.2-1
xf86-video-amdgpu 19.0.1-1
libdrm 2.4.99-1

After upgrading to the linux kernel 5.2 from the Arch Linux repositories, my
laptop started to show graphical corruption in Firefox or Konsole. It is much
worse if something is moving on the screen e.g., a video is playing. Sometimes
Firefox is almost unusable as a result. A downgrade to 5.1.16 immediately fixes
the issues.

Somebody mentioned similar corruption for bug 109206:
https://bugs.freedesktop.org/show_bug.cgi?id=109206#c57

My kernel command line is:

initrd=\amd-ucode.img initrd=\initramfs-linux.img
root=PARTUUID=34098e4c-f1bf-4a43-a0a8-2ba3ed3c71a6 idle=nomwait
psmouse.synaptics_intertouch=1 acpi_osi=Linux amdgpu.gpu_recovery=1
ivrs_ioapic[32]=00:14.0

I used to have iommu=pt or iommu=off on the command line to get this laptop to
boot properly but I have not needed that switch for a while. I might try to
reintroduce it with 5.2 just to see what happens. In any case, my setup worked
before, so something does not seem right.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3508 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

             reply	other threads:[~2019-07-13  6:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13  6:56 bugzilla-daemon [this message]
2019-07-13  6:57 ` [Bug 111122] 2500U: Graphics corruption on kernel 5.2 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
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@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.