Date: Tue, 26 Mar 2019 11:54:17 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Peter Jeremy <peter@rulingia.com> Cc: Shivaprashanth H <shivprashanth.h@globaledgesoft.com>, "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org> Subject: Re: loading the coredump file to memory Message-ID: <CAJ-Vmo=PiEn4rNC9WgQGxmtGyAFCcmVjEei-UmuqNuFF5Ute0g@mail.gmail.com> In-Reply-To: <20190326184433.GE72367@server.rulingia.com> References: <SL2PR03MB4058CB23CDB22EDB92486B6F9A5F0@SL2PR03MB4058.apcprd03.prod.outlook.com> <20190326184433.GE72367@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
... is someone trying to make suspend-to-disk work? :) -adrian On Tue, 26 Mar 2019 at 11:45, Peter Jeremy <peter@rulingia.com> wrote: > On 2019-Mar-26 13:16:40 +0000, Shivaprashanth H < > shivprashanth.h@globaledgesoft.com> wrote: > >using sysctl debug.kdb.panic=1 command, panic can be simulated which > results in system reboot and writing of system context(ram snapshot?) to a > file vmcore.x in /var/crash > > > >my question is, will it be possible to load this file back into memory? > > If you mean, can you take the crashdump and turn it back into a running > system, > no that's not possible. Maybe if you explain what your objective is, we > might > be able to make suggestions. > > (And, I'm not sure how this relates to ACPI). > -- > Peter Jeremy >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=PiEn4rNC9WgQGxmtGyAFCcmVjEei-UmuqNuFF5Ute0g>