From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: kexec on panic
Date: Fri, 10 Feb 2017 10:14:02 +0200 [thread overview]
Message-ID: <52a88de81ea3c62bb2be9e222eb85805@nuclearcat.com> (raw)
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?
Thanks!
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: kexec on panic
Date: Fri, 10 Feb 2017 10:14:02 +0200 [thread overview]
Message-ID: <52a88de81ea3c62bb2be9e222eb85805@nuclearcat.com> (raw)
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?
Thanks!
next reply other threads:[~2017-02-10 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 8:14 Denys Fedoryshchenko [this message]
2017-02-10 8:14 ` kexec on panic Denys Fedoryshchenko
2017-02-10 15:43 ` Petr Tesarik
2017-02-15 17:29 ` Clif Houck
2017-02-15 21:45 ` Marc Milgram
2017-02-18 7:42 ` Jon Masters
2017-02-18 7:42 ` Jon Masters
2017-02-18 8:09 ` Denys Fedoryshchenko
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=52a88de81ea3c62bb2be9e222eb85805@nuclearcat.com \
--to=nuclearcat@nuclearcat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.