From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932810AbcHXTQ4 (ORCPT ); Wed, 24 Aug 2016 15:16:56 -0400 Received: from mail-bn3nam01on0108.outbound.protection.outlook.com ([104.47.33.108]:53654 "EHLO NAM01-BN3-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755628AbcHXTQw (ORCPT ); Wed, 24 Aug 2016 15:16:52 -0400 X-Greylist: delayed 8361 seconds by postgrey-1.27 at vger.kernel.org; Wed, 24 Aug 2016 15:15:58 EDT From: Himanshu Madhani To: linux-kernel Subject: Capturing crash with 4.6.0 and above kernel does not work Thread-Topic: Capturing crash with 4.6.0 and above kernel does not work Thread-Index: AQHR/iYBAoDFF3sWuEegIgjb2Yzj+Q== Date: Wed, 24 Aug 2016 16:38:56 +0000 Message-ID: <0140312F-1DD9-4CC7-9484-32F8570B5089@qlogic.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/0.0.0.160212 authentication-results: spf=none (sender IP is ) smtp.mailfrom=himanshu.madhani@qlogic.com; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [173.186.134.106] x-ms-office365-filtering-correlation-id: c489cbc3-ca93-4753-aff2-08d3cc3d2473 x-microsoft-exchange-diagnostics: 1;DM5PR11MB1401;20:9WVfhBYknU88OjvimDp/tkvsVEbmL2aQTu4d71dIaNYrW/7FqgjUx1EYUzEInxv9sMpKyEyU3kz8ZuvP4Sa7ir4NNuLG17cOYRhrCtB/igAaW4sTG2ObkHqfIPNnvMA7AwetIIHJt+NCR44mDxFKNUxhl0o5CGE3F/Lxrd7Did0= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM5PR11MB1401; x-ld-processed: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba,ExtAddr x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001);SRVR:DM5PR11MB1401;BCL:0;PCL:0;RULEID:;SRVR:DM5PR11MB1401; x-forefront-prvs: 0044C17179 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(7916002)(199003)(189002)(106116001)(2906002)(305945005)(450100001)(92566002)(122556002)(66066001)(105586002)(3660700001)(8676002)(19580405001)(8936002)(33656002)(19580395003)(81156014)(81166006)(83716003)(87936001)(86362001)(10400500002)(7846002)(82746002)(7736002)(99286002)(83506001)(68736007)(101416001)(50986999)(229853001)(3846002)(586003)(3280700002)(102836003)(6116002)(15975445007)(54356999)(2900100001)(106356001)(189998001)(110136002)(4001350100001)(77096005)(107886002)(5002640100001)(5660300001)(97736004)(36756003)(104396002);DIR:OUT;SFP:1102;SCL:1;SRVR:DM5PR11MB1401;H:DM5PR11MB1404.namprd11.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: MIME-Version: 1.0 X-OriginatorOrg: qlogic.com X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Aug 2016 16:38:56.4233 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1401 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u7OJH1U7032595 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] 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