Comment 47 for bug 1158689

OK, finally I have some more encouraging news:

It now looks like the issue indeed started much earlier than initially thought, namely already between the 3.4 and 3.5 kernel series!!!

Results from my testing with stock kernels obtained from kernel.org (I've never ever before compiled so many kernels in such a short period of time...):

* 3.4.5 -> NO ISSUE
* 3.4.74 -> NO ISSUE
* 3.5.1 -> ISSUE SEEN
* 3.5.5 -> ISSUE SEEN
* all later versions (3.6 onwards) -> ISSUE SEEN.

So please advise now what next steps I should undertake to track it down more closely:

What new commits have happened between the 3.4 and 3.5 series, and did one of them possibly affect so-called "fencing" on NV86/NV50 chips?

(And - in order to learn some more git - how can I find out the associated commits using git command-line, such that I can produce the respective kernel tarballs for testing out of git?)

Many thanks in advance for your feedback! :-)

Andreas