Re: EXT: Re: EXT: Re: crash start in CentOS 8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----Original Message-----
> > [root@lxkmg-pag-ale test64]# /usr/bin/crash -d 15
> > System.map-4.18.0-147.el8.x86_64 vmlinux.debuginfo vmcore
...
> > <read_diskdump: addr: ffffffff82131200 paddr: 37b31200 cnt: 8>
> > read_diskdump: PAGE_EXCLUDED: paddr/pfn: 37b31200/37b31
> > crash: page excluded: kernel virtual address: ffffffff82131200  type: "page_offset_base"
> > [root@lxkmg-pag-ale test64]#
> 
> Hmmm, I think you should find better results with:
> 
> $ crash vmlinux vmcore (On the machine used for post-processing)
> 
> and
> 
> $ crash vmlinux /proc/kcore (On the original crashing system)
> 
> I think if that helps you reach the crash > prompt, we have a potential issue which needs to be looked-at.
> Can you please try to run the same and let me know the outcome?
> 
> Thanks,
> Bhupesh
> 
> 
> --
> Crash-utility mailing list
> Crash-utility@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/crash-utility
> 
> Hello,
> 
> Running the above mentioned command on the server used to post process the crash shows a message indicating
> a mismatch between the vmcore and kernel.debug binary.
> 
> I will now first try to clarify this and come back later on if the issue is still there.
> 
> Thanks for helping.
> Best regards,
> Patrick Agrain
> 

Just FYI, with respect to the System.map file, the following Dave's post
would be helpful:
https://www.redhat.com/archives/crash-utility/2018-June/msg00002.html

If you have the vmlinux corresponding to a running kernel, you don't need
the System.map file.

Thanks,
Kazu


--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility




[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux