On Mon, Apr 16, 2007 at 12:43:42PM -0600, Bob Montgomery wrote: > On Mon, 2007-04-16 at 13:44 +0530, Vivek Goyal wrote: > > On Mon, Apr 16, 2007 at 04:44:37PM +0900, Simon Horman wrote: > > > On Mon, Apr 16, 2007 at 10:59:12AM +0530, Vivek Goyal wrote: > > > > On Mon, Apr 16, 2007 at 07:13:19AM +0200, Thomas Meyer wrote: > > > > > Vivek Goyal schrieb: > > > > > > On Sun, Apr 15, 2007 at 01:38:25PM +0200, Thomas Meyer wrote: > > > > > > > > > > > >> Hi. > > > > > >> > > > > > >> Kexec fails with this error message: > > > > > >> > > > > > >> "Could not find a free area of memory of 9000 bytes... > > > > > >> locate_hole failed" > > > > > >> > > > > > >> Kexec version is 1.101-r4 (gentoo) > > > > > >> Linux kernel version is: 2.6.21-rc6 > > I get this message on my x86_64 system when my kdump kernel is a vmlinuz > instead of vmlinux.
That's perfectly fine as vmlinuz for x86_64 can't be loaded into reserved memory region and when "kexec -p" tries to load it, bzImage looks for regular address and not reserved regions. Hence above message. > When I try a vmlinuz with a different version of > kexec-tools, I just get "BzImage is not relocatable. Can't be used as > capture kernel." This also makes sense. Newer version of kexec-tools know that a bzImage can be relocatable too. If one is not, then it gives you the error message otherwise continues loading it. So this is even earlier detection of failure than the previous kexec-tools. Thanks Vivek _______________________________________________ fastboot mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/fastboot
