Messages in this thread | | | Date | Fri, 19 Sep 2003 22:27:40 +1200 | From | Nigel Cunningham <> | Subject | Re: Resuming from software suspend |
| |
Provided you're not making the data of the filesystem inconsistent with the state that the suspended image is expecting to see, you won't get any corruption. As to beginning a resume without rebooting, whether it would work would depend upon the size of the image, the amount of memory used when you start the resume and the degree of overlap between the two sets of memory.
Regards,
Nigel
On Fri, 2003-09-19 at 22:15, Måns Rullgård wrote: > Nigel Cunningham <ncunningham@clear.net.nz> writes: > > > If your filesystems were mounted readonly and the boot won't mount them > > writable, you should be fine with no special precautions. Last time I > > looked at 2.6 code, it didn't fix the suspend header when you use > > noresume. If that's still true, you should be able to boot with the > > noresume option, and then later normally. > > What I want to do is boot, do some things, and then resume the > suspended state without rebooting between. Is that possible? I don't > see any reason why it should be impossible to do, even if it's not > currently supported. -- Nigel Cunningham 495 St Georges Road South, Hastings 4201, New Zealand
You see, at just the right time, when we were still powerless, Christ died for the ungodly. -- Romans 5:6, NIV.
- 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/
| |