"Prabhakar K." <krishkar99 at 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
