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 wget http://people.ubuntu.com/~rtg/linux-2.6.24-19/linux-ubuntu-modules-2.6.24-19-generic_2.6.24-19.26_amd64.deb sudo dpkg -i linux-image-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 sudo reboot ** Changed in: linux (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Tim Gardner (timg-tpi) Status: Confirmed => In Progress -- Kernel 2.6.24-17 - broken resume from suspend to RAM https://bugs.launchpad.net/bugs/226279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
