Comment 7 for bug 558927

The basic answer: Nothing is better with the various upstream kernels I tried.

Slightly more details: If KMS isn't active, hibernate/restore appears to work with upstream kernels. If KMS is active, hibernate hangs whether invoked by Gnome GUI or from a text VT with X stopped.

With upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.12-lucid/, KMS doesn't work, so X won't start claiming that there are no DRI devices, and I get a low-resolution text VT. If I "sudo pm-hibernate" here, hibernate and restore work OK.

With upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.3-lucid/, KMS and X work. Hibernate from X using Gnome GUI hangs. Hibernate from a (KMS) text console with X stopped hangs. If I boot with "nomodeset" (X won't start claiming that there are no DRI devices) then hibernate from a (low-resolution) text VT, hibernate and restore works OK.

With upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc5-lucid/, KMS works, but X won't start, claiming that there are no DRI devices. Hibernate from a (KMS) text console hangs. If I boot with "nomodeset" then hibernate from a (low-resolution) text VT, hibernate and restore works OK.

Hopefully I didn't mix any of the above up...