On Sun, Mar 11, 2007 at 08:35:08PM -0800, Dharmosoth Seetharam wrote: > -------------------------------------- > > I have traced the kexec tool .. and found the following hang point. > (kexec-tools-1.101) > purgatory/arch/x86_64/entry64.S > > entry64: > > .......... > > /* Jump to the new code... */ > jmpq *rip(%rip) > > > > ....... > > r14: .quad 0x00000000 > r15: .quad 0x00000000 > rip: .quad entry32 > .size entry64_regs, . - entry64_regs > > As per the above code it should jump to the entry_32. > But, somehow it is not getting to that address and system got hung.
At run time entry point (rip) will be replaced with kernel entry point (kexec-elf-x86_64.c). In this case it should be startup_64 (kernel/head.S) and control should reach there after purgatory execution. Try using earlyprintk= on kernel command line or insert some 'out' instructions in kernel boot code to output some debugging message to serial port and trace where does it hang. Thanks Vivek _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
