Created attachment 79702 [details]
Backtrace of crash from gdb
I tested Kerbal Space Program today (after the new 0.20 updated) and it crashes when entering 'Settings' or starting the actual game from the menu.
I've attached a backtrace, and the crash seems to be the same in both cases. Atleast the same function is involved.
I was running mesa from git. Last commit was: 7bfb4bea6562b2e69d0376f15224c3811da42167
Running kernel 3.8.8.
The last version of the game (0.19.1) works without problems.
I can also add that I have a Radeon HD 5670.
Created attachment 80585 [details]
Way to big patch to "fix" this small problem
I was too lazy to fix all pipe_sampler_view_reference so in the meantime I introduced pipe_sampler_view_reference_old.
It's not a fix.
* Similar to pipe_sampler_view_reference() but always set the pointer to
* NULL and pass in an explicit context. Passing an explicit context is a
* work-around for fixing a dangling context pointer problem when textures
* are shared by multiple contexts. XXX fix this someday.
static INLINE void
It does the same thing and I think It might have a same problem.
Created attachment 80588 [details] [review]
Less broken patch
Created attachment 80590 [details]
Not tested yet.
Created attachment 80709 [details] [review]
Need more testing.
*** Bug 65803 has been marked as a duplicate of this bug. ***
Seems I didn't use the correct keywords when searching for duplicates. Anything I can do to help test? (I have HD6850)
Compile mesa, make it usable in a system, run piglit, apply the patch, compile mesa,run KSP to check out if it fixes the problem, run piglit again and report regressions.
That should be good enough. I hope.
I've tested the attached patch, and it fixes the crash in kerbal space program.
I've also run the piglit r600.tests before and after patching, but it seems the results are somewhat mixed. I ran piglit once before patching and a few times afterwards and the results differed each time I ran the tests. One time the test even zombied.
Does this behavior also occurred before patching?
Yeah, I ran the piglit tests multiple times again without the patch applied, and the same result can be observed.
Is someone interested in this patch?
I'd suggest sending it to the mailing list (firstname.lastname@example.org).
Please use git to format the patch and include a description of what the patch does and how it fixes the issue.
I have done that and no one cared.
(In reply to comment #16)
> I have done that and no one cared.
Are you sure it went through? I don't don't see the patch in the archives: http://lists.freedesktop.org/archives/mesa-dev/
(In reply to comment #17)
> (In reply to comment #16)
> > I have done that and no one cared.
> Are you sure it went through? I don't don't see the patch in the archives:
Here it is...
This issue seems to have gone away in the later git versions, without the requirement of the attached patch.
Then I will close the bug.
If there is still a problem please reopen it.