Date: Mon, 24 Jan 2005 19:37:34 -0600 From: Ryan Sommers <ryans@gamersimpact.com> To: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= <jonny@jonny.eng.br> Cc: hackers@freebsd.org Subject: Re: Resuming from a crashdump Message-ID: <41F5A2DE.5000306@gamersimpact.com> In-Reply-To: <41F59242.7090900@jonny.eng.br> References: <86pszu639o.fsf@borg.borderworlds.dk> <86brbe6052.fsf@borg.borderworlds.dk> <Pine.BSI.4.58L.0501241423530.27294@vp4.netgate.net> <200501242240.j0OMeIXP043763@apollo.backplane.com> <41F59242.7090900@jonny.eng.br>
next in thread | previous in thread | raw e-mail | index | archive | help
João Carlos Mendes Luís wrote: > Isn't it much easier to simply reload the full memory dump (hibernation > file, not dump device) into RAM and continue from that point? This > should be done by /boot/loader, not by a full kernel, as the memory dump > will also contain the kernel. > > At this point, all you have to do is to restore the hardware state, > which may (or may not) be just the same as recovering from suspend state. Restoring the hardware state requires restoring the state inside each and every hardware device. For certain devices this is trivial. However, I believe for devices with much more complex internal state machines this is way beyond the scope of the loader. Now, that isn't to say the loader couldn't start executing the kernel somewhere other than "the beginning" and instead at a point where the kernel would specifically know it was awoken from hibernation and cleanup/reinitialize any devices. My little knowledge on this subject aside. I'd love to have full suspend/resume functionality. It'd make my life as a mobile freebsd user much much easier. However, I wouldn't want it at the expense of every kernel. It would need to be something completely modular. -- Ryan Sommers ryans@gamersimpact.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41F5A2DE.5000306>