Bug 715 - MGA (CVS snapshot + XF86 4.x): Hard lockups ("[dri] Idle timed out") during heavy texture use, requiring system reset.
Summary: MGA (CVS snapshot + XF86 4.x): Hard lockups ("[dri] Idle timed out") during ...
Status: RESOLVED DUPLICATE of bug 473
Alias: None
Product: DRI
Classification: Unclassified
Component: General (show other bugs)
Version: DRI git
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2004-06-03 06:56 UTC by Chris Metzler
Modified: 2005-10-11 15:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Chris Metzler 2004-06-03 06:56:56 UTC
In heavy activity involving texturing, after a certain time, the
system locks hard.  The mouse cursor moves with the mouse; but
no other input of any sort has any effect (including attempts
to change virtual terminal).  A full system reset is necessary.

Unfortunately, this bug is hard to reproduce in a systematic fashion.
I can guarantee that if, for example,  you spend enough time flying
around close to the ground in FlightGear, the machine will lock up
in this fashion.  But I can't guarantee that "if you do X, Y, and Z
in sequence, it'll lock up."  But while it's not easily reproduced in
a systematic fashion, it is easily reproduced in that it comes up for
me quite frequently (I'm currently running into this several times a
week, and sometimes multiple times a night).

If there are things someone would want me to do to collect more info
in order to run the problem down (e.g. apply a patch to write a bunch
of info to the XF86 log when the idle timeout message below occurs),
I'm happy to do that.

As noted, the system locks hard.  Mouse movement moves the mouse
cursor around; but no other input has any effect, and all screen
updates (other than the mouse cursor) cease.

I've experienced this bug since XF86 4.0; it may have been present in
earlier versions, but I didn't have the G550 before I started using that
version of XFree86.  I hadn't reported it until recently because I was
getting no useful information about the crash; I didn't know whether it
was a problem with applications, the X server, user (X server) modules,
kernel modules, or the app itself.  But with XF86 4.3, when the lockup
occurs, I'm now getting an endless (well, thousands of instances) write

(EE) MGA(0): [dri] Idle timed out, resetting engine...
(EE) MGA(0): [dri] Idle timed out, resetting engine...
(EE) MGA(0): [dri] Idle timed out, resetting engine...
(EE) MGA(0): [dri] Idle timed out, resetting engine...

into XFree86.0.log, until the machine is reset.

DRI CVS Snapshot 20040527 as well as XFree86 4.x.

I have a Matrox G550 on a Via KT333-based board (Asus A7V333).
I run Linux kernel 2.4.23.  I do not use the proprietary/optional
mga_hal driver from Matrox.

- For 2D use, everything's fine.  For simple 3D use (e.g. glxgears,
rendering within blender, or the typical OpenGL-based screensaver),
it's fine.  This problem only occurs with intensive 3D use that
involves a lot of texture writing/mapping/shading/etc.

- This bug was previously reported on the DRI bugtracker at
Sourceforge.  However, Ian Romanick informed me that the BTS
there is deprecated, and that this was the one to use as soon as
it was up.

- This bug may be the same as


except I don't get it immediately upon starting up an app,
and I don't get it with simple OpenGL apps like glxgears.

- This bug may also be related to this bug reported by
Ian Romanick:


I simly don't know enough to say.

Please let me know if there's anything I can do to provide
more information or test anything.
Comment 1 Chris Bruner 2004-11-23 22:27:33 UTC
http://forums.gentoo.org/viewtopic.php?t=198023&highlight=lockups may provide 
more clues. This bug appears to be very hard to reproduce and happens with a 
wide variety of hardware.  
On my machine I'm using gcc 3.4 which may be the problem, and xorg ati drivers. 
Comment 2 Ian Romanick 2005-10-12 08:45:24 UTC
Closing as a duplicate of bug #473.  After reading the comments and looking at
all the attached log files, I strongly suspect that both bugs have the same root

*** This bug has been marked as a duplicate of 473 ***

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.