From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not useable) with RX580, amdgpu, dc=1 (of course), regression
Date: Sat, 29 Sep 2018 03:38:40 +0000 [thread overview]
Message-ID: <bug-108096-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2047 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108096
Bug ID: 108096
Summary: [amd-staging-drm-next] SDDM screen corruption (not
useable) with RX580, amdgpu, dc=1 (of course),
regression
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: Dieter@nuetzel-hh.de
Created attachment 141786
--> https://bugs.freedesktop.org/attachment.cgi?id=141786&action=edit
SDDM corruption 4.18.0-rc1
amd-staging-drm-next (since 21/22 August 2018)
didn't work any longer with my nice RX580
Latest working amd-staging-drm-next kernel was from 16th August 2018
#5024f8dfe478 (my testing for Huang Rui ray.huang at amd.com)
https://lists.freedesktop.org/archives/amd-gfx/2018-August/025332.html
On 22th August I got first SDDM corruption (see attchament) and
[ 14.322826] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser !
in dmesg with amd-staging-drm-next 4.18.0-rc1.
(see attchament) dmesg-4.18.0-rc1-1.g7262353-default+.log
Later (23th August) I saw SDDM corruption and
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser !
plus
[ 3.487757] RIP: 0010:amdgpu_bo_gpu_offset+0x56/0x90 [amdgpu]
(see attchament) dmesg-4.18.0-rc1-1.g7262353-default+.log3
After Alex's upgrade to amd-staging-drm-next 4.19.0-rc1
I got SDDM corruption (see attchament)
and
[ 14.439424] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser !
(see attchament) dmesg-4.19.0-rc1-1.g7262353-default+.log-25.10
First 'bisect' attempt went nuts 'cause the big merge with Linus tree didn't
resolve.
Can't find my former amd-staging-drm-next tag (#5024f8dfe478, see above) any
longer ;-(
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3590 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
next reply other threads:[~2018-09-29 3:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 3:38 bugzilla-daemon [this message]
2018-09-29 3:40 ` [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not useable) with RX580, amdgpu, dc=1 (of course), regression bugzilla-daemon
2018-09-29 3:43 ` bugzilla-daemon
2018-09-29 3:43 ` bugzilla-daemon
2018-09-29 3:44 ` bugzilla-daemon
2018-09-29 3:45 ` bugzilla-daemon
2018-09-29 3:47 ` bugzilla-daemon
2018-09-29 3:48 ` bugzilla-daemon
2018-09-30 13:33 ` bugzilla-daemon
2018-10-23 23:31 ` bugzilla-daemon
2018-10-23 23:41 ` [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not usable) " bugzilla-daemon
2018-10-24 8:33 ` bugzilla-daemon
2018-10-24 9:01 ` bugzilla-daemon
2018-10-25 0:56 ` bugzilla-daemon
2018-10-25 1:24 ` bugzilla-daemon
2018-10-26 3:36 ` [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not usable) with RX580, amdgpu, dc=1 (of course), regression - [bisected] bugzilla-daemon
2018-10-26 8:06 ` bugzilla-daemon
2018-10-26 12:05 ` bugzilla-daemon
2018-10-26 20:20 ` bugzilla-daemon
2018-10-26 23:29 ` bugzilla-daemon
2018-10-29 11:08 ` bugzilla-daemon
2018-10-29 14:08 ` bugzilla-daemon
2018-10-29 14:56 ` bugzilla-daemon
2018-10-29 17:08 ` bugzilla-daemon
2018-10-30 20:01 ` bugzilla-daemon
2018-11-01 1:42 ` bugzilla-daemon
2018-11-01 1:44 ` bugzilla-daemon
2018-11-01 1:44 ` bugzilla-daemon
2018-11-01 14:32 ` bugzilla-daemon
2018-11-07 22:11 ` bugzilla-daemon
2018-11-07 22:13 ` 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-108096-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).