https://bugs.freedesktop.org/show_bug.cgi?id=28402

--- Comment #27 from Lukas Schneiderbauer lukas.schneiderbauer@gmail.com 2010-08-31 09:21:07 PDT --- (In reply to comment #26)

Which repository did you use for bi-secting?

Linus' Tree

I don't know how/if git preserves history across merges in different branches, i.e. if you used linuz's tree, would you see the whole history or only the merge points?

I don't know. I'm not very familiar with git.

Also to me 32b3c2abaf8c61c80a8b02071c73f05252122ffe seems unlikely as the culprit, since it modifies something in the rs600 code, and hence should not have any effect on our r3xx cards.

I completely agree. I will rollback a view versions and try "good"-versions again.

Could you possibly see if the following three (consecutive) commits are in your tree too, and test them?

I'd like, as soon as I find out, how to checkout these specific versions. ;)

What we need is a damn trigger to this bug. Without reproducibility trying to catch the right commit is a pure matter of luck and very frustrating.