Bug 35838

Summary: Savage2 crashes when running Practice
Product: Mesa Reporter: Kevin DeKorte <kdekorte>
Component: Drivers/Gallium/r600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: idr
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Kevin DeKorte 2011-03-31 08:17:20 UTC 
Install kernel from drm-radeon-testing, libdrm git, mesa git, ddx git as of March 31, 2011

Run Savage2 64 bit
From main screen, click Practice
While screen is loading application will crash with following backtrace

~/Savage2/savage2.bin 
warning: The VAD has been replaced by a hack pending a complete rewrite
EE r600_pipe.c:343 r600_get_param - r600: unknown param 45
EE r600_pipe.c:343 r600_get_param - r600: unknown param 45
*** glibc detected *** /home/kdekorte/Savage2/savage2.bin: free(): invalid pointer: 0x00000000099254d0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3a34476d63]
/usr/lib64/dri/r600_dri.so(+0x123ebd)[0x7f80e94c5ebd]


Using git bisect, isolated crash to the following commit

89d81ab16c05818b290ed735c1343d3abde449bf is the first bad commit
commit 89d81ab16c05818b290ed735c1343d3abde449bf
Author: Ian Romanick <ian.d.romanick@intel.com>
Date:   Tue Jan 25 10:41:20 2011 -0800

    glsl: Calcluate Mesa state slots in front-end instead of back-end
    
    This should be the last bit of infrastructure changes before
    generating GLSL IR for assembly shaders.
    
    This commit leaves some odd code formatting in ir_to_mesa and brw_fs.
    This was done to minimize whitespace changes / reindentation in some
    loops.  The following commit will restore formatting sanity.
    
    Reviewed-by: Eric Anholt <eric@anholt.net>
    Reviewed-by: Chad Versace <chad.versace@intel.com>

:040000 040000 cad3ca6fb2a7b45cd21397a87f940da85102fcba 34a321443a5f0d58a5c15ea9330801c59a28c1f2 M	src
Comment 1 Kevin DeKorte 2011-04-05 18:20:19 UTC 
Appears to be fixed in

874a2c0b7da62f4dd08dedcec221f55b22e40e95
Comment 2 Andreas Boll 2012-09-11 07:35:04 UTC 
(In reply to comment #1)
> Appears to be fixed in
> 
> 874a2c0b7da62f4dd08dedcec221f55b22e40e95

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.