Discussion:
[Fastboot] fastboot Digest, Vol 59, Issue 2
Dharmosoth Seetharam
2009-10-22 05:55:50 UTC
Permalink
Prabhakar,

try with the following kernel command line.

crashkernel=128M at 16M

I think for i386 at least 128M should be reserved for dump-kernel to load.

thanks,
Seetharam
-----Original Message-----
From: fastboot-request at lists.linux-foundation.org
Sent: Wed, 30 Sep 2009 12:05:20 -0700
To: fastboot at lists.linux-foundation.org
Subject: fastboot Digest, Vol 59, Issue 2
Send fastboot mailing list submissions to
fastboot at lists.linux-foundation.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.linux-foundation.org/mailman/listinfo/fastboot
or, via email, send a message with subject or body 'help' to
fastboot-request at lists.linux-foundation.org
You can reach the person managing the list at
fastboot-owner at lists.linux-foundation.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of fastboot digest..."
1. Re: kexec - 2.6.14 - loads BIOS again (Eric W. Biederman)
2. Re: kexec - 2.6.14 - loads BIOS again (Prabhakar K.)
3. Re: kexec - 2.6.14 - loads BIOS again (Eric W. Biederman)
4. Re: kexec - 2.6.14 - loads BIOS again (Prabhakar K.)
5. Re: kexec - 2.6.14 - loads BIOS again (Prabhakar K.)
----------------------------------------------------------------------
Message: 1
Date: Fri, 25 Sep 2009 15:10:13 -0700
From: ebiederm at xmission.com (Eric W. Biederman)
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
To: "Prabhakar K." <krishkar99 at yahoo.com>
Cc: fastboot at lists.linux-foundation.org, Kexec Mailing List
<kexec at lists.infradead.org>
Message-ID: <m1iqf6oeuy.fsf at fess.ebiederm.org>
Content-Type: text/plain; charset=us-ascii
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,
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?
#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
------------------------------
Message: 2
Date: Mon, 28 Sep 2009 11:43:27 -0700 (PDT)
From: "Prabhakar K." <krishkar99 at yahoo.com>
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
To: Kexec Mailing List <kexec at lists.infradead.org>
Cc: fastboot at lists.linux-foundation.org
Message-ID: <808738.1314.qm at web65701.mail.ac4.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
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,
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.
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.
Thanks Eric. For directing me to the right mailing list.
I am not subscribed to the list, so please CC me. Thanks !!
Regards,Prabhakar
-------------- next part --------------
An HTML attachment was scrubbed...
http://lists.linux-foundation.org/pipermail/fastboot/attachments/20090928/7e93dc65/attachment-0001.htm
------------------------------
Message: 3
Date: Mon, 28 Sep 2009 17:41:17 -0700
From: ebiederm at xmission.com (Eric W. Biederman)
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
To: "Prabhakar K." <krishkar99 at yahoo.com>
Cc: fastboot at lists.linux-foundation.org, Kexec Mailing List
<kexec at lists.infradead.org>
Message-ID: <m1tyympope.fsf at fess.ebiederm.org>
Content-Type: text/plain; charset=us-ascii
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,
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
------------------------------
Message: 4
Date: Mon, 28 Sep 2009 19:48:22 -0700 (PDT)
From: "Prabhakar K." <krishkar99 at yahoo.com>
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
To: "Eric W. Biederman" <ebiederm at xmission.com>
Cc: fastboot at lists.linux-foundation.org, Kexec Mailing List
<kexec at lists.infradead.org>
Message-ID: <527147.77305.qm at web65705.mail.ac4.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
From: Eric W. Biederman <ebiederm at xmission.com>
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
To: "Prabhakar K." <krishkar99 at yahoo.com>
Cc: "Kexec Mailing List" <kexec at lists.infradead.org>,
fastboot at lists.linux-foundation.org
Date: Tuesday, September 29, 2009, 6:11 AM
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,
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?
Yes, we do have software watchdog and hardware watchdog. I disabled
software watchdog and I think the reason for resetting to the first
kernel can be explained due to hardware watchdog kicking in.
To try out a different version of the kexec, I took kexec version
20080227
from?http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/and
instrumented that code as well. With this, I was able to see the sha 256
verification done during kexec -e and also the post verification of
purgatory code. And it hangs there (does not reboot to the first kernel).
So, any conclusions based on these ? Please CC me in reply. Thanks !!
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
http://lists.linux-foundation.org/pipermail/fastboot/attachments/20090928/66467db3/attachment-0001.htm
------------------------------
Message: 5
Date: Wed, 30 Sep 2009 12:03:07 -0700 (PDT)
From: "Prabhakar K." <krishkar99 at yahoo.com>
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
To: "Eric W. Biederman" <ebiederm at xmission.com>
Cc: fastboot at lists.linux-foundation.org, Kexec Mailing List
<kexec at lists.infradead.org>
Message-ID: <367789.94839.qm at web65708.mail.ac4.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
I have back ported to multiple versions of different kexec-tools. Also I
disabled watchdogs so that the first kernel reboot is not kicked in.Now,
with all those kexec-tools I see that it hangs
after?post_verification_setup_arch( ).And I had to hard reboot the router
box.
Is there a specific kexec tools that is known to work with 2.6.14 ? Or
any additional changes needed ?
Any inputs welcome , thanks in advance !!
Please CC me in reply.
Regards,Prabhakar
From: Eric W. Biederman <ebiederm at xmission.com>
Subject: Re: [Fastboot] kexec - 2.6.14 - loads BIOS again
To: "Prabhakar K." <krishkar99 at yahoo.com>
Cc: "Kexec Mailing List" <kexec at lists.infradead.org>,
fastboot at lists.linux-foundation.org
Date: Tuesday, September 29, 2009, 6:11 AM
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,
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
-------------- next part --------------
An HTML attachment was scrubbed...
http://lists.linux-foundation.org/pipermail/fastboot/attachments/20090930/29193d81/attachment.htm
------------------------------
_______________________________________________
fastboot mailing list
fastboot at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/fastboot
End of fastboot Digest, Vol 59, Issue 2
***************************************
____________________________________________________________
GET FREE 5GB EMAIL - Check out spam free email with many cool features!
Visit http://www.inbox.com/email to find out more!

Loading...