Also tested linux-image-2.6.32-020632-generic_2.6.32-020632_amd64.deb, which was the closest mainline build I could see to the 2.6.32-22 build lucid is using, and it is also affected, so it looks like this was an upstream bug that got fixed somewhere between 2.6.32 and 2.6.35.
Also tested linux-image- 2.6.32- 020632- generic_ 2.6.32- 020632_ amd64.deb, which was the closest mainline build I could see to the 2.6.32-22 build lucid is using, and it is also affected, so it looks like this was an upstream bug that got fixed somewhere between 2.6.32 and 2.6.35.