Messages in this thread |  | | | Date | Fri, 18 Mar 2005 18:54:37 +0100 | | From | Stefan Seyfried <> | | Subject | Re: Suspend-to-disk woes |
| |
Erik Andrén wrote:
> My question is: Why isn't there a check before resuming a > suspend-to-disk image if the system has booted another kernel since the > suspend to prevent this kind of hassle?
Just provide a patch which does this. Hint: this is highly nontrivial. If you boot a kernel, that does not know swsusp (and if it knew, it would have invalidated the suspend image in the swap), or which does not have the necessary information (because of a missing resume= parameter), this kernel cannot do much.
Stefan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |