Comment 32 for bug 345710

This sounds a bit stupid but I created even a v3. The reason is that after getting in touch with Huaxu, he told me that the problem does not seem to be in 2.6.30 but he wasn't sure why. So looking a bit closer I realized that in newer kernels, instead of stopping the workqueue in question later, code after this moved to a location above. And this code might cause the queue to get scheduled again (I hope I do not loose everybody here).
So the v3 version takes the two patches from upstream instead of one from upstream and make some other changes. I hope I can get you to try that as well... The kernels are again on my peoples page.