Bug 34279 - [r300g] SIGFPE src/gallium/drivers/r300/r300_state.c:1514
Summary: [r300g] SIGFPE src/gallium/drivers/r300/r300_state.c:1514
Status: CLOSED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r300 (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-14 16:14 UTC by Vinson Lee
Modified: 2011-02-14 17:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Vinson Lee 2011-02-14 16:14:05 UTC
mesa: 20112cca262c926de887dff7d7f108b046ea781a (master)

chipset: RV530 71C5 (ATI Radeon X1600)
system architecture: i686
libdrm-dev: 2.4.21-1ubuntu2.1
kernel version: 2.6.35-22-generic
Linux distribution: Ubuntu 10.10 i386
Machine model: iMac4,1

Run piglit fdo10370 test.

$ ./bin/fdo10370
Floating point exception (core dumped)
Program terminated with signal 8, Arithmetic exception.
#0  0x0104f1d5 in r300_set_index_buffer (pipe=0x8c24758, ib=0xbfe692c0) at src/gallium/drivers/r300/r300_state.c:1514
1514	    assert(ib->offset % ib->index_size == 0);

(gdb) bt
#0  0x0104f1d5 in r300_set_index_buffer (pipe=0x8c24758, ib=0xbfe692c0) at src/gallium/drivers/r300/r300_state.c:1514
#1  0x01832475 in st_draw_vbo (ctx=0x8c4edc8, arrays=0x8c8f478, prims=0x8c8ddcc, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', 
    min_index=0, max_index=3) at src/mesa/state_tracker/st_draw.c:688
#2  0x018bbd7c in vbo_exec_vtx_flush (exec=0x8c8dc58, unmap=1 '\001') at src/mesa/vbo/vbo_exec_draw.c:383
#3  0x018b79f8 in vbo_exec_FlushVertices_internal (ctx=0x8c4edc8, unmap=1 '\001') at src/mesa/vbo/vbo_exec_api.c:912
#4  0x018b7a97 in vbo_exec_FlushVertices (ctx=0x8c4edc8, flags=1) at src/mesa/vbo/vbo_exec_api.c:946
#5  0x01866cec in enable_texture (ctx=0x8c4edc8, state=0 '\000', texBit=32) at src/mesa/main/enable.c:247
#6  0x01869039 in _mesa_set_enable (ctx=0x8c4edc8, cap=3553, state=0 '\000') at src/mesa/main/enable.c:609
#7  0x0186a73f in _mesa_Disable (cap=3553) at src/mesa/main/enable.c:1018
#8  0x0177350a in save_Disable (cap=3553) at src/mesa/main/dlist.c:2134
#9  0x08049184 in display () at /home/mks-hackers/piglit/tests/bugs/fdo10370.c:81
#10 0x00ccd820 in fghRedrawWindow (window=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece.
) at freeglut_main.c:210
#11 fghcbDisplayWindow (window=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece.
) at freeglut_main.c:227
#12 0x00cd1660 in fgEnumWindows (enumCallback=0xccd790 <fghcbDisplayWindow>, enumerator=0xbfe69658) at freeglut_structure.c:394
#13 0x00ccdcdb in fghDisplayAll () at freeglut_main.c:249
#14 glutMainLoopEvent () at freeglut_main.c:1450
#15 0x00cce605 in glutMainLoop () at freeglut_main.c:1498
#16 0x08049678 in main (argc=1, argv=0xbfe698d4) at piglit/tests/bugs/fdo10370.c:170
(gdb) frame 0
#0  0x0104f1d5 in r300_set_index_buffer (pipe=0x8c24758, ib=0xbfe692c0) at src/gallium/drivers/r300/r300_state.c:1514
1514	    assert(ib->offset % ib->index_size == 0);
(gdb) print ib->index_size
$1 = 0
Comment 1 Marek Olšák 2011-02-14 16:21:26 UTC
Does commit 4faf11ad6c44902e17c648c28d40e10067f83612 fix it?
Comment 2 Vinson Lee 2011-02-14 16:21:53 UTC
437583ea637ab402a06ae6683af6df35d52512d4 is the first bad commit
commit 437583ea637ab402a06ae6683af6df35d52512d4
Author: Marek Olšák <maraeo@gmail.com>
Date:   Mon Feb 14 10:11:50 2011 +0100

    r300g: cleanup the draw functions

:040000 040000 8791ba88c149c95c4503e412fbbdd6315dca0637 c8d4ba154df1d479fceef06c53b979137be7fb85 M	src
bisect run success
Comment 3 Vinson Lee 2011-02-14 17:22:55 UTC
(In reply to comment #1)
> Does commit 4faf11ad6c44902e17c648c28d40e10067f83612 fix it?

Yes.
Comment 4 Marek Olšák 2011-02-14 17:30:54 UTC
Thank you. I couldn't test it because I was in the middle of something else. Closing..


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.