All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, fastboot@lists.osdl.org
Subject: Re: Stupid kexec/kdump question...
Date: Tue, 26 Sep 2006 22:10:29 -0700	[thread overview]
Message-ID: <20060926221029.d9e87650.akpm@osdl.org> (raw)
In-Reply-To: <200609261525.k8QFP6j4022389@turing-police.cc.vt.edu>

On Tue, 26 Sep 2006 11:25:06 -0400
Valdis.Kletnieks@vt.edu wrote:

> OK, I'm running a Fedora Core 6 (rawhide actually) box with -18-mm1 kernel.
> I've installed kexec-tools and similar, and am trying to get the kernels
> built following the hints in Documentation/kdump/kdump.txt, but a few
> questions arise:
> 
> 1) Other than the fact that the Fedora userspace looks for a ${kernelvers}kdump
> kernel, is there any reason the kdump kernel has to match the running one, or
> can an older kernel be used?
> 
> 2) I'm presuming that a massively stripped down kernel (no sound support,
> no netfilter, no etc) that just has what's needed to mount the dump location
> is sufficient?
> 
> 3) The docs recommend 'crashkernel=64M@16M', but that's 8% of my memory.
> What will happen if I try '16M@16M' instead?  Just slower copying due to
> a smaller buffer cache space, or something more evil?
> 

(cc added)

  reply	other threads:[~2006-09-27  5:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 15:25 Stupid kexec/kdump question Valdis.Kletnieks
2006-09-27  5:10 ` Andrew Morton [this message]
2006-09-27  5:27   ` [Fastboot] " Horms
2006-09-27  8:00     ` Eric W. Biederman
2006-09-27 12:51       ` Valdis.Kletnieks
2006-09-27 13:11         ` Vivek Goyal
2006-09-27 13:24         ` Vivek Goyal
2006-09-27 14:44           ` Valdis.Kletnieks

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=20060926221029.d9e87650.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.