[Intel GM965/GL960] OpenGL applications crash whole system

Bug #178451 reported by Rebecca Palmer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
New
Undecided
Unassigned

Bug Description

All my OpenGL applications (blender, flightgear and fgfs-atlas) sometimes crash my entire system.

Dell Latitude D630 (Hardware Information identifies graphics hardware as Intel Mobile GM965/GL960 Integrated Graphics Controller) using its built-in screen at the default 1280x800, Ubuntu 7.10 with default libgl1-mesa-glx and libgl1-mesa-dri.

Symptoms:
-Mouse pointer stops responding
-Colours go funny (both inside and outside the OpenGL application window)
-Screen goes off (blacker than 0,0,0 black), back on (with funny colours still present) and off again
{
-Screen goes on to all black
-"Please wait" cursor appears in centre (but is neither animated nor responsive to mouse) and remains for a few seconds
-Seemingly random colours appear (only) on circular edge of this cursor*
-Screen goes off (blacker than 0,0,0 black), on and off again
}repeats 5 times, then on 6th time stops at *
At this point neither Ctrl+Alt+Backspace nor Ctrl+Alt+F1 does anything; the only way out appears to be an Alt+SysRq+e,u,i,b reboot. No crash report is left in /var/crash.

To reproduce:
-Open Blender (either fullscreen or windowed)
-File > Import > AC3D and choose an .ac file (I have tried several FlightGear .ac files including /usr/share/games/FlightGear/Aircraft/c172p/Models/c172p.ac, they all triggered the crash)
-Spin the view around a bit (press middle mouse button/wheel and drag)
-Click the "Object mode" button and change it to "Edit mode"
-The default cube will be selected (yellow); press X and select Erase All. The cube will disappear but the .ac object will remain
-Render (F12)
-The crash may occur after some seconds; if it doesn't, close the render window and spin the view around a bit more, and it will crash

In FlightGear and Atlas, the crash happens when switching back to these from other applications, and is then fairly common, but I do not yet have a 100% certain way to trigger it in these applications. Note that Atlas depends on libgl1 but appears to use only 2D graphics.

Revision history for this message
Rebecca Palmer (rebecca-palmer) wrote :

Ran Atlas under debugger with output redirected to file, crashed system by switching from Atlas to the debugger terminal and back twice then dragging the map around a bit, got the following: (The normal text output of Atlas is "Please wait while loading databases...done.")

...
...
(no debugging symbols found)
Please wait while loading databases...intelWaitIrq: drmI830IrqWait: -16
done.

Program exited with code 01.
(gdb)

Revision history for this message
BrianGilman (brian-gilman) wrote :

I have the same exact bug, running 7.10 on a Thinkpad R61, with the same chipset and resolution. It happens with Blender and Second Life.

Revision history for this message
BrianGilman (brian-gilman) wrote :

From the kernel log at time of crash -
Dec 27 23:10:54 r61 kernel: [ 2400.292000] [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 1048705 emitted: 1048718

Daemon log -
Dec 27 23:10:55 r61 gdm[5464]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

Revision history for this message
Rebecca Palmer (rebecca-palmer) wrote :

I also get the above log messages, the X one always and the kernel one about half the time (with Blender). The crash can also occur in 1024x768 resolution.

Switching from Atlas to the terminal window it was started from and back twice, then dragging the map around a bit if it hasn't crashed already, seems to also be a reliable way to trigger this bug; I have yet to find one for FlightGear. I don't have Second Life.

Revision history for this message
Rebecca Palmer (rebecca-palmer) wrote :

This may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/120834.

This hardware has also been reported to crash Second Life under Windows: http://softwarecommunity.intel.com/isn/Community/en-US/forums/30244361/ShowThread.aspx The workaround there is to disable object occlusion; can this be done in X?

Attached Xorg log is from a Blender crash; on this particular one, the random colours didn't occur, but the kernel log message did,
Dec 28 21:49:14 **** kernel: [ 6383.072853] [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 250577 emitted: 251224

Revision history for this message
Rebecca Palmer (rebecca-palmer) wrote :

Inserting Option "DRI" "false" into xorg.conf as suggested in #120834 stopped the crashes, but made FlightGear unusably slow (frame rate dropped from 10-11 to 1-2).

Revision history for this message
maor (maors) wrote :

this bug is indeed a duplicate of bug 12083 see the new bug description i created for details

Revision history for this message
Michele Bini (michele-bini) wrote :

The bug seems to be solved with the new version of libgl1-mesa-dri, 7.1-1ubuntu1 from intrepid.

I have intel video hardware and used to get frequent crashes with blender. The fix seems to be independent of xserver-xorg version.

Hope this is helpful

Revision history for this message
Rubin (rubin) wrote :

bug 12083 is about ldap? typo?

Revision history for this message
rickyrockrat (rickyrockrat) wrote :

Please see bug 24505 - there are full instructions for fixing this using intrepid repos.

An update of libgl1 only will cause other errors. You will get these errors:
glxChooseVisual failed
or an RGB error running glxgears.

Revision history for this message
Mike Roberts (m.roberts) wrote :

24505? this bug is about rss feeds. could you please post the fixed report? thanks.

Revision history for this message
darkraven (jasminr) wrote :

THis has NOTHING to do with RSS FEEDS! Which LAME brain came up with that IDEA?

Furthermore.....what is with the attitudes here on this forum that COMMUNITY BUG REPORTS with VALID DATA are being treated as garbage....very unprofessional I might add. I dont care what language you program in. If you dont like your day job... find another.

that out of the way....

This is a INTEL MESA BUG.
The updates, I get from ppa from crack-coders and it updates ok several times a week..better some 3d than no 3d, but the 3d/mesa drivers dont work. Better to go software in this case, which unfortunately requires a reinstall of xorg and ubuntu-desktop packages and on intel systems and SEVERELY DEGRADES performance.

With a nVidia or ATI(mind you both have proprietary 3D acceleraltion packages), software rendering is not an issue, but a performance hit. On notebooks such as these(and my Gateway/Acer LT21) this software mode makes rendering next to impossible. It is the DRI/Hardware acceration modules of MESA/OpenGL that crashes X11.

If you enable the x11 ctrl-alt-backspace keyconfig and kill xorg with 'top' as root you can weasel your way back to a working system on the Gateway/Acer. The keyconfig is under the system gnome panel.

I dont understand...
Why cant everyone use a darm VESA 3 API and just get over it? The specs are out and I have them. Its all the same drawing code anyway....Its (MESA)openGL/DirectX that are different. And YES, I do OS development and have looked at the linux kernel and X11 sources. Not to pleased..

output of lspci is attached.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.