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: Mon, 28 Sep 2009 17:41:17 -0700 [thread overview]
Message-ID: <m1tyympope.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <808738.1314.qm@web65701.mail.ac4.yahoo.com> (Prabhakar K.'s message of "Mon\, 28 Sep 2009 11\:43\:27 -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.
>
>>>>>
> I have instrumented the purgatory code. when I run kexec -e, It hangs for a
> while at
> sha256_starts(&ctx); in the function verify_sha256_digest(), and then reboots
> to the first kernel (from BIOS). I have put debug prints in sha256_starts, but
> none of those are executed.
>
> Interestingly, the same function sha256_starts is executed during kexec -l,
> which is called as part of update_purgatory( )( when my_load( ) is called from
> kexec.c).
> so its surprise why the same function is giving problems when kexec -e is run.
Do you by any chance have a watchdog you are not petting?
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-09-29 0:41 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 ` [Fastboot] kexec - 2.6.14 - loads BIOS again Eric W. Biederman
2009-09-28 18:43 ` Prabhakar K.
2009-09-29 0:41 ` Eric W. Biederman [this message]
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=m1tyympope.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.