Hi Kevin, Thank you for the report. Worth, Kevin wrote: > I now get the following result (still a failure but hopefully provides > some additional info). As I mentioned before, I have another system with > identical hardware but only 2GB of memory instead of 4GB and I don't > encounter this, not sure what kind of system you're testing on, but it > may not reproduce with <4GB of memory, despite having a matching config. My system has 5GB memory, and I'm testing on ubuntu kernel which is built by your config file. But I haven't been able to reproduce this problem yet. > Excluding zero pages : [ 38 %] readmem: Can't seek the dump memory(/proc/vmcore). (offset:800002d8) Invalid argument > readmem: addr:84060000, size:4096 > exclude_zero_pages: Can't get the page data(pfn:84060, max_mapnr:140000). > create_2nd_bitmap: Can't exclude pages filled with zero for creating an ELF dumpfile. > > [snip] > > LOAD (3) > phys_start : 38000000 > phys_end : bf790000 > virt_start : ffffffffffffffff > virt_end : 8778ffff When lseek() fails at readmem(), the physical address is 0x84060000 and this address is valid because it exists in LOAD (3). The cause of lseek() failure is due to an invalid 'offset' value or a kernel problem related to /proc/vmcore. I'd like to know real 'offset' value when lseek() fails, so could you run makedumpfile-1.3.0-rc01 by strace ? Ex) strace makedumpfile -D -E -d 31 -i $rootmnt/boot/vmcoreinfo /proc/vmcore $rootmnt/var/crash/vmcore BTW if you specify '-d 30' as makedumpfile arguments, does it succeed ? Thanks Ken'ichi Ohmichi
