Comment 24 for bug 719446

Alan - Are you able and willing to build your own kernel? Risks are more or less the same as for installing a development kernel, but it takes a bit of time to compile. If you don't want to build a kernel, but are willing to trust me enough to test one I built, I'll post a generic build here later.

If you can't reproduce the bug with the kernel made with these steps, it means we suffer from the same thing.

Maverick git repository:

If so, can you please follow the instructions here for installing the tools: https://help.ubuntu.com/community/Kernel/Compile#Tools you'll need
(steps are the same as for Lucid).

then, in the terminal, make a directory and download repository from git (warning: it's few hundred megabytes), e.g.
mkdir kernel-custom
cd kernel-custom
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git
cd ubuntu-maverick
git checkout -b bug-testing master
git revert 58e15f5029c75b45adbcb25cd76a36d26a6c4297
<<press ctrl+x>>
fakeroot debian/rules clean
AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic

This should build for you two .deb packages for linux-image (which you need to install) and linux-headers (which isn't necessary for this testing) with version number of 2.6.35-28.49 and place them in your kernel-custom directory. After installation, you need to reboot and select the new kernel. You can uninstall it in a standard way (synaptic, dpkg - choose your favourite) after you've done testing.