From: nborisov <n.borisov.lkml@gmail.com>
To: Steve Wise <swise@opengridcomputing.com>, linux-kernel@vger.kernel.org
Subject: Re: vmcore not getting created on linux-4.7
Date: Fri, 24 Jun 2016 18:06:31 +0300 [thread overview]
Message-ID: <576D4C77.8010404@gmail.com> (raw)
In-Reply-To: <007001d1ce27$17845550$468cfff0$@opengridcomputing.com>
On 24.06.2016 17:45, Steve Wise wrote:
> I've been trying to get crash dumps working on linux-4.7 and haven't succeeded.
> The kdump kernel boots up and appears to be chugging along and then just reboots
> and never creates the vmcore, and fails to create the vmcore-dmesg.txt, though
> I've never seen that working on my nodes. Below is the tail of the boot.
>
> Any ideas?
>
> Saving to the local filesystem UUID=f63753d9-74a5-4db8-9b63-2fc1ba2b5f85
> e2fsck 1.42.12.wc1 (15-Sep-2014)
> /dev/sda2: recovering journal
> Setting free inodes count to 3490861 (was 3490926)
> Setting freeEXT4-fs (sda2): mounted filesystem with ordered data mode. Opts:
> blocks count to 7307269 (was 7307159)
> /dev/sda2: clean, 678867/4169728 files, 9358331/16665600 blocks
> Free memory/Total memory (free %): 45936 / 112096 ( 40.9792 )
> Loading SELINUX policy
> SELinux: Disabled at runtime.
> audit: type=1404 audit(1466753867.960:2): selinux=0 auid=4294967295
> ses=4294967295
> Policy load failed, a relabel will be required on reboot
> Saving vmcore-dmesg.txhpet1: lost 88 rtc interrupts
> t
> Missing the struct log size export
> Saving vmcore-dmesg.txt failed
Regarding the vmcore-dmesg failed, it's likely you are hitting this issue:
http://lists.infradead.org/pipermail/kexec/2012-July/006602.html
Can you try to download an compile the latest kexec tools from
git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
Also what's the content of your /etc/kdump.conf file?
> umount: can't umount /mnt/selinux: Invalid argument
> sd 3:0:0:0: [sdb] Synchronizing SCSI cache
> sd 1:0:0:0: [sda] Synchronizing SCSI cache
> iw_cxgb4:0000:82:00.4: Detach
> reboot: Restarting system
> reboot: machine restart
>
next prev parent reply other threads:[~2016-06-24 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:45 vmcore not getting created on linux-4.7 Steve Wise
2016-06-24 15:06 ` nborisov [this message]
2016-06-24 15:12 ` Steve Wise
2016-06-24 16:37 ` nborisov
2016-06-24 20:19 ` Steve Wise
[not found] ` <014e01d1ce55$aa4ba040$fee2e0c0$@opengridcomputing.com>
2016-07-12 16:13 ` Steve Wise
[not found] ` <00ca01d1dc58$52f00730$f8d01590$@opengridcomputing.com>
2016-07-14 19:19 ` Steve Wise
[not found] ` <00b501d1ce2a$cad610f0$608232d0$@opengridcomputing.com>
2016-06-24 16:37 ` Steve Wise
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=576D4C77.8010404@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/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;
as well as URLs for NNTP newsgroup(s).