On Thursday 08 June 2017 10:31 AM, Pratyush Anand wrote: > > > On Thursday 08 June 2017 10:23 AM, Abhishek Shah wrote: >> Hi Pratyush, >> I have posted the same question on the list as well.... >> Maybe I will copy your response there and continue discussion... > > Ah..I was on PTO, and just chasing with volume of mails. > > I see your mail at list :-) > >> I am using yocto(2.3 version) to build makedumpfile, which fetches v1.6.1 >> makedumpfile and also applys some patches including arm64 specific patches. What are these ARM64 specific patches? I believe, you do not need any topup in makedumpfile for ARM64 if you use v1.6.1. >> We have VA_BITS set as 48 bits... I will get other information and post on the >> list. OK. >> >> Regards, >> Abhishek >> >> On Jun 8, 2017 10:05 AM, "Pratyush Anand" <panand at redhat.com >> <mailto:panand at redhat.com>> wrote: >> >> Hi Abhishek, >> >> >> On Monday 05 June 2017 04:51 PM, Abhishek Shah wrote: >> >> Hi Atsushi, >> >> I am using makedumpfile utility to compress the ramdump taken by >> kexec/kdump, >> i.e. /proc/vmcore, on arm64 platform. >> >> /proc/vmcore works fine with crash utility without passing it though >> makedumpfile, but the file generated by makedumpfile is not getting >> processed >> by crash utility; I am getting following error: >> crash: seek error: kernel virtual address: ffff8008000c16a0 type: >> "memory >> section" >> >> Makedumpfile currently seems to support kernel up to 4.8 as per >> documentation. >> Is there plan to support newer kernel? can you provide some pointers to >> modifications required for newer kernel support, if I can help? >> >> >> Are you using makedumpfile-1.6.1? I expect that it should work with latest >> ARM64 kernel as well. If it does not work, can you please share your >> kernel configuration specially about, >> >> VA_BITS, PAGE_SHIFT, RANDOMIZE_BASE etc. >> >> ..and please keep mailing list in CC so that you can get answer from more >> people. Also, other can get benefit from this conversation. >> >> ~Pratyush >> >> ~Pratyush
