[Bug 108533] [Polaris 20] 4.19.0 final unusable with RX580 - SDDM screen corruption, regression
https://bugs.freedesktop.org/show_bug.cgi?id=108533
Bug ID: 108533 Summary: [Polaris 20] 4.19.0 final unusable with RX580 - SDDM screen corruption, regression Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: Dieter@nuetzel-hh.de
Created attachment 142163 --> https://bugs.freedesktop.org/attachment.cgi?id=142163&action=edit dmesg-4.19.0-1.gd04171e-default.log
Sadly my reported https://bugs.freedesktop.org/show_bug.cgi?id=108096 SDDM screen corruption (unusable desktop) found it's way into 4.19.0 final.
Tried running openSUSE's Kernel:stable kernel-default-4.19.0-1.1.gd04171e.x86_64
and got the same broken SDDM screen and NOT running KDE Plasma 5 desktop as with 'amd-staging-drm-next'. Only gfx (amdgpu) isn't running any longer. All the rest is running as expected.
Going back to openSUSE's Kernel:stable kernel-default-4.18.16-1.1.gbd19c86.x86_64 all is fine, again.
No one commented on my former bug report https://bugs.freedesktop.org/show_bug.cgi?id=108096;-(
Images and logs are mostly the same as with https://bugs.freedesktop.org/show_bug.cgi?id=108096.
No, I can't bisect 'amd-staging-drm-next' 'cause I failed with the several merges from git upstream.
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #1 from Dieter Nützel Dieter@nuetzel-hh.de --- Created attachment 142164 --> https://bugs.freedesktop.org/attachment.cgi?id=142164&action=edit Xorg.0.log-4.19.0-1.gd04171e-default
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #2 from Dieter Nützel Dieter@nuetzel-hh.de --- Created attachment 142165 --> https://bugs.freedesktop.org/attachment.cgi?id=142165&action=edit 20181024_021330.jpg
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #3 from Dieter Nützel Dieter@nuetzel-hh.de --- Created attachment 142166 --> https://bugs.freedesktop.org/attachment.cgi?id=142166&action=edit 20181024_021334.jpg
https://bugs.freedesktop.org/show_bug.cgi?id=108533
Dieter Nützel Dieter@nuetzel-hh.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|medium |high
--- Comment #4 from Dieter Nützel Dieter@nuetzel-hh.de --- My screen show periodically the 2 attached pictures.
Bug appeared first on 30.09.2018 in amd-staging-drm-next.
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #5 from Dieter Nützel Dieter@nuetzel-hh.de --- dmesg show this error (all the time):
[ 14.690300] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser ! [ 16.458594] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser ! [ 16.483781] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser !
https://bugs.freedesktop.org/show_bug.cgi?id=108533
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE CC|michel@daenzer.net | Status|NEW |RESOLVED
--- Comment #6 from Michel Dänzer michel@daenzer.net --- (In reply to Dieter Nützel from comment #0)
No one commented on my former bug report https://bugs.freedesktop.org/show_bug.cgi?id=108096;-(
That's sad, but no justification for filing a duplicate report.
No, I can't bisect 'amd-staging-drm-next' 'cause I failed with the several merges from git upstream.
You most certainly can. If you share the actual commands you're running and their output, we may be able to help.
P.S. No need to add me to the CC list, I get bug updates via the mailing lists.
*** This bug has been marked as a duplicate of bug 108096 ***
https://bugs.freedesktop.org/show_bug.cgi?id=108533
Dieter Nützel Dieter@nuetzel-hh.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org