From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not usable) with RX580, amdgpu, dc=1 (of course), regression - [bisected]
Date: Fri, 26 Oct 2018 12:05:56 +0000 [thread overview]
Message-ID: <bug-108096-502-1OKKUDP4IN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108096-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2024 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #15 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
(In reply to Michel Dänzer from comment #14)
> Which Git commit of Mesa are you using? Any local patches on top?
Every, since ever, as always (even, since _before_ Aug 22, 2018) ...;-)
But kidding aside, _currently_
#0ff1ccca25
(with merged branch from Marek for testing purposes)
04ba4eae68 (HEAD -> ext_gpu_shader4) Merge branch 'ext_gpu_shader4' of
git://people.freedesktop.org/~mareko/mesa into ext_gpu_shader4
0ff1ccca25 (origin/master, origin/HEAD, master) radv: call
nir_link_xfb_varyings()
Has it something to do with the DRM version?
DRM 3.26.0 (4.18) vs. DRM 3.27.0 (4.19)?
[-]
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
index 06aede1..529500c 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
@@ -69,9 +69,10 @@
* - 3.24.0 - Add high priority compute support for gfx9
* - 3.25.0 - Add support for sensor query info (stable pstate sclk/mclk).
* - 3.26.0 - GFX9: Process AMDGPU_IB_FLAG_TC_WB_NOT_INVALIDATE.
+ * - 3.27.0 - Add new chunk to to AMDGPU_CS to enable BO_LIST creation.
*/
#define KMS_DRIVER_MAJOR 3
-#define KMS_DRIVER_MINOR 26
+#define KMS_DRIVER_MINOR 27
#define KMS_DRIVER_PATCHLEVEL 0
[-]
But this commit is _in_ since
author Andrey Grodzovsky <andrey.grodzovsky@amd.com> 2018-07-06 14:16:54
-0400
committer Alex Deucher <alexander.deucher@amd.com> 2018-07-16
15:29:47 -0500
and I had it running (on stable and amd-staging-drm-next, daily), even with AMD
testing code (Huang Rui ray.huang at amd.com), Aug 16, 2018.
https://lists.freedesktop.org/archives/amd-gfx/2018-August/025411.html
Do you need more logs?
With which kernel parameter?
System _is_ running, but with unusable gfx/dri screen.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3251 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 prev parent reply other threads:[~2018-10-26 12:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 3:38 [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:40 ` 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 [this message]
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-1OKKUDP4IN@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