Comment 50 for bug 136836

Just a recap of my experience to help anyone who is trying to figure out whether the problem is fixed or not.

I had a problem which had similar or identical symptoms to the problems other people reported. The problem happened reliably.

I did not try the workaround of passing "msi=0 msix=0".

I did instead upgrade my kernel from the Hardy kernel to Linus's 2.6.25, then to Linus's 2.6.26, then to a pre-release of Linus's 2.6.27. Once I switched to the pre-release of Linus's 2.6.27 the problem went away. Remember, the problem happened reliably, so there is no question that the only thing that I changed was changing my kernel to the 2.6.27-prerelease-from-Linus and there is no question that this change fixed the problem for me.

Then I kept upgrading my kernel to newer git snapshots of Linus's kernel throughout the 2.6.27-prerelease process, and the problem did not recur. The I upgraded my kernel to 2.6.27-final from Linus and the problem did not recur. Then I upgraded my kernel to the 2.6.27.x stable releases from the GregKH Stable Team and the problem did not recur.

So, it could be that the problem I had was different than the problems other people had, which is why other people upgrading to Intrepid with the Ubuntu-2.6.27 kernel didn't fix theirs even though me upgrading to Linus-2.6.27 fixed mine. Or it could be that the problem I had is the same as what other people have, but there is some difference between Ubuntu-2.6.27 and Linus-2.6.27 so that the former doesn't fix the problem but the latter does. Oh, and there is another consideration which is that my kernel config is a custom kernel config of my own choosing, so it could be that applying my kernel config instead of the Ubuntu kernel config to either the Ubuntu-2.6.27 or the Linus-2.6.27 would change whether this bug occurs.

I am very busy with other projects right now, so I am not planning to experiment any more with my system (which now works). Good luck!