From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58354] New: r600g locks up in Unigine Tropics with drm-next
Date: Sun, 16 Dec 2012 06:26:59 +0000 [thread overview]
Message-ID: <bug-58354-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 845 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58354
Priority: medium
Bug ID: 58354
Assignee: dri-devel@lists.freedesktop.org
Summary: r600g locks up in Unigine Tropics with drm-next
Severity: critical
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers@gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Testing with drm-next with latest mesa, ddx and drm, Unigine Tropics locks up
when launching the demo. The problem appears somewhere between
a636a9829175987e74ddd28a2e87ed17ff7adfdc (locks) and
1a1494def7eacbd25db05185aa2e81ef90892460 (OK). I'll pinpoint it tomorrow.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2148 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 reply other threads:[~2012-12-16 6:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 6:26 bugzilla-daemon [this message]
2012-12-16 17:40 ` [Bug 58354] [bisected] r600g locks up in Unigine Tropics with drm-next bugzilla-daemon
2012-12-16 17:45 ` bugzilla-daemon
2012-12-18 6:29 ` [Bug 58354] [bisected] r600g: use DMA engine for VM page table updates on cayman locks in Unigine Tropics bugzilla-daemon
2012-12-23 0:12 ` bugzilla-daemon
2012-12-23 0:58 ` bugzilla-daemon
2012-12-23 2:27 ` bugzilla-daemon
2012-12-23 3:45 ` bugzilla-daemon
2012-12-23 3:46 ` bugzilla-daemon
2012-12-23 4:07 ` bugzilla-daemon
2012-12-23 7:17 ` bugzilla-daemon
2012-12-23 7:23 ` bugzilla-daemon
2013-01-03 22:05 ` bugzilla-daemon
2013-01-03 22:08 ` bugzilla-daemon
2013-01-08 5:58 ` bugzilla-daemon
2013-01-08 13:50 ` bugzilla-daemon
2013-01-09 1:24 ` bugzilla-daemon
2013-01-09 1:27 ` bugzilla-daemon
2013-01-09 13:58 ` bugzilla-daemon
2013-01-10 3:03 ` bugzilla-daemon
2013-01-10 18:04 ` bugzilla-daemon
2013-01-11 0:58 ` bugzilla-daemon
2013-01-11 1:01 ` bugzilla-daemon
2013-01-17 4:07 ` bugzilla-daemon
2013-01-31 20:22 ` bugzilla-daemon
2013-01-31 20:23 ` bugzilla-daemon
2013-02-01 3:58 ` bugzilla-daemon
2013-02-01 13:48 ` bugzilla-daemon
2013-02-23 10:28 ` bugzilla-daemon
2013-02-24 16:28 ` bugzilla-daemon
2014-01-26 11:33 ` 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-58354-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).