From: Rich Freeman <r-btrfs@gw.thefreemanclan.net>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Duncan <1i5t5.duncan@cox.net>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: unable to handle kernel paging request - btrfs
Date: Sun, 25 Sep 2016 19:42:52 -0500 [thread overview]
Message-ID: <CAGfcS_mhq6meu-d7BxwxaMLQBhm=STPG31OzVTf-ZaKb6a3KNw@mail.gmail.com> (raw)
In-Reply-To: <df57cbab-f316-c6a1-fccc-0a1c1e6dc276@suse.com>
On Sun, Sep 25, 2016 at 7:39 PM, Jeff Mahoney <jeffm@suse.com> wrote:
>
> I'm not sure about other distros, but at least with SLES/openSUSE you
> can configure kdump to /just/ dump the dmesg.
>
Well, on Gentoo I wrote the official docs on how it works, quite some
time ago... :) It is purely manual, so you can of course capture
whatever you want. Just have it reboot to a shell and then save what
you need to. An automated cross-distro core capture tool would
probably be useful. I wonder if there is a generic one floating
around somewhere.
--
RIch
next prev parent reply other threads:[~2016-09-26 0:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 12:18 unable to handle kernel paging request - btrfs Rich Freeman
2016-09-22 12:44 ` Holger Hoffstätte
2016-09-22 16:23 ` David Sterba
2016-09-22 16:46 ` Rich Freeman
2016-09-22 17:29 ` Chris Murphy
2016-09-22 17:41 ` Jeff Mahoney
2016-09-30 18:54 ` Rich Freeman
2016-09-30 20:55 ` Jeff Mahoney
2016-09-30 21:07 ` Rich Freeman
2016-10-01 0:38 ` Jeff Mahoney
2016-10-07 14:00 ` Rich Freeman
2016-10-08 21:55 ` Rich Freeman
2016-10-10 12:54 ` Rich Freeman
2016-09-23 4:58 ` Duncan
2016-09-25 13:55 ` Rich Freeman
2016-09-26 0:22 ` Jeff Mahoney
2016-09-26 0:37 ` Rich Freeman
2016-09-26 0:39 ` Jeff Mahoney
2016-09-26 0:42 ` Rich Freeman [this message]
2016-09-26 2:21 ` Duncan
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='CAGfcS_mhq6meu-d7BxwxaMLQBhm=STPG31OzVTf-ZaKb6a3KNw@mail.gmail.com' \
--to=r-btrfs@gw.thefreemanclan.net \
--cc=1i5t5.duncan@cox.net \
--cc=jeffm@suse.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).