Re: [Crash-utility] vmss.core and kernel dbgsym do not match!

----- Original Message ----- q That was an old Xen RHEL5 kernel issue, so I don't know if that applies to your 4.4-based VMware vmss dumpfile (?). Although I only have a 4 sample vmss dumpfiles, one of does happen to be a RHEL5 kernel and it does require --machdep phys_base=0x200000. But it's certainly possible that could be the issue. If you run the guest again and log into it, you could try running crash on the live system. If it comes up OK, run the "help -m" command and grep for "phys_base". Then try that value as the --machdep phys_base= argument with the dumpfile. Worse case, you could try different phys_base values and basically fish for the correct value. What does "strings vmlinux-4.4.0-36-generic" show? You'll need to verify that the full string above is exactly the same. It's the PhysAddr that's the key to crash -- the header is showing that the dumpfile contains 2GB (0x80000000) of physical memory starting at physical address 0. If you show the output of "crash -d8 ..." it may yield some more clues. Dave