From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84662] Long pauses with Unreal demo Elemental on R9270X since : Always flush the HDP cache before submitting a CS to the GPU
Date: Tue, 07 Oct 2014 23:38:13 +0000 [thread overview]
Message-ID: <bug-84662-502-WoDNjVciN3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84662-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1004 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84662
--- Comment #22 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Alexandre Demers from comment #21)
> > So currently a bit confused - as reported by Christoph in the other bug, it
> > is possible to have good with vanilla mesa/kernel, but apparently for me the
> > "same" mesa can also be bad.
> >
> > I did try more clean/rebuild cycles including single thread but am currently
> > still bad.
>
> I'm also seeing this behavior while bisecting a different bug on a 7950...
> Probably related...
It seems like current mesa doesn't build/install properly when patched without
being totally clean.
The mesa patch in this bug on an already built tree does provoke -
make[3]: Entering directory
'/mnt/sdb1/Src64/Mesa-git/mesa/src/gallium/drivers/radeon'
CC r600_buffer_common.lo
CCLD libradeon.la
but radeonsi_dri.so is not changed after make install.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2029 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-07 23:38 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 14:50 [Bug 84662] New: Long pauses with Unreal demo Elemental on R9270X since : Always flush the HDP cache before submitting a CS to the GPU bugzilla-daemon
2014-10-04 14:51 ` [Bug 84662] " bugzilla-daemon
2014-10-04 14:57 ` bugzilla-daemon
2014-10-04 14:58 ` bugzilla-daemon
2014-10-05 15:41 ` bugzilla-daemon
2014-10-05 17:31 ` bugzilla-daemon
2014-10-05 17:48 ` bugzilla-daemon
2014-10-05 19:24 ` bugzilla-daemon
2014-10-05 20:15 ` bugzilla-daemon
2014-10-05 20:50 ` bugzilla-daemon
2014-10-05 21:17 ` bugzilla-daemon
2014-10-05 21:29 ` bugzilla-daemon
2014-10-06 7:24 ` bugzilla-daemon
2014-10-06 11:35 ` bugzilla-daemon
2014-10-06 14:33 ` bugzilla-daemon
2014-10-06 16:59 ` bugzilla-daemon
2014-10-06 17:15 ` bugzilla-daemon
2014-10-07 3:47 ` bugzilla-daemon
2014-10-07 9:39 ` bugzilla-daemon
2014-10-07 13:13 ` bugzilla-daemon
2014-10-07 13:17 ` bugzilla-daemon
2014-10-07 14:19 ` bugzilla-daemon
2014-10-07 23:38 ` bugzilla-daemon [this message]
2014-10-07 23:44 ` bugzilla-daemon
2014-10-08 3:04 ` bugzilla-daemon
2014-10-08 8:03 ` bugzilla-daemon
2014-10-08 8:04 ` bugzilla-daemon
2014-10-08 8:06 ` bugzilla-daemon
2014-10-08 9:15 ` bugzilla-daemon
2014-10-08 15:20 ` bugzilla-daemon
2014-10-08 15:22 ` bugzilla-daemon
2014-10-08 15:52 ` bugzilla-daemon
2014-10-08 15:57 ` bugzilla-daemon
2014-10-09 12:54 ` bugzilla-daemon
2014-10-09 19:58 ` bugzilla-daemon
2014-10-09 20:27 ` bugzilla-daemon
2014-10-09 21:18 ` bugzilla-daemon
2014-10-10 1:23 ` bugzilla-daemon
2014-10-10 1:26 ` bugzilla-daemon
2014-10-15 6:54 ` bugzilla-daemon
2014-10-15 9:52 ` bugzilla-daemon
2014-10-15 9:55 ` bugzilla-daemon
2014-10-16 3:12 ` bugzilla-daemon
2014-10-19 20:20 ` bugzilla-daemon
2014-10-19 20:34 ` bugzilla-daemon
2014-10-19 20:40 ` bugzilla-daemon
2014-10-20 7:16 ` bugzilla-daemon
2014-11-03 22:00 ` bugzilla-daemon
2014-11-03 22:03 ` bugzilla-daemon
2014-11-04 0:30 ` bugzilla-daemon
2014-12-22 21:52 ` bugzilla-daemon
2014-12-22 21:54 ` bugzilla-daemon
2014-12-22 23:13 ` bugzilla-daemon
2015-01-08 7:12 ` bugzilla-daemon
2015-01-08 17:30 ` bugzilla-daemon
2015-02-06 2:39 ` bugzilla-daemon
2015-02-06 18:12 ` bugzilla-daemon
2015-11-05 7:45 ` bugzilla-daemon
2015-11-05 9: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-84662-502-WoDNjVciN3@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