Bug 29311

Summary: [r300g]: Compiz crashes when trying to start it with latest mesa master.
Product: DRI Reporter: Scott Moreau <oreaus>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact: Brian Paul <brianp>
Severity: normal    
Priority: medium CC: oreaus
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
compiz crash backtrace none

Description Scott Moreau 2010-07-29 19:19:34 UTC 
Created attachment 37448 [details]
compiz crash backtrace

I bisected and got this:

ba2cc3b8e6ad161181b67fd2575c6bc768584d23 is the first bad commit
commit ba2cc3b8e6ad161181b67fd2575c6bc768584d23
Author: Brian Paul <brianp@vmware.com>
Date:   Thu Jul 29 13:49:21 2010 -0600

    gallium: implement bounds checking for constant buffers
    
    Plumb the constant buffer sizes down into the tgsi interpreter where
    we can do bounds checking.  Optional debug code warns upon out-of-bounds
    reading.  Plus add a few other assertions in the TGSI interpreter.

:040000 040000 7141c078038120e29bab2e275fb935f20731c0ff e2f4d072421db8d000922127dc1f707145b73c61 M	src
Comment 1 Marek Olšák 2010-07-31 22:17:08 UTC 
The thing is the Draw module in Gallium has 3 codepaths:
- Slow interpreter
- SSE code generation (broken)
- LLVM

Guess what, yeah, you use the broken one.

The SSE codepath will most probably be dropped, so I am closing this bug as WONTFIX.

See here:
http://lists.freedesktop.org/archives/mesa-dev/2010-July/001658.html


Now you have two options to fix your setup:
1) Compile Mesa with --enable-gallium-llvm to get the LLVM codepath.
2) Set the environment variable GALLIUM_NOSSE=1 to use the slow interpreter.
Comment 2 Marek Olšák 2010-08-02 08:48:49 UTC 
Fixed by commit aef4500ca4ae9e5bc57560c6f9a32d9ad892975b.
Comment 3 Scott Moreau 2010-08-02 16:49:08 UTC 
(In reply to comment #2)
> Fixed by commit aef4500ca4ae9e5bc57560c6f9a32d9ad892975b.

With latest mesa master the same symptoms persist here.
Comment 4 Scott Moreau 2010-08-02 19:28:43 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > Fixed by commit aef4500ca4ae9e5bc57560c6f9a32d9ad892975b.
> 
> With latest mesa master the same symptoms persist here.

DISREGARD this comment. It is indeed fixed (bug report # mixup)

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.