From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753823AbcGLQN1 (ORCPT ); Tue, 12 Jul 2016 12:13:27 -0400 Received: from smtp.opengridcomputing.com ([72.48.136.20]:51469 "EHLO smtp.opengridcomputing.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751463AbcGLQNZ (ORCPT ); Tue, 12 Jul 2016 12:13:25 -0400 From: "Steve Wise" To: "'nborisov'" , References: <007001d1ce27$17845550$468cfff0$@opengridcomputing.com> <576D4C77.8010404@gmail.com> <00b401d1ce2a$cace6fd0$606b4f70$@opengridcomputing.com> <576D61C3.6030509@gmail.com> <014e01d1ce55$aa4ba040$fee2e0c0$@opengridcomputing.com> In-Reply-To: <014e01d1ce55$aa4ba040$fee2e0c0$@opengridcomputing.com> Subject: RE: vmcore not getting created on linux-4.7 Date: Tue, 12 Jul 2016 11:13:27 -0500 Message-ID: <00c901d1dc58$52e86610$f8b93230$@opengridcomputing.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHw+JIfyrncQv60OhHhf+PiSDdJCQFHSXhBAgl2yzMCUZrWgwEZaF10n6DhFsA= Content-Language: en-us Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > >> 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@my.server.com > > > 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. > > Updating to 1.6.0 of makedumpfile didn't help. :( > Does anyone else have suggestions on how to debug this? From my original post, the dump kernel just reboots and I'm not sure why. Where can I add printks to gather more info on why the dump kernel gives on on the dump? Thanks, Steve.