From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758811AbcHYIKx (ORCPT ); Thu, 25 Aug 2016 04:10:53 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:37578 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758203AbcHYIKw (ORCPT ); Thu, 25 Aug 2016 04:10:52 -0400 Date: Thu, 25 Aug 2016 10:10:49 +0200 From: Michal Hocko To: Himanshu Madhani Cc: linux-kernel , Dave Young , Baoquan He , Vivek Goyal , kexec@lists.infradead.org Subject: Re: Capturing crash with 4.6.0 and above kernel does not work Message-ID: <20160825081049.GA4235@dhcp22.suse.cz> References: <0140312F-1DD9-4CC7-9484-32F8570B5089@qlogic.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0140312F-1DD9-4CC7-9484-32F8570B5089@qlogic.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [Let's add kdump people] On Wed 24-08-16 16:38:56, Himanshu Madhani wrote: > Hello list, > > I am wondering if anybody has issue capturing crash dump with the 4.6.0 and above kenrel. > > I have a system, when booted in 4.5.7 kernel is able to capture crash dump. > However, when I boot this system in 4.6.4 and 4.7.2 kernel, crash dump is not > able to capture any crash. > > I am still facing same issue with 4.8.0-rc2+ kernel and from the error at the command prompt, > it seems like kexec is ignoring “crashkenrel” parameter. > > I added below information in https://bugzilla.kernel.org/show_bug.cgi?id=119291. > > # uname -r > 4.8.0-rc2+ > > # cat /proc/cmdline > ro root=/dev/mapper/vg_dut4110-lv_root rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=512M rd_LVM_LV=vg_dut4110/lv_swap rd_LVM_LV=vg_dut4110/lv_root rd_NO_DM rhgb quiet > > # service kdump status > Kdump is not operational > > # service kdump start > Memory for crashkernel is not reserved > Please reserve memory by passing "crashkernel=X@Y" parameter to the kernel > Starting kdump: [FAILED] It smells like the crash kernel reservation has failed. Could you provide the full kernel log? > message file confirms that kexec was not able to start the service > > Aug 15 10:41:17 dut4110 kdump: kexec: failed to load kdump kernel > Aug 15 10:41:17 dut4110 kdump: failed to start up > > Note, that same option is able to load kdump service for 4.5.7 kernel. > > I can provide any details needed to help resolve this issue. > > Thanks, > - Himanshu > -- Michal Hocko SUSE Labs