On Tue, Apr 05, 2022 at 01:44:14PM +0200, Philipp Rudo wrote:
Hi Coiby,
On Sat, 2 Apr 2022 18:07:09 +0800
Coiby Xu <coxu(a)redhat.com> wrote:
> Hi Philipp,
>
> Thanks for reviewing this patch set!
>
> On Fri, Mar 25, 2022 at 06:16:13PM +0100, Philipp Rudo wrote:
> >Hi Coiby,
> >
> >On Tue, 1 Mar 2022 17:39:57 +0800
> >Coiby Xu <coxu(a)redhat.com> wrote:
> >
> >> 1. yum is deprecated so use dnf instead
> >> 2. use the "kdumpctl reset-crashkernel" API
> >>
> >> Signed-off-by: Coiby Xu <coxu(a)redhat.com>
> >> ---
> >> kexec-kdump-howto.txt | 23 ++++++++++++-----------
> >> 1 file changed, 12 insertions(+), 11 deletions(-)
> >>
> >> diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt
> >> index 1aeffc7..0121d0e 100644
> >> --- a/kexec-kdump-howto.txt
> >> +++ b/kexec-kdump-howto.txt
> >> @@ -44,7 +44,7 @@ ia64 and ppc64.
> >> If you're reading this document, you should already have kexec-tools
> >> installed. If not, you install it via the following command:
> >>
> >> - # yum install kexec-tools
> >> + # dnf install kexec-tools
> >>
> >> Now load a kernel with kexec:
> >>
> >> @@ -66,23 +66,24 @@ How to configure kdump
> >> Again, we assume if you're reading this document, you should already
have
> >> kexec-tools installed. If not, you install it via the following command:
> >>
> >> - # yum install kexec-tools
> >> + # dnf install kexec-tools
> >>
> >
> >
> >> To be able to do much of anything interesting in the way of debug
analysis,
> >> you'll also need to install the kernel-debuginfo package, of the same
arch
> >> as your running kernel, and the crash utility:
> >>
> >> - # yum --enablerepo=\*debuginfo install kernel-debuginfo.$(uname -m)
crash
> >> + # dnf --enablerepo=\*debuginfo install kernel-debuginfo.$(uname -m)
crash
> >
> >personally I would remove the whole paragraph. IMHO this how-to should
> >be on how to setup kdump to create a dump. Not how to analyze one.
>
> I'd like to keep it for two reasons,
ok, no problem it was only a suggestion.
> - This info is useful and I don't find a file like crash-howto.
> - This paragraph dated to 2006 according to commit 9ac14dd ("fixing bz
> 206861"). There could be another unknown reason why it has such a
> long history.
Hmm.. no clue what the bug and the commit fit together...
Nevertheless only because it has been this way for a long time doesn't
automatically mean that it made sense in the first place ;-)
I just notice this file has the following paragraphs in the later
section,
Once back to your normal kernel, you can use the previously installed crash
kernel in conjunction with the previously installed kernel-debuginfo to
perform postmortem analysis:
# crash /usr/lib/debug/lib/modules/2.6.17-1.2621.el5/vmlinux
/var/crash/2006-08-23-15:34/vmcore
crash> bt
So I guess we need to keep the info of installing kernel-debuginfo.
--
Best regards,
Coiby