From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40904] New: Radeon 9100 (R200): GPU lockup using blender
Date: Thu, 15 Sep 2011 02:05:24 -0700 (PDT) [thread overview]
Message-ID: <bug-40904-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=40904
Summary: Radeon 9100 (R200): GPU lockup using blender
Product: Mesa
Version: 7.11
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r200
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: froncor@gmail.com
Created an attachment (id=51230)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51230)
dmesg with GPU lockup error
Blender doesn't work on my system. If I try to move the 3D blender scene with
the mouse the screen freezes, the cursor disappears and the system become
unusable for some seconds. The dmesg reports a "GPU lockup (waiting for
0x00002034 last fence id 0x00002030)" error.
My system configuration:
Linux Slackware 13.37
Kernel 2.6.37.6
libdrm-2.4.26
mesa-7.11
xf86-video-ati-6.14.1
ATI Radeon 9100 (R200) AGP Video card
Steps to reproduce:
1. Start Blender 2.59:
$ blender
2. On the default scene with the cube, hold down the mouse wheel (middle mouse
button) and move the scene
3. A GPU lockup occurs quite immediately and the screen freezes.
The bug is very easy to reproduce on my system.
Most of the time after few seconds I can use the system again (sometimes I have
to reset the system), but blender is unusable.
The same happens using blender 2.58a, 2.56, ...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
reply other threads:[~2011-09-15 9:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-40904-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