Re: vmcore not getting created on linux-4.7

[nborisov]

On 24.06.2016 18:12, Steve Wise wrote:
> 
>> -----Original Message-----
>> From: nborisov [mailto:n.borisov.lkml@xxxxxxxxx]
>> Sent: Friday, June 24, 2016 10:07 AM
>> To: Steve Wise; linux-kernel@xxxxxxxxxxxxxxx
>> Subject: Re: vmcore not getting created on linux-4.7
>>
>>
>>
>> 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
>>
> 
> I did build/install kexec-tools-2.0.12. 
> 
>> Also what's the content of your /etc/kdump.conf file?
>>
> 
> #raw /dev/sda5
> #ext4 /dev/sda3
> #ext4 LABEL=/boot
> #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> #net my.server.com:/export/tmp
> #net user@xxxxxxxxxxxxx
> path /var/crash
> #ext4 /dev/nvme0n1
> core_collector makedumpfile -c --message-level 1 -d 31
> #core_collector makedumpfile -c --message-level 1 -d 17
> #core_collector scp
> #core_collector cp --sparse=always
> #extra_bins /bin/cp
> #link_delay 60
> #kdump_post /var/crash/scripts/kdump-post.sh
> #extra_bins /usr/bin/lftp
> #disk_timeout 30
> #extra_modules gfs2
> #options modulename options
> #default shell
> #debug_mem_level 0
> #force_rebuild 1
> #sshkey /root/.ssh/kdump_id_rsa
> 

Rather standart, indeed. I have a similar configuration and everything
is working as expected. The only other thing which I can suggest is to
try updating the makedumpfile binary.