Comment 57 for bug 1158689

> You really want to be doing a git bisect to do the least amount of work; I
> don't see what you mean by "move forward" but I really hope that you are
> testing the commits in a binary tree style.

Yup. Indeed, I am trying to use a "binary" approach to minimize work, but am not using git bisect, but hope to augment augment cutting the solution tree in half by reading the commit comments and letting my intellect suggest which ones look like more or less likely candidates...

> You can put the tarball-based process in a script so you only need to run a
> single command after moving further in the bisection.

I have indeed already done so (not based on git bisect, but a commit id).

Note that while I'm indeed a complete newbie to git, I am not at all a newbie Linux/Unix shell scripting. In my main job, though, I am a Java architect/developer/support engineer, so I typically am only a "dummy user" of Linux kernels - unless it very rarely happens that something breaks which is really important for me, so I try and see whether I can help... ;-)

I started trying to drive this forward when I became suddenly affected by this issue because it has indeed been introduced into RHEL6 mainline kernels with the most recent RHEL 6.5 kernel update - so I hope that once we're done and you have been able to successfully fix the issue, you can take care of the fix also being ported into subsequent RHEL6 kernels (working at Red Hat, I hope that Ben Skeggs should hopefully be interested enough in doing so...).

Will report back here as soon as I have been able to track things down to a particular commit... :-)

Thanks & BR,
Andreas