All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108533] [Polaris 20] 4.19.0 final unusable with RX580 - SDDM screen corruption, regression
Date: Wed, 24 Oct 2018 00:05:37 +0000	[thread overview]
Message-ID: <bug-108533-502@http.bugs.freedesktop.org/> (raw)


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

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.

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

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

             reply	other threads:[~2018-10-24  0:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  0:05 bugzilla-daemon [this message]
2018-10-24  0:06 ` [Bug 108533] [Polaris 20] 4.19.0 final unusable with RX580 - SDDM screen corruption, regression bugzilla-daemon
2018-10-24  0:21 ` bugzilla-daemon
2018-10-24  0:22 ` bugzilla-daemon
2018-10-24  0:35 ` bugzilla-daemon
2018-10-24  0:58 ` bugzilla-daemon
2018-10-24  8:33 ` bugzilla-daemon
2018-11-02  2:45 ` 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-108533-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.