I've been running with rc6 enabled for most of the precise development cycle, and I never observed the destkop hangs but have started seeing them recently. I can't say for certain whether or not they started with the 3.2.0-17.26 kernel. But the machine is very much alive when it happens; I can switch to a VT, the apps on my desktop still seem to be running (based on the fact that they still use some CPU), and I can get back to a functioning desktop with 'sudo service lightdm restart'. I'm seeing a strong correlation between these hangs and scrolling in a window, especially when I'm scrolling in chromium.
However, after upgrading this morning I'm not able to reproduce these hangs. I had a couple of pretty reliable ways of reproducing the issue, and neither of them are working. There were some libgl1-mesa updates when I upgraded, which could be related. So I'd suggest getting up-to-date on precise and seeing if the hangs are still reproducible (independently of testing Leann's kernel, so that it's clear what fixed the issue if it does go away).
I've been running with rc6 enabled for most of the precise development cycle, and I never observed the destkop hangs but have started seeing them recently. I can't say for certain whether or not they started with the 3.2.0-17.26 kernel. But the machine is very much alive when it happens; I can switch to a VT, the apps on my desktop still seem to be running (based on the fact that they still use some CPU), and I can get back to a functioning desktop with 'sudo service lightdm restart'. I'm seeing a strong correlation between these hangs and scrolling in a window, especially when I'm scrolling in chromium.
However, after upgrading this morning I'm not able to reproduce these hangs. I had a couple of pretty reliable ways of reproducing the issue, and neither of them are working. There were some libgl1-mesa updates when I upgraded, which could be related. So I'd suggest getting up-to-date on precise and seeing if the hangs are still reproducible (independently of testing Leann's kernel, so that it's clear what fixed the issue if it does go away).