OK, my next theory is the that scheduler change from CONFIG_FAIR_USER_SCHED to CONFIG_FAIR_CGROUP_SCHED has broken suspend, so I've built a kernel with the original scheduler setting. Please test by loading and running the kernel/lum packages from http://people.ubuntu.com/~rtg/linux-2.6.24-19. For example (if you are running the 64 bit kernel):
OK, my next theory is the that scheduler change from CONFIG_ FAIR_USER_ SCHED to CONFIG_ FAIR_CGROUP_ SCHED has broken suspend, so I've built a kernel with the original scheduler setting. Please test by loading and running the kernel/lum packages from http:// people. ubuntu. com/~rtg/ linux-2. 6.24-19. For example (if you are running the 64 bit kernel):
wget http:// people. ubuntu. com/~rtg/ linux-2. 6.24-19/ linux-image- 2.6.24- 19-generic_ 2.6.24- 19.33_amd64. deb people. ubuntu. com/~rtg/ linux-2. 6.24-19/ linux-ubuntu- modules- 2.6.24- 19-generic_ 2.6.24- 19.26_amd64. deb 2.6.24- 19-generic_ 2.6.24- 19.33_amd64. deb linux-ubuntu- modules- 2.6.24- 19-generic_ 2.6.24- 19.26_amd64. deb
wget http://
sudo dpkg -i linux-image-
sudo reboot