From: Petr Tesarik <ptesarik@suse.cz>
To: kexec@lists.infradead.org
Subject: Re: kexec on panic
Date: Fri, 10 Feb 2017 16:43:13 +0100 [thread overview]
Message-ID: <20170210164313.5fe98b75@hananiah.suse.cz> (raw)
In-Reply-To: <52a88de81ea3c62bb2be9e222eb85805@nuclearcat.com>
On Fri, 10 Feb 2017 10:14:02 +0200
Denys Fedoryshchenko <nuclearcat@nuclearcat.com> wrote:
> Hello,
>
> After years of using kexec and recent unpleasant experience with modern
> (supposed to be blazing fast to boot) hardware that need 5-10 minutes
> just to pass POST tests,
> one question came up to me:
> Is it possible anyhow to execute regular (not special "panic" one to
> capture crash data) kexec on panic to reduce reboot time?
No. But you can load a specially crafted panic initrd which kexec's
back to the production kernel.
HTH,
Petr T
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2017-02-10 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 8:14 kexec on panic Denys Fedoryshchenko
2017-02-10 15:43 ` Petr Tesarik [this message]
2017-02-15 17:29 ` Clif Houck
2017-02-15 21:45 ` Marc Milgram
2017-02-18 7:42 ` Jon Masters
2017-02-18 8:09 ` Denys Fedoryshchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170210164313.5fe98b75@hananiah.suse.cz \
--to=ptesarik@suse.cz \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox