From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751397AbeA1KAn (ORCPT <rfc822;w@1wt.eu>);
        Sun, 28 Jan 2018 05:00:43 -0500
Received: from mout.gmx.net ([212.227.17.20]:61545 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1750808AbeA1KAl (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 28 Jan 2018 05:00:41 -0500
Message-ID: <1517133624.6669.22.camel@gmx.de>
Subject: Re: crash binary for latest unreleased kernel
From: Mike Galbraith <efault@gmx.de>
To: Joe Smith <codesoldier1@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Date: Sun, 28 Jan 2018 11:00:24 +0100
In-Reply-To: <1517131246.6669.11.camel@gmx.de>
References: <CABGNecyRGfSrrTH99Jps7KaDO3G3GuRErUDGixt4fueX467UBQ@mail.gmail.com>
         <1517027565.10239.61.camel@gmx.de>
         <b7b94e75-8052-738d-cc18-5aa1d0b4afde@infradead.org>
         <1517028522.10239.66.camel@gmx.de>
         <CABGNecydtsBT070SoVNRGbnmBdGNHAkEaAzJdoHd_ogyUn=ayw@mail.gmail.com>
         <1517131246.6669.11.camel@gmx.de>
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:uhz5j2FCcE52uuN/FF00SVA8AeKmtg8aYKuwMNHin+usHtWldwD
 xZjDSuqRRQgmd70TkokJjLAdFIqE8gNL5C3LSpfj3EbPXbCbUujk5CVPaEWRZbf3jAnOUs1
 dR9i07d0ZFmZcsr4Zc6mjtN0DbkAIflayLzuUJV0lsGZZwyynkubpkpjbFDGKxoLufRs0L4
 9ATVeVVjCJ7X7IiB//KlQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:A8/vTzpDIXE=:Sbn6H+rYks+eXSsuN9+9zN
 4BWKeAKn4XRXeeNZ9pumPdtx2B74QNCg9cDaJrjOUXcEeb/4Juu52aryc15FYGznDd8uZv+63
 2P08KJhIEJ3rd6s93ZQRvlH6znOzDFM5ZU2tJsNMhA5NJtGqRThmChegY/uRZatoaoyXzUIJD
 U/5ZH8cI0DJvGjlhr5z0uy9i7HMvTVLgXZlyxo87a+JdAmxPLAAa6G0kIZ8NL+8kltXOzXvrh
 230wukKrODyCAlKGTNG3lbATyuHzNgVgrD68LuW7vve1Xe5jh2IGJfksEn/Uzg4WbzfOAXemo
 e3s7hD5xbAw2Ob2WSQwj8NwSumhVsMFJdscoZl/sN4nf6NVnZ76Kbi9ajaLGsL/uSTvdpWgbZ
 ZQDZMB7CxFPn4l3CYRAqrHYWJLcE1IE3FFjSpiNYquZ5fXADMy1rAFUnACLwzskoG6iVsc1i3
 MyR6XFb9d6QPbNIAyOjJMi2BKwQvabKcCReS23n/JO++gLscN3tiDiDTbWJqxwx/MHUXqUgXU
 KA3KBIWeClZ1+Uo5w0g4YYv3PSnIt13gUYcJLzCRHFfXjBD8Z6mQg72VA6LP12iBmildAiCV5
 uvBkLzGtnG6YwxVVV/UfVcbzkS+ix88aIIuxKAR7rJ8JwO4JpeWc/765XCVZ3uOEL+6KLLs8X
 i5ssN3MiSpntm8kOZlglPYD8uLIOX3eua+vGWcmxig57jT4+dLyEgvGLasKv9ZXl5dg0e3JHG
 39DUk4GVXraNQSizcBnFd6V9GhpWjS1M7H+EcljVHY/Uqowa7sXGYeFiUnBXDJJ1+Ifi9hUvq
 5DbgRBzhqri63FPbr38rP2hT4dSZjsTmH+tEl2Kq2/58WGKGP8YSeDaZXnJDn6g8UEkJLapi0
 V9srT3oZsYcSRtbuLLczd7Ut9yMczjJ4pQ+6aemQoLknlBGlbRYkQCeQoB56bShlYFVqo74Is
 ffNwpZYt0Xg==
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, 2018-01-28 at 10:20 +0100, Mike Galbraith wrote:
> On Sun, 2018-01-28 at 00:37 -0800, Joe Smith wrote:
> > I happen to look at the patches for the crash binary and came across
> > this log entry from Jan 19. I am also using 4.15-rc kernel. Not
> > knowing anything about crash it is hard to even attempt to fix it.
> 
> It may not work all that well if box does something new/creative, but
> mundane manual crash, and live rummaging seem to work well enough.

And looking through my modified makedumpfile package, looks like I've
replaced everything I had ever done do it with backports from newer
versions, so you should be able to get kdump working with nothing more
than an update to makefumpfile, plus virgin upstream crash source.

	-Mike