From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34313] RV770 lock-up with OpenGL
Date: Mon, 11 Apr 2011 06:00:55 -0700 (PDT) [thread overview]
Message-ID: <20110411130055.2A98513004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-34313-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=34313
--- Comment #14 from eric <e.durmin@gmx.net> 2011-04-11 06:00:55 PDT ---
This happens also with r300g + linux-2.6.38.2 + KMS.
I can not always reproduce this GPU lockup, but working (scrolling, opening a
new tab) with big or fullscreen windows seems to trigger this lockup... but not
right after a reboot... so it's difficult to reproduce. Hopefully someone finds
a better way to reproduce this lockup.
When the lockup starts the display disappears (turns to black) for 1 or 2
seconds, then the next will happen:
1) display will return and everything will work again, but the next lockup will
happen soon;
2) display will return but only mouse and keyboard are working, the display
will be frozen except the mouse pointer can move around; I have to exit all
running applications (alt+f4) blindly because the changes will not be seen, go
to console (ctrl+alt+f1) and from there reboot the system.
Switching to console (ctrl+alt+f1) usually works and there the display is
working again, but killing and restarting X will not work, the only way to get
X back is to reboot.
During the lockup the kernel.log will be full of:
kernel: [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
kernel: [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1).
These lines are going for ever until I kill X.
Some lockups looking like mine were solved by turning off 'EnablePageFlip' in
xorg.conf or setting 'agpmode' to -1, 1 or 4 in modprobe.conf or exporting
'LIBGL_ALWAYS_INDIRECT=1'... none of these solutions worked for me. Maybe
turning off KMS works, but without KMS certain things won't work/are different,
so I try to keep using KMS.
--
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-04-11 13:00 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 [this message]
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
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=20110411130055.2A98513004F@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).