I've been looking between 2.6.39 and 3.0-rc1 now, but nothing stands out as the change that potentially fixes this issue. The next step is to perform a bisection to try and locate the commit that fixes the problem. I'll provide a series of kernels, please test each one and let me know whether or not it contains the issue.
Everyone who is able to test please do so, as it can't hurt to have multiple people testing.
Yes, 2.6.39-1 is after 2.6.39-rc7.
I've been looking between 2.6.39 and 3.0-rc1 now, but nothing stands out as the change that potentially fixes this issue. The next step is to perform a bisection to try and locate the commit that fixes the problem. I'll provide a series of kernels, please test each one and let me know whether or not it contains the issue.
Everyone who is able to test please do so, as it can't hurt to have multiple people testing.
Bisect build #000 is available at:
http:// people. canonical. com/~sforshee/ lp727620/ bisect/
Bisect log so far (note that since we're hunting for the commit that fixes the problem, the meanings of 'good' and 'bad' are swapped in the log).
# bad: [55922c9d1b84b8 9cb946c777fddcc b3247e7df2c] Linux 3.0-rc1 3549928dfd9f3e8 f26aa36a8cf] Linux 2.6.39
# good: [61c4f2c81c61f7
git bisect start 'v3.0-rc1' 'v2.6.39'