Ogre3D programs crash with intel driver

Bug #390160 reported by mumismo
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Invalid
High
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

Using Ubuntu 9.04
I have tried the intel driver 2.6.3 that comes with Ubuntu 9.04 and the 2.7.1 that comes from the X-updated PPA

Both gives a segmentation fault with running a Ogre3D program:

#0 0x00007f18588cea8b in ?? () from /usr/lib/dri/i915_dri.so
#1 0x00007f18588e6d8a in ?? () from /usr/lib/dri/i915_dri.so
#2 0x00007f18588dc8ef in _tnl_run_pipeline () from /usr/lib/dri/i915_dri.so
#3 0x00007f18588357c4 in ?? () from /usr/lib/dri/i915_dri.so
#4 0x00007f18588dceb0 in _tnl_draw_prims () from /usr/lib/dri/i915_dri.so
#5 0x00007f18588d588e in ?? () from /usr/lib/dri/i915_dri.so
#6 0x00007f18588025d1 in intel_clear_tris () from /usr/lib/dri/i915_dri.so
#7 0x00007f1858802a67 in ?? () from /usr/lib/dri/i915_dri.so
#8 0x00007f1859103845 in Ogre::GLRenderSystem::clearFrameBuffer (this=0x7f1862e34d28, buffers=<value optimized out>, colour=<value optimized out>, depth=1, stencil=0) at OgreGLRenderSystem.cpp:3099
#9 0x00007f18627695a7 in Ogre::SceneManager::_renderScene (this=0x7f1862e38fb8, camera=0x7f1862edae10, vp=0x7f1862eba470, includeOverlays=<value optimized out>) at OgreSceneManager.cpp:1343
#10 0x00007f186274005c in Ogre::RenderTarget::updateImpl (this=0x7f1862e36998) at OgreRenderTarget.cpp:113
#11 0x00007f186273f96c in Ogre::RenderTarget::update (this=0x12291a8, swap=224) at OgreRenderTarget.cpp:501

This can be reproduced with the ogre3D demos.
I am using a integrated intel G33/G31

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-intel 2:2.7.1-0ubuntu1~xup~1
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.28-11-generic x86_64
UnreportableReason: This is not a genuine Ubuntu package

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02)
     Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02)
     Subsystem: ASUSTeK Computer Inc. Device [1043:8276]

Revision history for this message
mumismo (mumismo) wrote :
Robert Hooker (sarvatt)
affects: xserver-xorg-video-intel (Ubuntu) → mesa (Ubuntu)
Bryce Harrington (bryce)
tags: added: crash
Changed in mesa (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
description: updated
Revision history for this message
Robert Hooker (sarvatt) wrote :

Which Ogre3d demo specifically causes it so I can reproduce and see if it fixed already in newer versions of mesa?

Revision history for this message
Robert Hooker (sarvatt) wrote :

Need more info to reproduce

Changed in mesa (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
mumismo (mumismo) wrote :

I was in fact not using the demos but a program that uses Ogre3D
I made even a very basic program that does almost nothing and it crashed also with the same error. So I assume the same will happen with the more complex demos.
I am using Ogre 1.6 compiled manually (as it is not included in Jaunty) and working perfectly with non-intel drivers.

So maybe is a bug that only can be trigerred by Ogre 1.6?

Revision history for this message
Robert Hooker (sarvatt) wrote :

Can you provide a small example of something that crashes with instructions on how to compile it then? I was asking which demo because of this comment:

This can be reproduced with the ogre3D demos.

Ogre3D 1.6.1 is in karmic so I can test that without compiling the whole thing but I don't have any code and compiling something random might not crash on your system so I wanted to be sure. I am unfamiliar with ogre but have many versions of mesa available to test against which hopefully could help narrow down where the breakage occured. I have seen quite alot of bugs from people having problems with ogre code in the more recent mesa versions on the fdo bugzilla though. Thanks for the help!

Also, this might help find the problem depending where it is --
MESA_DEBUG=1 ./yourdemo
and this will let you see if its an intel specific problem (which it sounds like tried, but listing it just incase)
LIBGL_ALWAYS_SOFTWARE=1 ./yourdemo

Revision history for this message
mumismo (mumismo) wrote :

The program I was using is Gazebo, it can be found here:
https://launchpad.net/~thjc/+archive/ppa

It needs karmin koala.

I will try those environmental variables but now I can not access that computer so it may take some thime.

Revision history for this message
Gennadi (genaios) wrote :

I did my college ex using OGRE 1.4.9 that compiled and worked nicely in Kubuntu 8.10, but since I upgraded to 9.04 the ex gives segfault. I added karmic sources to repo sources and switched to Ogre 1.6.1 but still there is segfault.

I did:

MESA_DEBUG=1
gdb ./mydemo

the output:
===
*-*-* OGRE Initialising
*-*-* Version 1.6.1 (Shoggoth)
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable
Mesa: User error: GL_INVALID_ENUM in GetIntegerv(0x8b4c)
Mesa: User error: GL_INVALID_VALUE in glTexImage2D(internalFormat=0x881b)
Mesa: : 3 similar GL_NO_ERROR errors
Mesa: User error: GL_INVALID_VALUE in glTexImage2D(internalFormat=0x881e)

Program received signal SIGSEGV, Segmentation fault.
0x05be2b7e in ?? () from /usr/lib/dri/i915_dri.so
===

I know this question is asked million times but what else exactly can help to resolve the bug?
I have installed both packages xserver-xorg-video-intel and xserver-xorg-video-intel-dbg, how I can enable debug symbols in gdb?

Revision history for this message
Bryce Harrington (bryce) wrote :

Yes there is more info needed. Please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions.

Changed in mesa (Ubuntu):
status: Incomplete → New
importance: Undecided → High
status: New → Incomplete
Bryce Harrington (bryce)
tags: added: jaunty
Changed in mesa (Ubuntu):
status: Incomplete → Fix Released
status: Fix Released → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in mesa (Ubuntu):
status: Incomplete → Invalid
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.