From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85647] Random radeonsi crashes with mesa 10.3.x
Date: Tue, 18 Nov 2014 08:15:41 +0000 [thread overview]
Message-ID: <bug-85647-502-j8gGT8OBpj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85647-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85647
--- Comment #35 from Hannu <hannu.tmp@pp.inet.fi> ---
(In reply to Michel Dänzer from comment #34)
> (In reply to Hannu from comment #33)
> > I'll try "fix that only disables DMA if 1D tiling is involved" from bug 83500,
>
> You can save the time for that, given that it didn't fully fix the problem
> for the reporter of that bug.
>
>
> > if that doesn't work I give up and use the fix I did in comment 26.
>
> Why don't you just use the fix I pushed to resolve this report? :) I
> deliberately didn't keep the second si_dma_copy_buffer path enabled because
> I know (from experience trying to port the DMA code to CIK) that it doesn't
> properly check for all cases it can't handle. I don't think that path is
> very relevant in practice anyway.
OK, I'll stop testing for now.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2123 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-11-18 8:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 12:45 [Bug 85647] New: Random radeonsi crashes with mesa 10.3.x bugzilla-daemon
2014-10-30 13:51 ` [Bug 85647] " bugzilla-daemon
2014-10-30 14:41 ` bugzilla-daemon
2014-10-30 15:09 ` bugzilla-daemon
2014-10-30 15:10 ` bugzilla-daemon
2014-10-30 15:18 ` bugzilla-daemon
2014-10-30 15:48 ` bugzilla-daemon
2014-10-31 2:24 ` bugzilla-daemon
2014-10-31 2:31 ` bugzilla-daemon
2014-10-31 5:44 ` bugzilla-daemon
2014-11-01 18:26 ` bugzilla-daemon
2014-11-03 21:19 ` bugzilla-daemon
2014-11-03 21:24 ` bugzilla-daemon
2014-11-05 9:03 ` bugzilla-daemon
2014-11-05 9:59 ` bugzilla-daemon
2014-11-06 17:29 ` bugzilla-daemon
2014-11-08 12:09 ` bugzilla-daemon
2014-11-08 15:37 ` bugzilla-daemon
2014-11-10 13:22 ` bugzilla-daemon
2014-11-11 7:13 ` bugzilla-daemon
2014-11-11 8:54 ` bugzilla-daemon
2014-11-11 12:53 ` bugzilla-daemon
2014-11-11 13:20 ` bugzilla-daemon
2014-11-11 21:08 ` bugzilla-daemon
2014-11-12 9:17 ` bugzilla-daemon
2014-11-13 5:01 ` bugzilla-daemon
2014-11-13 11:49 ` bugzilla-daemon
2014-11-15 10:13 ` bugzilla-daemon
2014-11-17 7:25 ` bugzilla-daemon
2014-11-17 9:52 ` bugzilla-daemon
2014-11-17 14:58 ` bugzilla-daemon
2014-11-17 16:52 ` bugzilla-daemon
2014-11-18 7:05 ` bugzilla-daemon
2014-11-18 7:52 ` bugzilla-daemon
2014-11-18 8:03 ` bugzilla-daemon
2014-11-18 8:15 ` bugzilla-daemon [this message]
2014-11-18 8:39 ` bugzilla-daemon
2014-11-18 11:20 ` bugzilla-daemon
2014-12-08 7:32 ` bugzilla-daemon
2014-12-09 6:24 ` bugzilla-daemon
2014-12-09 7:05 ` bugzilla-daemon
2014-12-09 7:22 ` bugzilla-daemon
2015-01-08 11:31 ` bugzilla-daemon
2015-03-04 7:29 ` bugzilla-daemon
2015-03-04 7:31 ` 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-85647-502-j8gGT8OBpj@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