Messages in this thread | | | Subject | RE: [PATH 0/1] Kexec jump - v2 - the first step to kexec based hibernation | Date | Mon, 6 Aug 2007 21:22:46 +0800 | From | "Huang, Ying" <> |
| |
>-----Original Message----- >From: Pavel Machek [mailto:pavel@ucw.cz] >> > Did the trick, I got the kernel to load, and it even attempted >> > exec... but I got doublefault (or what is it?) >> > >> > Int 6: ... EIP: c4739906. Address is in reserve_bootmem_core. >> > >> > Do I have to disable ACPI completely? I tried with acpi=off, >> > nosmp... but problem does not seem device related. >> >> It seems that the problem has nothing to do with device or ACPI. Can you >> do a normal kexec? That is: >> >> kexec -l <...> >> kexec -e >> >> or >> >> kexec -p <...> >> ALT-SysRq-c to trigger a crash dump. > >...that was indeed a problem. I can do successful kexec, as long as I >load bzImage (and not vmlinux). (Both kernels 2.6.22 and >2.6.23-rc2-git). Problem is, I can only load bzImage using -l, attempt >to load bzImage using -p results in > >"Could not find a free area of memory of 9000 bytes" >locate_hole failed > >. Any ideas?
The Kexec-tools 1.101 can not deal with bzImage with "-p" properly. So vmlinux must be used with "-p". And the tricks previous mentioned must be used for normal kexec -p too. The example command line is as follow:
kexec -p --args-linux vmlinux --append="root=/dev/<xxx> ..."
Best Regards, Huang Ying - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |