This fix has regressed (or not been included) in the 2.6.32-33-generic kernel that was just pushed. Any chance of a package respin? Does anything need to happen to make sure it gets included for the next kernel?
This fix has regressed (or not been included) in the 2.6.32-33-generic kernel that was just pushed. Any chance of a package respin? Does anything need to happen to make sure it gets included for the next kernel?