----- Original Message ----- > On 11/19/2015 07:45 AM, Dave Anderson wrote: > > Hi Dave, > > > ----- Original Message ----- > <snip> > > > >> (2) Execute "crash -d8" on physical machine will cause crash utility core > >> dump. > > > > I can reproduce this, so I'll look into it. It's related to the /dev/mem "test" > > to determine whether the kernel was configured with CONFIG_STRICT_DEVMEM, where > > it tries to read from pfn 257 (just above the CONFIG_STRICT_DEVMEM limit), but > > gets into an infinite loop when used in conjunction with -d. > > > > Anyway, just continue to use /proc/kcore and you should be fine. > > I assume switch_to_proc_kcore() isn't Xen specific but since it will > happen on all our dom0's would you care if I continued with it? Right. And as far as fixing this, if devmem_is_restricted() is patched to return FALSE if it's recursively called, that seems to work for me. Or were you thinking of hacking PRINT_ERROR_MESSAGE() up even further? Dave -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
