Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gokul Praveen <g-praveen@ti.com>
To: <kexec@lists.infradead.org>
Subject: Re: VMCORE and kdump.conf file not found LINUX 6.12 KERNEL
Date: Tue, 18 Feb 2025 11:36:37 +0530	[thread overview]
Message-ID: <a69a8eaf-9fc0-468b-b39a-1486e6054878@ti.com> (raw)
In-Reply-To: <4ccd4d81-2efd-4369-a759-552dbb9a007f@ti.com>

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
>      > echo c > /proc/sysrq-trigger
> 
> 
> LOGS:
> 
>           Starting Reboot and dump vmcore via kexec...
> [  OK  ] Listening on Docker Socket for the API.
> [  OK  ] Listening on Weston socket.
> [  OK  ] Started D-Bus System Message Bus.
> [  OK  ] Reached target Socket Units.
> [  OK  ] Reached target Basic System.
> [  OK  ] Started Job spooling tools.
>           Starting Avahi mDNS/DNS-SD Stack...
> [  OK  ] Started Periodic Command Scheduler.
>           Starting Print notice about GPLv3 packages...
>           Starting IPv6 Packet Filtering Framework...
>           Starting IPv4 Packet Filtering Framework...
> [  OK  ] Started irqbalance daemon.
>           Starting Telephony service...
>           Starting Expand the rootfs partiti…to full size of the boot 
> device....
> [    5.992254] audit: type=1334 audit(1728487094.820:10): prog-id=14 
> op=LOAD
> 
> [    6.003634] audit: type=1334 audit(1728487094.832:11): prog-id=15 
> op=LOAD
> [    6.010482] audit: type=1334 audit(1728487094.832:12): prog-id=16 
> op=LOAD
>           Starting User Login Management...
>           Starting Telnet Server...
> [  OK  ] Finished IPv6 Packet Filtering Framework.
> [  OK  ] Finished IPv4 Packet Filtering Framework.
> [  OK  ] Finished Telnet Server.
> [  OK  ] Started User Login Management.
> [  OK  ] Finished Expand the rootfs partition to full size of the boot 
> device..
> [  OK  ] Started Telephony service.
> [  OK  ] Started Avahi mDNS/DNS-SD Stack.
> [  OK  ] Created slice Slice /system/systemd-fsck.
>           Expecting device /dev/mmcblk0p1...
> [  OK  ] Reached target Preparation for Network.
>           Starting Load Kernel Module drm...
> [    6.406000] audit: type=1334 audit(1728487095.236:13): prog-id=17 
> op=LOAD
>           Starting Network Configuration...
>           Starting Virtual Console Setup...
> [  OK  ] Stopped target RPC Port Mapper.
> [  OK  ] Stopped target Timer Units.
> [  OK  ] Stopped Daily rotation of log files.
> [  OK  ] Stopped Daily Cleanup of Temporary Directories.
> [  OK  ] Stopped target System Time Set.
>           Stopping Job spooling tools...
>           Stopping Avahi mDNS/DNS-SD Stack...
>           Stopping Periodic Command Scheduler...
>           Stopping irqbalance daemon...
> [  OK  ] Stopped target Host and Network Name Lookups.
>           Stopping Telephony service...
> [  OK  ] Stopped Expand the rootfs partition to full size of the boot 
> device..
>           Stopping strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf...
> [  OK  ] Removed slice Slice /system/getty.
> [  OK  ] Removed slice Slice /system/serial-getty.
>           Stopping User Login Management...
>           Stopping Load/Save OS Random Seed...
>           Starting Record Runlevel Change in UTMP...
>           Stopping Telnet Server...
> [  OK  ] Stopped target Remote File Systems.
> [  OK  ] Stopped Reboot and dump vmcore via kexec.


  reply	other threads:[~2025-02-18  6:06 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 [this message]
2025-02-18  8:48   ` Dave Young
2025-02-18 16:05     ` Philipp Rudo

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=a69a8eaf-9fc0-468b-b39a-1486e6054878@ti.com \
    --to=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