From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108625] AMDGPU - Can't even get Xorg to start - Kernel driver hangs with ring buffer timeout on ARM64
Date: Mon, 19 Nov 2018 13:00:31 +0000 [thread overview]
Message-ID: <bug-108625-502-dQ96xUoZ58@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108625-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 890 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108625
--- Comment #15 from Carsten Haitzler <raster@rasterman.com> ---
And lo and behold:
--- ./include/drm/drm_cache.h~ 2018-08-12 21:41:04.000000000 +0100
+++ ./include/drm/drm_cache.h 2018-11-16 11:06:16.976842816 +0000
@@ -48,7 +48,7 @@
#elif defined(CONFIG_MIPS) && defined(CONFIG_CPU_LOONGSON3)
return false;
#else
- return true;
+ return false;
#endif
}
Makes it work. Of course this isn't a brilliant patch, but indeed there is
something up with the way write combined memory is handled on ARM here. but
disabling WC for all ARM DRM devices might be too much of a sledgehammer... I'm
going to look into a less sledge-hammer solution that might make this work more
universally. I'll get back to you on that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1791 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-11-19 13:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 15:59 [Bug 108625] AMDGPU - Can't even get Xorg to start - Kernel driver hangs with ring buffer timeout on ARM64 bugzilla-daemon
2018-11-01 17:55 ` bugzilla-daemon
2018-11-02 12:14 ` bugzilla-daemon
2018-11-02 12:15 ` bugzilla-daemon
2018-11-02 12:15 ` bugzilla-daemon
2018-11-02 12:16 ` bugzilla-daemon
2018-11-02 18:41 ` bugzilla-daemon
2018-11-02 18:41 ` bugzilla-daemon
2018-11-04 13:17 ` bugzilla-daemon
2018-11-04 16:15 ` bugzilla-daemon
2018-11-05 9:08 ` bugzilla-daemon
2018-11-05 15:20 ` bugzilla-daemon
2018-11-05 15:32 ` bugzilla-daemon
2018-11-09 20:32 ` bugzilla-daemon
2018-11-09 20:33 ` bugzilla-daemon
2018-11-19 13:00 ` bugzilla-daemon [this message]
2018-11-19 13:39 ` bugzilla-daemon
2019-03-21 20:55 ` 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-108625-502-dQ96xUoZ58@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