From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90741] Radeon: System pauses on TAHITI
Date: Mon, 02 Mar 2015 10:03:56 +0000 [thread overview]
Message-ID: <bug-90741-2300-QrYS4CRZHG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-90741-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=90741
--- Comment #48 from Maarten Lankhorst <bugs@mblankhorst.nl> ---
Created attachment 168571
--> https://bugzilla.kernel.org/attachment.cgi?id=168571&action=edit
flush hdp harder
No idea if this does anything, adding a bunch of flushes instead of doing a
sleep.. pauses still occur?
If not can you check if it still works with only the chunk in
radeon_fence_enable_signalling?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-02 10:03 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 0:35 [Bug 90741] New: Radeon: System pauses on TAHITI bugzilla-daemon
2015-01-04 14:07 ` [Bug 90741] " bugzilla-daemon
2015-01-05 9:01 ` bugzilla-daemon
2015-01-05 9:14 ` bugzilla-daemon
2015-01-05 19:15 ` bugzilla-daemon
2015-01-06 2:17 ` bugzilla-daemon
2015-01-06 11:14 ` bugzilla-daemon
2015-01-06 12:55 ` bugzilla-daemon
2015-01-06 13:47 ` bugzilla-daemon
2015-01-06 13:50 ` bugzilla-daemon
2015-01-06 14:23 ` bugzilla-daemon
2015-01-20 8:34 ` bugzilla-daemon
2015-01-20 20:15 ` bugzilla-daemon
2015-01-21 9:24 ` bugzilla-daemon
2015-01-21 9:50 ` bugzilla-daemon
2015-01-21 14:47 ` bugzilla-daemon
2015-01-21 18:02 ` bugzilla-daemon
2015-01-22 19:30 ` bugzilla-daemon
2015-01-22 19:48 ` bugzilla-daemon
2015-01-23 19:19 ` bugzilla-daemon
2015-01-23 22:58 ` bugzilla-daemon
2015-01-24 12:57 ` bugzilla-daemon
2015-01-25 19:55 ` bugzilla-daemon
2015-01-25 20:03 ` bugzilla-daemon
2015-01-25 23:00 ` bugzilla-daemon
2015-01-28 12:21 ` bugzilla-daemon
2015-01-28 12:24 ` bugzilla-daemon
2015-01-28 15:34 ` bugzilla-daemon
2015-01-28 19:43 ` bugzilla-daemon
2015-01-29 12:14 ` bugzilla-daemon
2015-01-29 12:21 ` bugzilla-daemon
2015-01-29 12:35 ` bugzilla-daemon
2015-01-29 13:29 ` bugzilla-daemon
2015-01-29 13:38 ` bugzilla-daemon
2015-02-05 9:10 ` bugzilla-daemon
2015-02-05 9:13 ` bugzilla-daemon
2015-02-12 8:35 ` bugzilla-daemon
2015-02-12 9:47 ` bugzilla-daemon
2015-02-12 9:49 ` bugzilla-daemon
2015-02-12 9:53 ` bugzilla-daemon
2015-02-12 14:35 ` bugzilla-daemon
2015-02-12 18:28 ` bugzilla-daemon
2015-02-23 11:48 ` bugzilla-daemon
2015-03-02 8:29 ` bugzilla-daemon
2015-03-02 9:15 ` bugzilla-daemon
2015-03-02 9:27 ` bugzilla-daemon
2015-03-02 9:46 ` bugzilla-daemon
2015-03-02 9:55 ` bugzilla-daemon
2015-03-02 10:03 ` bugzilla-daemon [this message]
2015-03-02 10:11 ` bugzilla-daemon
2015-03-02 10:19 ` bugzilla-daemon
2015-03-02 10:21 ` bugzilla-daemon
2015-03-02 10:22 ` bugzilla-daemon
2015-03-02 10:41 ` bugzilla-daemon
2015-03-02 10:54 ` bugzilla-daemon
2015-03-02 11:00 ` bugzilla-daemon
2015-03-02 11:04 ` bugzilla-daemon
2015-03-02 11:05 ` bugzilla-daemon
2015-03-02 17:09 ` bugzilla-daemon
2015-03-02 18:46 ` bugzilla-daemon
2015-03-02 18:49 ` bugzilla-daemon
2015-03-02 19:19 ` bugzilla-daemon
2015-03-02 19:24 ` bugzilla-daemon
2015-03-02 20:02 ` bugzilla-daemon
2015-03-02 20:23 ` bugzilla-daemon
2015-03-02 20:27 ` bugzilla-daemon
2015-03-02 20:29 ` bugzilla-daemon
2015-03-02 20:33 ` bugzilla-daemon
2015-03-02 20:40 ` bugzilla-daemon
2015-03-02 20:48 ` bugzilla-daemon
2015-03-02 21:07 ` bugzilla-daemon
2015-03-02 22:00 ` bugzilla-daemon
2015-03-02 22:11 ` bugzilla-daemon
2015-03-03 1:44 ` bugzilla-daemon
2015-03-03 1:47 ` bugzilla-daemon
2015-03-03 6:34 ` bugzilla-daemon
2015-03-03 17:59 ` bugzilla-daemon
2015-03-03 18:52 ` bugzilla-daemon
2015-03-03 21:50 ` bugzilla-daemon
2015-03-04 9:21 ` bugzilla-daemon
2017-04-26 13:35 ` 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-90741-2300-QrYS4CRZHG@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.