From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752319AbdBJIPJ (ORCPT <rfc822;w@1wt.eu>);
        Fri, 10 Feb 2017 03:15:09 -0500
Received: from nuclearcat.com ([144.76.183.226]:55676 "EHLO nuclearcat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751616AbdBJIO7 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 10 Feb 2017 03:14:59 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 10 Feb 2017 10:14:02 +0200
From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: kexec on panic
Message-ID: <52a88de81ea3c62bb2be9e222eb85805@nuclearcat.com>
User-Agent: Roundcube Webmail/1.2.3
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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!