Bug 23798

Summary: [945gm][UXA] openfreespace2 crashes
Product: Mesa Reporter: matej.tyc
Component: Drivers/DRI/i915Assignee: Ian Romanick <idr>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium CC: jaimerave
Version: unspecifiedKeywords: NEEDINFO
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: "full" backtrace from the crash
full backtrace with mesa debug info

Description matej.tyc 2009-09-08 13:36:59 UTC 
Created attachment 29340 [details]
"full" backtrace from the crash

Hello,
the openfreespace2 (http://www.hard-light.net/) crashes right after the initial menu (segfault).
I have compiled it and mesa with debugging info, so I attach a (hopefully useful) backtrace. I am quite convinced that it is the driver's fault since it crashed in a different place before the update :-)
I also have a core file, is it of any use?
Regards,
Matej

Archlinux 64-bit, 945GM

kernel 2.6.30.5
intel-dri 7.5.1
xf86-video-intel 2.8.1
Comment 1 matej.tyc 2009-09-13 12:59:52 UTC 
Created attachment 29491 [details]
full backtrace with mesa debug info

I have added a more useful backtrace
Comment 2 Ian Romanick 2009-09-15 11:05:43 UTC 
One of the most important bits of information is missing:  what Mesa version is this? :)  If it's Mesa master, it seems like this bug may have been fixed by the following commit.  Could you retest?

commit 8ec456c68cc69349c2506ce64047d06c7113780c
Author: Brian Paul <brianp@vmware.com>
Date:   Mon Sep 14 12:40:53 2009 -0600

    intel: fix renderbuffer map/unmap regression
    
    Commit 36dd53a3cded9d003ec418732b7fc93c1476aa9b caused a few regressions
    because the glReadBuffer() buffer wasn't getting mapped when GL_READ_BUFFER
    != GL_DRAW_BUFFER.
Comment 3 Ian Romanick 2009-09-16 23:58:56 UTC 
*** Bug 22807 has been marked as a duplicate of this bug. ***
Comment 4 Eric Anholt 2009-10-19 13:03:48 UTC 
Feedback timeout -- we think this is fixed.

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.