Summary: | random freeze in ioquake3 like games | ||
---|---|---|---|
Product: | Mesa | Reporter: | Donald Jankins <dj.jankins> |
Component: | Drivers/DRI/r300 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
xorg log when crashed
xorg config file |
Description
Donald Jankins
2010-02-23 04:39:02 UTC
Sounds like a 3D bug. Can you attach your xorg log and config? Created attachment 33519 [details]
xorg log when crashed
Created attachment 33520 [details]
xorg config file
Here it is.
Perhaps I figured out when it happens. When I run VirtualBox virtual machine with accelerated 3D graphics enabled and shutdown it normally (at least 3-4 times), the bug occurs. It happens when I run any game (not only quake3, I tried doomsday engine for example). I will disable any 3D acceleration and try again. Maybe it helps me as a workaround. This is on an eee pc 901, i915, and also with latest git drivers from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ . I downloaded the ubuntu xorg-edgers intel drivers from today (2010-04-23) and proceeded to start compiz and run the phoronix-test-suite benchmark openarena. It crashes somewhere in the first test run. The crash renders the system completely unresponsive. I have to resort to pressing the power button since ctrl-alt-del or the ctrl-alt-sysreq-SEKUB sequences do nothing. > proceeded to start compiz .
Correction no compiz. Compiz messes up openarena's refresh rate for me and results in a black screen which is responsive (ctrl-alt-F1) until the random freeze.
The classic r300 driver has been abandoned long ago. It was replaced by the Gallium driver r300g. If you have issues with r300g please file a new bug report with component Drivers/Gallium/r300 Thanks. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.