From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34313] RV770 lock-up with OpenGL
Date: Mon, 16 May 2011 08:07:58 -0700 (PDT) [thread overview]
Message-ID: <20110516150758.6A8EE13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-34313-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=34313
--- Comment #16 from Bob Ham <rah@bash.sh> 2011-05-16 08:07:58 PDT ---
After testing I've discovered that there is no obvious culprit. Reducing the
number of GL features (texture compression, VBOs, GLSL, etc) used by nexuiz
simply extends the amount of time it takes for the GPU to lock up. A lockup
will occur even with all optional GL features turned off, it just takes a long
time. Increasing the number of GL features in use just reduces the time it
takes for the GPU to lock up.
Repeatedly running the simple mesa demos in a cycle will eventually cause the
GPU to lock up. Unfortunately, not always at the same point.
Disabling writeback using 'radeon.no_wb=1' on the kernel command line does not
stop GPU lockups. Temperature is not a factor; the GPU has locked up at 48
degrees while at other times running fine at over 58 degrees for long periods.
There are no such problems while using the proprietary fglrx driver.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-05-16 15:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 23:38 [Bug 34313] New: RV770 lock-up with OpenGL bugzilla-daemon
2011-02-15 23:39 ` [Bug 34313] " bugzilla-daemon
2011-02-15 23:39 ` bugzilla-daemon
2011-02-15 23:40 ` bugzilla-daemon
2011-02-15 23:43 ` bugzilla-daemon
2011-02-16 1:15 ` bugzilla-daemon
2011-02-16 23:57 ` bugzilla-daemon
2011-02-16 23:58 ` bugzilla-daemon
2011-02-16 23:58 ` bugzilla-daemon
2011-02-16 23:59 ` bugzilla-daemon
2011-02-16 23:59 ` bugzilla-daemon
2011-02-21 18:52 ` bugzilla-daemon
2011-02-21 19:02 ` bugzilla-daemon
2011-03-31 18:56 ` bugzilla-daemon
2011-03-31 19:16 ` bugzilla-daemon
2011-04-11 13:00 ` bugzilla-daemon
2011-04-11 13:03 ` bugzilla-daemon
2011-04-25 17:01 ` bugzilla-daemon
2011-05-16 15:07 ` bugzilla-daemon [this message]
2011-05-16 15:18 ` bugzilla-daemon
2011-05-16 22:36 ` bugzilla-daemon
2011-05-22 2:55 ` bugzilla-daemon
2011-05-22 16:09 ` bugzilla-daemon
2011-05-22 17:01 ` bugzilla-daemon
2011-05-27 16:47 ` bugzilla-daemon
2011-05-27 16:50 ` bugzilla-daemon
2011-05-27 23:01 ` bugzilla-daemon
2012-11-02 14:41 ` bugzilla-daemon
2012-11-02 14:47 ` bugzilla-daemon
2019-11-19 8:18 ` 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=20110516150758.6A8EE13004F@annarchy.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).