[Crash-utility] ARM support for CONFIG_SPARSEMEM: (was Re:DDimage)

[Mika Westerberg]

On Thu, May 26, 2011 at 11:53 AM,  <takuo.koguchi.sw at hitachi.com> wrote:
> Hi Mika,
>
>>Please check your platforms
>>arch/arm/mach-<yourmach>/include/mach/memory.h and set both
>>_SECTION_SIZE_BITS and _MAX_PHYSMEM_BITS to be the same as defined in
>>the header. If crash works with the correct values, we just need to
> Both SECTION_SIZE_BITS 28 and MAX_PHYSMEM_BITS 32 are defined correctly in the kernel header and defs.h.
> Although, still I got
>>> crash: invalid kernel virtual address: f67f000  type: "page table"

Do you happen to have CONFIG_HIGHPTE enabled?

>
> It might come form my vmcore file's incorrectness.
> Currently my vmcore contains the following,
> Program Headers:
>  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
>  NOTE           0x000074 0x00000000 0x00000000 0x00000 0x00000     0
>  LOAD           0x000074 0xc0000000 0x00000000 0x20000000 0x20000000 RWE 0
>
> But actual mapping is,
> Virtual 0xc0000000-0xcfffffff corresponds Physical 0x00000000-0x0fffffff
> and
> Virtual 0xd0000000-0xdfffffff corresponds Physical 0x40000000-0x4fffffff
>
> Then I tried to prepend the following header instead,
> Program Headers:
>  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
>  NOTE           0x000094 0x00000000 0x00000000 0x00000 0x00000     0
>  LOAD           0x000094 0xc0000000 0x00000000 0x10000000 0x10000000 RWE 0
>  LOAD           0x10000094 0xd0000000 0x40000000 0x10000000 0x10000000 RWE 0
>
> This time crash does not recognize the vmcore file.
>
> Perhaps I have to change VTOP/PTOV macros accordingly?

It should be enough if you have machdep->machspec->phys_base set to
correct value, which is 0 in your case. You can see this by running
'crash -d1 ...'. Also if possible, can you post the full output here
so that we can analyze it further.