Trying to debug a problem and my understanding is dim. Is the entry that is presented to the kernel equal to the entry that one would get from readelf -h on a vmlinux compiled with a physical offset?
If so then I am seeing a problem with the kexec-tools not providing the correct entry point. This is using kexec-tools-testing (assuming that it already has the kdump patches in it) v1.101-g1e2050c from git://git.kernel.org/pub/scm/linux/kernel/git/horms/kexec-tools-testing readelf -h vmlinux ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x1000000 Start of program headers: 52 (bytes into file) Start of section headers: 1290880 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 3 Size of section headers: 40 (bytes) Number of section headers: 39 Section header string table index: 36 kexec_load failed: Cannot assign requested address entry = 0x1498 flags = 1 _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
