From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31530] New: r600g: GPU hangs and segfaults with piglit (Regression)
Date: Wed, 10 Nov 2010 11:16:22 -0800 (PST) [thread overview]
Message-ID: <bug-31530-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31530
Summary: r600g: GPU hangs and segfaults with piglit
(Regression)
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: monraaf@gmail.com
Created an attachment (id=40180)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40180)
part of backtrace of fbo-blit-d24s8
With latest git master I see a lot of piglit tests segfault and also some more
GPU hangs. e.g. fbo-blit-d24s8 segfaults and fbo-readpixels now hangs the GPU.
git bisect says:
63c3e3a3dc73f8a72e0d08ac4453df57bccdfdb9 is the first bad commit
commit 63c3e3a3dc73f8a72e0d08ac4453df57bccdfdb9
Author: Keith Whitwell <keithw@vmware.com>
Date: Tue Nov 9 20:08:45 2010 +0000
r600: fix my pessimism about PIPE_TRANSFER_x flags
For some reason I though we needed the _DISCARD flag to avoid
readbacks, which isn't true at all. Now write operations should
pipeline properly, gives a good speedup to demos/tunnel.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-11-10 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 19:16 bugzilla-daemon [this message]
2010-11-10 22:59 ` [Bug 31530] r600g: GPU hangs and segfaults with piglit (Regression) 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-31530-502@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 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.