Comment 13 for bug 754711

That's really strange that you can't switch vts. We may be looking at more than one bug here. Does the same thing happen if you run 'sudo chvt 1' in a console?

Are the meminfo and vmalloc dumps from a boot with xforcevesa nomodeset? Because it really isn't using much of the vmalloc area, so I'd be surprised to see the vmap failures from the original "won't suspend" problem in that situation.

It might be best to try to attack the various issues one at a time. Starting with the vmalloc problem, I guess the first thing is for you to tell me whether the meminfo/vmalloc information you just supplied is from a "xforcevesa nomodeset" or not. If it is, I'd be interested to see the same information with the default kernel command-line.

The next step is probably to test the 2.6.38.3 mainline build since that's closest to natty's kernel and will tell us which direction we need to start looking to track down the regression. You can grab this build at:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38.3-natty/