Bug 108533

Summary: [Polaris 20] 4.19.0 final unusable with RX580 - SDDM screen corruption, regression
Product: DRI Reporter: Dieter Nützel <Dieter>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: high CC: alexdeucher, ckoenig.leichtzumerken, harry.wentland, sndirsch
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg-4.19.0-1.gd04171e-default.log
none
Xorg.0.log-4.19.0-1.gd04171e-default
none
20181024_021330.jpg
none
20181024_021334.jpg none

Description Dieter Nützel 2018-10-24 00:05:37 UTC
Created attachment 142163 [details]
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.
Comment 1 Dieter Nützel 2018-10-24 00:06:31 UTC
Created attachment 142164 [details]
Xorg.0.log-4.19.0-1.gd04171e-default
Comment 2 Dieter Nützel 2018-10-24 00:21:43 UTC
Created attachment 142165 [details]
20181024_021330.jpg
Comment 3 Dieter Nützel 2018-10-24 00:22:36 UTC
Created attachment 142166 [details]
20181024_021334.jpg
Comment 4 Dieter Nützel 2018-10-24 00:35:03 UTC
My screen show periodically the 2 attached pictures.

Bug appeared first on 30.09.2018 in amd-staging-drm-next.
Comment 5 Dieter Nützel 2018-10-24 00:58:18 UTC
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 !
Comment 6 Michel Dänzer 2018-10-24 08:33:52 UTC
(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 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.