I've confirmed that this bug occurs in upstream, using the source from http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.10.tar.bz2, and building with config-2.6.32-17-generic-pae from linux-image-2.6.32-17-generic-pae (using "make oldconfig").
I've attached a copy of the config file for that build as config-2.6.32.10u1. (Note that it differs from config-2.6.32-17-generic-pae, because some options differ in the upstream source.) After some experimentation, I found that I could resume successfully if I disabled CONFIG_RELOCATABLE, and set CONFIG_PHYSICAL_START=0x1000000 (instead of CONFIG_PHYSICAL_START=0x100000 -- moving the start address from 1MB to 16MB). I'll attach a copy of the working config file as config-2.6.32.10a10. ** Attachment added: "config that fails to resume" http://launchpadlibrarian.net/42294724/config-2.6.32.10u1 -- resume from hibernate fails on thinkpad t410 https://bugs.launchpad.net/bugs/543477 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
