Comment 3 for bug 793437

I installed the 2.6.38-02063808.201106040910_amd64 mainline kernel following instructions from https://wiki.ubuntu.com/Kernel/MainlineBuilds/, and found that the bug persists there as well. Following that, I performed a manual binary-ish search between the newest kernel known to work and the oldest kernel known to have this behavior.

v2.6.38.8-natty (2.6.38-02063808.201106040910) fails
v2.6.37.1-natty (2.6.37-02063701.201102181135) fails
v2.6.36.1-natty (2.6.36-02063601.201011231330) fails
v2.6.35-maverick (2.6.35-020635) succeeds

So I would be inclined to start looking at changes that were made between the 2.6.35 kernel and the 2.6.36 kernel, except for one thing: the 2.6.36-* and later mainline kernels were configured with natty in mind, while the 2.6.35-* kernels were configured with maverick in mind. I suspect that the change in configuration is more likely to blame for my problems than a change in the kernel itself.

Is there a way I can apply the maverick configuration to the 2.6.36 kernel or the natty configuration to the 2.6.35 kernel to test this?