As it turns out, I have found the crux of the problem now and also worked around it. As I reviewed the dmesg output from my previous posts, I realized that hibernation image creation was working fine, as was restoring it when the kernel knew where to look.
To cut a long story short, when I helped the kernel find the hibernation image by adding the "resume=" command line parameter, it worked like a charm. I successfully did "sudo pm-hibernate" with both kernel versions 3.13.0-24-generic and 3.15.0-031500rc2-generic.
I am attaching the dmesg output for 3.13.0-24-generic. Please let me know how to proceed with this bug report.
Hi Christopher,
Thanks a lot for help and support.
As it turns out, I have found the crux of the problem now and also worked around it. As I reviewed the dmesg output from my previous posts, I realized that hibernation image creation was working fine, as was restoring it when the kernel knew where to look.
To cut a long story short, when I helped the kernel find the hibernation image by adding the "resume=" command line parameter, it worked like a charm. I successfully did "sudo pm-hibernate" with both kernel versions 3.13.0-24-generic and 3.15.0- 031500rc2- generic.
I am attaching the dmesg output for 3.13.0-24-generic. Please let me know how to proceed with this bug report.
Thanks,
Kunjesh.