From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34313] RV770 lock-up with OpenGL
Date: Sun, 22 May 2011 10:01:32 -0700 (PDT) [thread overview]
Message-ID: <20110522170132.D061913004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-34313-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=34313
--- Comment #21 from Bob Ham <rah@bash.sh> 2011-05-22 10:01:32 PDT ---
(In reply to comment #20)
> Does:
> Option "EnablePageFlip" "False"
> in the device section of your xorg.conf fix the issues?
Yes and no. I believe there are at least three distinct problems causing
lockups. Firstly, this immediate lockup caused by page flipping (it happens
very quickly with GL programs.) Secondly, is a lockup from some other cause
that takes longer to show itself but inevitably does. Lastly is a more serious
lockup that is not detected by the kernel driver and causes a hard lock. This
last lockup is rarer still than the second.
The first immediate lockup seems to be remedied by disabling page flipping.
The second (and I presume third) is still present, however. It only takes 5-15
minutes of playing nexuiz for the second type of lockup to assert itself.
Compare this with 0-60 second for the first, page flipping lockup.
So yes, disabling page flipping solves one lockup but there are still others
that it doesn't solve. I will try to do more testing using warzone 2100
instead of nexuiz to see if I can find the cause of the second lockup.
--
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-22 17:01 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
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 [this message]
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=20110522170132.D061913004F@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).