From: Vivek Goyal <vgoyal@in.ibm.com>
To: Alexander Nyberg <alexn@telia.com>
Cc: vgoyal@in.ibm.com,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
fastboot@lists.osdl.org, rddunlap@osdl.org,
Ralf.Hildebrandt@charite.de, petkov@uni-muenster.de,
Morton Andrew Morton <akpm@osdl.org>,
coywolf@gmail.com
Subject: Re: [Fastboot] Fw: Re: kexec?
Date: Wed, 11 May 2005 13:39:59 +0530 [thread overview]
Message-ID: <20050511080959.GB3799@in.ibm.com> (raw)
In-Reply-To: <1115795427.917.10.camel@localhost.localdomain>
> >
> > maxcpus=1 is the culprit. Even through bios/grub kernel does not boot with
> > option maxcpus=1. It is a known issue with got notieced 2.6.12-rc2-mm1 onwards.
> > So build second kernel as uniprocessor kernel and don't specify maxcpus=1 and
> > test it out. It should work.
> >
>
> Vivek,
>
> kexec-tools-1.101 does not contain your last patch series (that includes
> --crashdump which is lacking from the above cmdline). Currently you need
> to patch up 1.101 with the stuff from
> [RFC/PATCH 5/17][kexec-tools-1.101] Add command line option
> "--crash-dump" etc.
>
> It would be good having a 1.2 or something with the patches included on
> the site...
We have uploaded the kdump related user space patches which can be
accessed at following link.
http://lse.sourceforge.net/kdump/patches/
A single consolidated patch can be applied on top of kexec-tools-1.101.tar.gz
to get kdump working.
Thanks
Vivek
next prev parent reply other threads:[~2005-05-11 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050510193225.53192aad.akpm@osdl.org>
2005-05-11 3:02 ` Vivek Goyal
2005-05-11 7:10 ` Alexander Nyberg
2005-05-11 8:09 ` Vivek Goyal [this message]
2005-05-11 8:30 ` Alexander Nyberg
2005-05-11 8:57 ` Vivek Goyal
2005-05-12 3:35 ` randy_dunlap
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=20050511080959.GB3799@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=Ralf.Hildebrandt@charite.de \
--cc=akpm@osdl.org \
--cc=alexn@telia.com \
--cc=coywolf@gmail.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkov@uni-muenster.de \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®