On 5 November 2010 17:33, Sebastian Andrzej Siewior <sebast...@breakpoint.cc> wrote: >>The resume procedure is smarter and can resume a suspended image of a >>similar kernel so unless you dist-upgrade or something like that you >>should still be able to resume. > > I just updated from 2.6.32-26 to 2.6.32-27 and run (once again) into > this issue. How did I skip the smart part? >
I guess it's a bug then. 2.6.32 should be resumable if the kernel did not change significantly. I resume various 2.6.36 rc kernels without regard to exact rc revision and without any issues. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
