vmcore_init() failure using uImage on fsl_booke

McClintock Matthew-B29882 B29882 at freescale.com
Thu Sep 15 12:20:31 EDT 2011

On Thu, Sep 15, 2011 at 11:13 AM, Maxim Uvarov <muvarov at gmail.com> wrote:
> 2011/9/15 Dennis Flynn <dennis.flynn at ericsson.com>:
>>> I assume this is 512M?
>> Yes, 512M.
>>> It appears to have allocated a segment at this address. Can you try adding debug statements to exec to see the contents of this segment? I suspect kexec is loading nothing since it does not have an ELF header to load for the uImage case.
>> I added code to default_machine_kexec() to ioremap the segment[2].mem physical address and then use print_hex_dump() to dump the contents of this segment. Looks like the ELF header signature is present. Just not visible via /dev/oldmem from the crash kernel?
> But should /dev/oldmem have elf header? As I remember it is
> constructing when you read from /proc/vmcore.

It seems logical that /dev/oldmem should not require anything except
the old memory not to be modified. So, in any case this should not be
a fatal error, right?


More information about the kexec mailing list