From: Himanshu Madhani <himanshu.madhani@qlogic.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Capturing crash with 4.6.0 and above kernel does not work
Date: Wed, 24 Aug 2016 16:38:56 +0000 [thread overview]
Message-ID: <0140312F-1DD9-4CC7-9484-32F8570B5089@qlogic.com> (raw)
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
next reply other threads:[~2016-08-24 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 16:38 Himanshu Madhani [this message]
2016-08-25 8:10 ` Michal Hocko
2016-08-25 17:45 ` Himanshu Madhani
2016-08-26 5:03 ` Dave Young
2016-08-26 16:48 ` Himanshu Madhani
2016-08-26 5:39 ` Baoquan He
2016-08-26 16:47 ` Himanshu Madhani
2016-08-27 0:15 ` Baoquan He
2016-08-30 5:44 ` Himanshu Madhani
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=0140312F-1DD9-4CC7-9484-32F8570B5089@qlogic.com \
--to=himanshu.madhani@qlogic.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®