Hello Kazu,
Thanks for the explanation. It's now clear.
I was mixing DISKDUMP_LOCAL and KDUMP_COMPRESSED_LOCAL dumpfiles.
Best regards,
Patrick Agrain
-Message d'origine-
De : HAGIO KAZUHITO(萩尾 一仁) [mailto:k-hagio...@nec.com]
Envoyé : mercredi 10 mars 2021 02:52
À : Agrain P
Hello,
I have a dump file produced by makedumpfile with following command:
/sbin/makedumpfile -d 0 -c --message-level 7 /proc/vmcore /tmpd/crashdump-`date
+"%Y%m%d-%H%M"`
When I edit the raw binary, it seems that the first bytes could be mapped to a
disk_dump_header structure.
Is that correct
development
Objet : EXT: Re: [Crash-utility] Address - Symbol correspondance
** External email - Please consider with caution **
Hi Patrick,
Try 'dis' command, like:
crash> dis 0xa4099980
Li Yueyi
Send by my mobile phone.
在 2021年3月5日，16:19，Agrain Patrick
mailto:patr
Hello all,
Target runs a CentOS8 kernel with KASLR enabled.
I triggered a crash on it for training purpose with 'echo c >
/proc/sysrq-trigger'.
I analyze the produced dumpfile on another machine where I setup all sources
and required debuginfo packages.
So far, so good, the backtrace list is co
ussion list for crash utility usage, maintenance and development
Objet : EXT: Re: [Crash-utility] Is there a way to validate the coherency of a
kdump-compressed dumpfile ?
** External email - Please consider with caution **
Hi Patrick,
On Thu, Feb 11, 2021 at 7:27 PM Agrain Patrick
w
Hello,
I'm trying to setup an analyze procedure (with scripts) and would like to
'check' the dumpfile before starting the interactive mode of 'crash'.
Is there a 'crash' option, command that would just :
* Return a status to say 'dumpfile is OK to be processed by crash'.
* Display a hea
i Mizuma [mailto:msys.miz...@gmail.com]
Envoyé : lundi 20 juillet 2020 14:50
À : Agrain Patrick
Cc : Discussion list for crash utility usage, maintenance and development
Objet : EXT: Re: [Crash-utility] EXT: Re: EXT: Re: crash start in CentOS 8
** External email - Please consider with caution **
H
--
De : Masayoshi Mizuma [mailto:msys.miz...@gmail.com]
Envoyé : lundi 20 juillet 2020 14:50
À : Agrain Patrick
Cc : Discussion list for crash utility usage, maintenance and development
Objet : EXT: Re: [Crash-utility] EXT: Re: EXT: Re: crash start in CentOS 8
** External email - Please consider
e
vmcores and execute:
# crash /usr/lib/debug/lib/modules/4.18.0-147.el8.x86_64/vmlinux vmcore
If it's (2), you need to boot the VM with the kernel and make a crash.
Could you check this first?
Thanks,
Kazu
On Mon, Jul 6, 2020 at 10:03 PM Agrain Patrick
wrote:
>
> Hello all,
>
cores and execute:
# crash /usr/lib/debug/lib/modules/4.18.0-147.el8.x86_64/vmlinux vmcore
If it's (2), you need to boot the VM with the kernel and make a crash.
Could you check this first?
Thanks,
Kazu
On Mon, Jul 6, 2020 at 10:03 PM Agrain Patrick
wrote:
>
> Hello all,
>
>
Hello all,
Back on this topic:
I compiled a kernel with debuginfo on the Virtual Machine with CentOS8.
I made a crash on this same VM.
I transferred the vmcore and vmlinux.debuginfo files on another CentOS8
baremetal machine.
The command '/usr/bin/crash -d 15 vmlinux.debuginfo vmcore' produces f
crash start in CentOS 8
** External email - Please consider with caution **
Hi Patrick,
On Mon, Jun 15, 2020 at 12:51 PM Agrain Patrick
wrote:
> -Message d'origine-
> De : crash-utility-boun...@redhat.com
> [mailto:crash-utility-boun...@redhat.com] De la part de Bhupe
rt in CentOS 8
** External email - Please consider with caution **
Hello Patrick,
On Mon, Jun 15, 2020 at 12:28 PM Agrain Patrick
wrote:
>
> Hello,
>
>
>
> I tried to test the crash utility from CentOS 8 with following requirements:
>
> First machine (VMware) on which
Hello,
I tried to test the crash utility from CentOS 8 with following requirements:
* First machine (VMware) on which CentOS 8 is installed and on which I
performed a fake crash using SysRq. After reboot, The /var/crash was populated
with the vmcore.
* Second machine (Server) on which C
14 matches
Mail list logo
