Bug 14113 - intel driver 965GM random crash
Summary: intel driver 965GM random crash
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-17 06:53 UTC by Vianney Lecroart
Modified: 2017-07-24 23:11 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vianney Lecroart 2008-01-17 06:53:17 UTC
OS: Ubuntu 7.10
Computer: MacBook 3.1 (santa rosa) with intel X3100

Xorg -version

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8)
Current Operating System: Linux cahantamac 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
Build Date: 29 September 2007
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present

I have some random crash on my opengl application and the callstack always go to the dri intel driver.

When trying glxgears with valgrind (latest stable version), It generates some invalid read error.

I also have these warning when running my application with valgrind

The invalid read always occurs in a realloc call:

==9966== Invalid read of size 1
==9966==    at 0x4024BAF: memcpy (mc_replace_strmem.c:402)
==9966==    by 0x48128F2: _mesa_realloc (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x47D2778: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47D45E0: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47D5ECE: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47CBAF4: brw_validate_state (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x47C014C: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47C041A: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47C0860: brw_draw_prims (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x485A723: vbo_save_playback_vertex_list (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x47F6D05: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47F9AD6: _mesa_CallList (in /usr/lib/dri/i965_dri.so)
==9966==  Address 0x9d1e5ab is 3 bytes after a block of size 768 alloc'd
==9966==    at 0x4022AB8: malloc (vg_replace_malloc.c:207)
==9966==    by 0x47D328B: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47D5ECE: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47CBAF4: brw_validate_state (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x47C014C: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47C041A: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47C0860: brw_draw_prims (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x485A723: vbo_save_playback_vertex_list (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x47F6D05: (within /usr/lib/dri/i965_dri.so)
==9966==    by 0x47F9AD6: _mesa_CallList (in /usr/lib/dri/i965_dri.so)
==9966==    by 0x8049C2A: (within /usr/bin/glxgears)
==9966==    by 0x804A6C1: (within /usr/bin/glxgears)
Comment 1 Vianney Lecroart 2008-01-17 07:31:22 UTC
glxinfo: Mesa DRI Intel(R) 965GM 4.1.3002 x86/MMX/SSE2


When it crashs, there is the callstack in debug mode:

Program terminated with signal 11, Segmentation fault.
#0  0xb7a6ccbc in memcpy () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0  0xb7a6ccbc in memcpy () from /lib/tls/i686/cmov/libc.so.6
#1  0xb76448f3 in _mesa_realloc () from /usr/lib/dri/i965_dri.so
#2  0xb7604779 in ?? () from /usr/lib/dri/i965_dri.so
#3  0xad4f8b58 in ?? ()
#4  0x00000600 in ?? ()
#5  0x00000600 in ?? ()
#6  0xbfdb7648 in ?? ()
#7  0xb7604307 in ?? () from /usr/lib/dri/i965_dri.so
#8  0x00000001 in ?? ()
#9  0x00d10025 in ?? ()
#10 0x00d10015 in ?? ()
#11 0x00000007 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Comment 2 Vianney Lecroart 2008-01-17 07:35:35 UTC
When I run my application under gdb and the crash happen, it completly freeze gdb in an infinite loop where the application takes 100% cpu

I need to kill -9 gdb to release it
Comment 3 Matt Turner 2010-12-02 20:09:41 UTC
Closing due to inactivity. Reopen if this is still a problem. (You probably didn't get any feedback because you filed it in the wrong section.)


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.