On 08/14/2013 03:40 PM, Joseph Salisbury wrote: > I'd like to perform a bisect to figure out what commit caused this > regression. We need to identify the earliest kernel where the issue > started happening as well as the latest kernel that did not have this > issue. > > Can you test the following kernels and report back? We are looking for > the first kernel version that exhibits this bug: > > v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring > v3.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy > v3.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy > v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/
Tested with 3.11.0-2-generic: works. *however*, I had to take care to manually select the same kernel I was running at hibernation time in the Grub boot menu. This may be what happened last time: a new kernel got installed, then I hibernated my machine and grub picked the new kernel. In Fedora, when you hibernate your system, on the next boot grub skips the menu and automatically boots the same kernel that was used before. Additionally, I feel that the user should be shown an error message when dehibernation failed. I was puzzled when I got a lightdm login screen instead of my old session. -- _ // Bernie Innocenti \X/ http://codewiz.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212266 Title: [LENOVO 4291AK7] hibernate/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
