From: ebiederm@xmission.com (Eric W. Biederman)
To: "Prabhakar K." <krishkar99@yahoo.com>
Cc: fastboot@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
Date: Fri, 25 Sep 2009 15:10:13 -0700 [thread overview]
Message-ID: <m1iqf6oeuy.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <473364.90108.qm@web65711.mail.ac4.yahoo.com> (Prabhakar K.'s message of "Fri\, 25 Sep 2009 11\:27\:15 -0700 \(PDT\)")
"Prabhakar K." <krishkar99@yahoo.com> writes:
> Hi - After my previous posting I was able to make some progress.
>
> When I do
>
> kexec -l vmlinux --append="init 1 root=/dev/hda2" --console-serial
>
> and
> kexec -e,
>
> I get message:
>
> Starting new kernel
> I'm in purgatory
>
> And after that it still boots from BIOS (to the same first kernel).
>
> Whats the problem here?
I would recommend instrumenting up purgatory and then your target kernel.
It is quite possible the problem is in your backport.
> Also do I need kdump again in addition to the latest kexec tools?
> When I do:
> #chkconfig kdump on
> error reading information on service kdump
> #service kdump start
> Bad core dump start addres: start
The user space kdump stuff is just a user space wrapper, that creates
a useful initrd etc.
> What am I missing here?
The appropriate list. Discussion of all things kexec has moved to the kexec
list at infradead which I have cc'd.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next parent reply other threads:[~2009-09-25 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <473364.90108.qm@web65711.mail.ac4.yahoo.com>
2009-09-25 22:10 ` Eric W. Biederman [this message]
2009-09-28 18:43 ` [Fastboot] kexec - 2.6.14 - loads BIOS again Prabhakar K.
2009-09-29 0:41 ` Eric W. Biederman
2009-09-29 2:48 ` Prabhakar K.
2009-09-30 19:03 ` Prabhakar K.
2009-10-01 0:07 ` Prabhakar K.
2009-10-01 0:59 ` Eric W. Biederman
2009-10-01 21:09 ` Prabhakar K.
2009-10-02 2:03 ` Eric W. Biederman
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=m1iqf6oeuy.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=fastboot@lists.linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=krishkar99@yahoo.com \
/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.