Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rudo <prudo@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: Gokul Praveen <g-praveen@ti.com>, kexec@lists.infradead.org
Subject: Re: VMCORE and kdump.conf file not found LINUX 6.12 KERNEL
Date: Tue, 18 Feb 2025 17:05:22 +0100	[thread overview]
Message-ID: <20250218170522.0861f62f@rotkaeppchen> (raw)
In-Reply-To: <CALu+AoRDtPRgZS6t57xXpQvQ9bXv7hTyebAVfPLXH69Op2qRzA@mail.gmail.com>

Hi,

On Tue, 18 Feb 2025 16:48:26 +0800
Dave Young <dyoung@redhat.com> wrote:

> On Tue, 18 Feb 2025 at 14:07, Gokul Praveen <g-praveen@ti.com> wrote:
> >
> > Hi Team,
> >
> > Just a reminder.
> > It would be really great if you could help me with the following.
> >
> > Regards
> > Gokul
> >
> > On 05/02/25 17:50, Gokul Praveen wrote:  
> > > Hi Team,
> > >
> > > It would be really great,if you could help me with a couple of questions
> > > regarding kexec and kdump.
> > >
> > > I tried kdump on my SOC and it is rebooting fine . However,the VMCORE
> > > file and /etc/kdump.conf file is not found.
> > >
> > > VERSION:
> > > kexec-tools 2.0.30.
> > > kernel 6.12v
> > >
> > > STEPS FOLLOWED:
> > >
> > > 1)git clone git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
> > >
> > > 2)
> > >     HOST PC:  
> > >      >cd $KEXEC_TOOLS_DIR
> > >      >./bootstrap LDFLAGS=-static ./configure --prefix=/usr/local  
> > > --host=aarch64-linux-gnu --target=aarch64-linux-gnu  
> > >      >make
> > >      >cp $KEXEC_TOOLS_DIR/build/sbin/kexec /media/$USER/rootfs/usr/sbin  
> > > (To copy the kexec binary to the rootfs filesystem of the target board)
> > >
> > >     TARGET BOARD:  
> > >      >Booted upto linux
> > >      >cmdline="crashkernel=128M console=ttyS2,115200n8  
> > > root=/dev/mmcblk0p2 rw rootfste=ext4 rootwait" (/dev/mmcblk0p2 refers to
> > > EMMC)  
> > >      > /kexec -p /Image --command-line="$cmdline"  
> > > --dtb=/k3-j721e-common-proc-board.dtb

The kdump kernel only presents the dump via /proc/vmcore but doesn't
write it to disk. That is done by user space contained in the initrd.
So for it to work you also have to provide an initrd that mounts the
target disk and writes the dump to it. But, as Dave already pointed
out, the creation of initrds is highly distro specific.

Thanks
Philipp

> > >      > echo c > /proc/sysrq-trigger  
> 
> Hi,
> 
> This looks more like a distribution related issue, I suggest you ask
> distribution developers to help.
> 
> Thanks
> Dave
> 
> 



      reply	other threads:[~2025-02-18 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 12:20 VMCORE and kdump.conf file not found LINUX 6.12 KERNEL Gokul Praveen
2025-02-18  6:06 ` Gokul Praveen
2025-02-18  8:48   ` Dave Young
2025-02-18 16:05     ` Philipp Rudo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250218170522.0861f62f@rotkaeppchen \
    --to=prudo@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=g-praveen@ti.com \
    --cc=kexec@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox