The poky repository master branch is no longer being updated.

You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

b) use the new bitbake-setup

You can find information about either approach in our documentation:
https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

10 files changed, 0 insertions, 470 deletions

diff --git a/meta/recipes-kernel/kexec/kexec-tools/0001-Make-the-segment-base-match-pinned-section-address.patch b/meta/recipes-kernel/kexec/kexec-tools/0001-Make-the-segment-base-match-pinned-section-address.patch
deleted file mode 100644
index 6babf16e6e..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/0001-Make-the-segment-base-match-pinned-section-address.patch
+++ /dev/null
@@ -1,62 +0,0 @@
-From 0d8a9e12b6509cb2a79818f5f4062a0bee33edfc Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@gmail.com>
-Date: Wed, 3 Sep 2025 13:28:32 -0700
-Subject: [PATCH] Make the segment base match pinned section address
-
-ET_EXEC uses image base of 0x400000, but the build forces
-section VMAs like .text = 0x10000. LLD now errors when any
-section address is below the image base unless you explicitly
-set the base. (Older LLD tolerated it.)
-
-To fix this, set the image base to match forced section addresses
-
-Fixes
-| x86_64-yoe-linux-ld.lld: error: section '.text' address (0x10000) is smaller than image base (0x400000); specify --image-base
-| x86_64-yoe-linux-ld.lld: error: section '.bss' address (0x12000) is smaller than image base (0x400000); specify --image-base
-
-Upstream-Status: Submitted [https://lists.infradead.org/pipermail/kexec/2025-September/033493.html]
-
-Signed-off-by: Khem Raj <raj.khem@gmail.com>
----
- kexec_test/Makefile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
---- a/kexec_test/Makefile
-+++ b/kexec_test/Makefile
-@@ -5,7 +5,7 @@ RELOC:=0x10000
- KEXEC_TEST_SRCS:= kexec_test/kexec_test16.S kexec_test/kexec_test.S
- 
- dist += kexec_test/Makefile $(KEXEC_TEST_SRCS)                         \
--       kexec_test/x86-setup-legacy-pic.S
-+       kexec_test/x86-setup-legacy-pic.S kexec_test/kexec_test.ld
- 
- BUILD_KEXEC_TEST = no
- ifeq ($(ARCH),i386)
-@@ -31,7 +31,7 @@ $(KEXEC_TEST): CPPFLAGS+=-DRELOC=$(RELOC
- $(KEXEC_TEST): ASFLAGS+=-m32
- #$(KEXEC_TEST): LDFLAGS=-m32 -Wl,-e -Wl,_start -Wl,-Ttext -Wl,$(RELOC) \
- #                     -nostartfiles
--$(KEXEC_TEST): LDFLAGS=-melf_i386 -e _start -Ttext $(RELOC)
-+$(KEXEC_TEST): LDFLAGS=-melf_i386 -e _start -T $(srcdir)/kexec_test/kexec_test.ld
- 
- $(KEXEC_TEST): $(KEXEC_TEST_OBJS)
-        mkdir -p $(@D)
---- /dev/null
-+++ b/kexec_test/kexec_test.ld
-@@ -0,0 +1,16 @@
-+ENTRY(_start)
-+SECTIONS
-+{
-+  . = 0x10000;
-+  .text : { *(.text .text.*) }
-+
-+  /* Place the note after .text to avoid overlap */
-+  . = ALIGN(16);
-+  .note.gnu.property : { *(.note.gnu.property) }
-+
-+  .rodata : { *(.rodata .rodata.*) }
-+
-+  /* If you need bss fixed: */
-+  . = 0x12000;
-+  .bss : { *(.bss .bss.* COMMON) }
-+}
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0001-arm64-kexec-disabled-check-if-kaslr-seed-dtb-propert.patch b/meta/recipes-kernel/kexec/kexec-tools/0001-arm64-kexec-disabled-check-if-kaslr-seed-dtb-propert.patch
deleted file mode 100644
index ee731cea4b..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/0001-arm64-kexec-disabled-check-if-kaslr-seed-dtb-propert.patch
+++ /dev/null
@@ -1,67 +0,0 @@
-From 9e95f8933bded10fdd664fc95492825347ec59a7 Mon Sep 17 00:00:00 2001
-From: Alexander Kamensky <alexander.kamensky42@gmail.com>
-Date: Thu, 12 Nov 2020 12:56:46 -0800
-Subject: [PATCH] arm64: kexec: disabled check if kaslr-seed dtb property was
- wiped
-
-Kexec when loading arm64 kernel checks if chosen/kaslr-seed dtb property is
-wiped. It's a good assertion to verify proper behavior of kernel. However,
-if bootloader creates and fills kaslr-seed property and kernel is not
-configured with CONFIG_RANDOMIZE_BASE then logic of reading and wiping
-kaslr-seed does not run. As a result kaslr-seed property is not zero and when
-kexec tries to load secondary kernel it fails with the following message:
-
-setup_2nd_dtb: kaslr-seed is not wiped to 0.
-kexec: setup_2nd_dtb failed.
-kexec: load failed.
-
-This was observed on Yocto Project on qemuarm64 machine with 5.8 kernel,
-qemu 5.1.0. Qemu created kaslr-seed property but kernel was not configured
-with CONFIG_RANDOMIZE_BASE.
-
-Although check has some value, there is a use-case where it breaks kexec,
-this patch removes it.
-
-Note in described use-case the fact that kaslr-seed is not wiped and user
-readable through /sys/firmware/fdt or
-/sys/firmware/devicetree/base/chosen/kaslr-seed is not a security problem
-as kaslr is disabled anyway.
-
-Signed-off-by: Alexander Kamensky <alexander.kamensky42@gmail.com>
-Upstream-Status: Submitted [http://lists.infradead.org/pipermail/kexec/2020-November/021740.html]
----
- kexec/arch/arm64/kexec-arm64.c | 14 +-------------
- 1 file changed, 1 insertion(+), 13 deletions(-)
-
-diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
-index 9091f40..ea304f9 100644
---- a/kexec/arch/arm64/kexec-arm64.c
-+++ b/kexec/arch/arm64/kexec-arm64.c
-@@ -504,7 +504,7 @@ static int setup_2nd_dtb(struct dtb *dtb, char *command_line, int on_crash)
-        int len, range_len;
-        int nodeoffset;
-        int new_size;
--       int i, result, kaslr_seed;
-+       int i, result;
- 
-        result = fdt_check_header(dtb->buf);
- 
-@@ -577,18 +577,6 @@ static int setup_2nd_dtb(struct dtb *dtb, char *command_line, int on_crash)
-                        return result;
-                }
-        } else {
--               kaslr_seed = fdt64_to_cpu(*prop);
--
--               /* kaslr_seed must be wiped clean by primary
--                * kernel during boot
--                */
--               if (kaslr_seed != 0) {
--                       dbgprintf("%s: kaslr-seed is not wiped to 0.\n",
--                                       __func__);
--                       result = -EINVAL;
--                       goto on_error;
--               }
--
-                /*
-                 * Invoke the getrandom system call with
-                 * GRND_NONBLOCK, to make sure we
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0001-kexec.c-add-MFD_NOEXEC_SEAL-flag-explicitly.patch b/meta/recipes-kernel/kexec/kexec-tools/0001-kexec.c-add-MFD_NOEXEC_SEAL-flag-explicitly.patch
deleted file mode 100644
index 5d994d9ffb..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/0001-kexec.c-add-MFD_NOEXEC_SEAL-flag-explicitly.patch
+++ /dev/null
@@ -1,43 +0,0 @@
-From 0b176595ca1610037d1175e1786d1a8aff1fb43f Mon Sep 17 00:00:00 2001
-From: Chen Qi <Qi.Chen@windriver.com>
-Date: Tue, 6 Aug 2024 21:42:43 -0700
-Subject: [PATCH] kexec.c: add MFD_NOEXEC_SEAL flag explicitly
-
-Add MFD_NOEXEC_SEAL to avoid kernel warning like below:
-
-  kexec[970]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
-
-For old kernels, there will be no MFD_NOEXEC_SEAL definition, so fallback
-to define it to 0.
-
-Upstream-Status: Submitted [https://github.com/horms/kexec-tools/pull/7]
-
-Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
----
- kexec/kexec.c | 6 +++++-
- 1 file changed, 5 insertions(+), 1 deletion(-)
-
-diff --git a/kexec/kexec.c b/kexec/kexec.c
-index 6bf12d7..2f8e7cc 100644
---- a/kexec/kexec.c
-+++ b/kexec/kexec.c
-@@ -61,6 +61,10 @@
- #define KEXEC_LOADED_PATH "/sys/kernel/kexec_loaded"
- #define KEXEC_CRASH_LOADED_PATH "/sys/kernel/kexec_crash_loaded"
- 
-+#ifndef MFD_NOEXEC_SEAL
-+#define MFD_NOEXEC_SEAL 0
-+#endif
-+
- unsigned long long mem_min = 0;
- unsigned long long mem_max = ULONG_MAX;
- unsigned long elfcorehdrsz = 0;
-@@ -661,7 +665,7 @@ static int copybuf_memfd(const char *kernel_buf, size_t size)
- {
-        int fd, count;
- 
--       fd = memfd_create("kernel", MFD_ALLOW_SEALING);
-+       fd = memfd_create("kernel", MFD_ALLOW_SEALING | MFD_NOEXEC_SEAL);
-        if (fd == -1)
-                return fd;
- 
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0001-powerpc-change-the-memory-size-limit.patch b/meta/recipes-kernel/kexec/kexec-tools/0001-powerpc-change-the-memory-size-limit.patch
deleted file mode 100644
index 029650f35c..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/0001-powerpc-change-the-memory-size-limit.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From 211cae4b6a02a4d9d37bfcd76f3702696e095fc3 Mon Sep 17 00:00:00 2001
-From: Quanyang Wang <quanyang.wang@windriver.com>
-Date: Tue, 16 Jun 2015 12:59:57 +0800
-Subject: [PATCH] powerpc: change the memory size limit
-
-When run "kexec" in powerpc board, the kexec has a limit that
-the kernel text and bss size must be less than 24M. But now
-some kernel size exceed the limit. So we need to change the limit,
-else will get the error log as below:
-
-my_load:669: do
-Could not find a free area of memory of 0x12400 bytes...
-Could not find a free area of memory of 0x13000 bytes...
-locate_hole failed
-
-Upstream-Status: Pending
-
-Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
----
- kexec/arch/ppc/kexec-ppc.h | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/kexec/arch/ppc/kexec-ppc.h b/kexec/arch/ppc/kexec-ppc.h
-index 04e728e..6bae9ec 100644
---- a/kexec/arch/ppc/kexec-ppc.h
-+++ b/kexec/arch/ppc/kexec-ppc.h
-@@ -44,7 +44,7 @@ void dol_ppc_usage(void);
-  * During inital setup the kernel does not map the whole memory but a part of
-  * it. On Book-E that is 64MiB, 601 24MiB or 256MiB (if possible).
-  */
--#define KERNEL_ACCESS_TOP (24 * 1024 * 1024)
-+#define KERNEL_ACCESS_TOP (36 * 1024 * 1024)
- 
- /* boot block version 17 as defined by the linux kernel */
- struct bootblock {
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0001-ppc-fs2dt-Match-function-signatures.patch b/meta/recipes-kernel/kexec/kexec-tools/0001-ppc-fs2dt-Match-function-signatures.patch
deleted file mode 100644
index 483e5195a9..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/0001-ppc-fs2dt-Match-function-signatures.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From 4a07e8f22b4f224dca79767e5cb86a0de91498dc Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@gmail.com>
-Date: Sat, 17 May 2025 07:48:50 -0700
-Subject: [PATCH] ppc/fs2dt: Match function signatures
-
-The prototypes of function pointers is analysed and
-compiler finds the signature mismatches and complain about it.
-
-../kexec-tools-2.0.31/kexec/arch/ppc/fs2dt.c:338:44: error: incompatible function pointer types passing 'int (const void *, const void *)' to parameter of type 'int (*)(const struct dirent **, const struct dirent **)' [-Wincompatible-function-pointer-types]
-  338 |         numlist = scandir(pathname, &namelist, 0, comparefunc);
-      |                                                   ^~~~~~~~~~~
-
-Upstream-Status: Submitted [https://lore.kernel.org/kexec/20250517145852.2488183-1-raj.khem@gmail.com/T/#u]
-Signed-off-by: Khem Raj <raj.khem@gmail.com>
----
- kexec/arch/ppc/fs2dt.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/kexec/arch/ppc/fs2dt.c b/kexec/arch/ppc/fs2dt.c
-index fed499b..4952bfc 100644
---- a/kexec/arch/ppc/fs2dt.c
-+++ b/kexec/arch/ppc/fs2dt.c
-@@ -292,7 +292,7 @@ static void putprops(char *fn, struct dirent **nlist, int numlist)
-  * Compare function used to sort the device-tree directories
-  * This function will be passed to scandir.
-  */
--static int comparefunc(const void *dentry1, const void *dentry2)
-+static int comparefunc(const struct dirent ** dentry1, const struct dirent **dentry2)
- {
-        char *str1 = (*(struct dirent **)dentry1)->d_name;
-        char *str2 = (*(struct dirent **)dentry2)->d_name;
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0002-purgatory-Pass-r-directly-to-linker.patch b/meta/recipes-kernel/kexec/kexec-tools/0002-purgatory-Pass-r-directly-to-linker.patch
deleted file mode 100644
index a537ac2f0b..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/0002-purgatory-Pass-r-directly-to-linker.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From e5bc9fbd6029057a4e3815a5326af5bd83a450e6 Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@gmail.com>
-Date: Mon, 7 Sep 2015 07:59:45 +0000
-Subject: [PATCH] purgatory: Pass -r directly to linker
-
-This helps compiling with clang since -r is not a known option for clang
-where as gcc knows how to deal with it and passes it down to linker
-unfiltered
-
-Signed-off-by: Khem Raj <raj.khem@gmail.com>
-
-Upstream-Status: Pending
-
----
- purgatory/Makefile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/purgatory/Makefile b/purgatory/Makefile
-index 4d2d071..6673423 100644
---- a/purgatory/Makefile
-+++ b/purgatory/Makefile
-@@ -61,7 +61,7 @@ $(PURGATORY): CPPFLAGS=$($(ARCH)_PURGATORY_EXTRA_CFLAGS) \
-                        -I$(shell $(CC) -print-file-name=include)
- $(PURGATORY): LDFLAGS=$($(ARCH)_PURGATORY_EXTRA_CFLAGS)\
-                        -Wl,--no-undefined -nostartfiles -nostdlib \
--                       -nodefaultlibs -e purgatory_start -r \
-+                       -nodefaultlibs -e purgatory_start -Wl,-r \
-                        -Wl,-Map=$(PURGATORY_MAP)
- 
- $(PURGATORY): $(PURGATORY_OBJS)
diff --git a/meta/recipes-kernel/kexec/kexec-tools/0005-Disable-PIE-during-link.patch b/meta/recipes-kernel/kexec/kexec-tools/0005-Disable-PIE-during-link.patch
deleted file mode 100644
index 6a21744ac1..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/0005-Disable-PIE-during-link.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-From 494888bcc3bbf070dfce1b2686ee34c8619aa33d Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@gmail.com>
-Date: Sat, 10 Jun 2017 11:18:49 -0700
-Subject: [PATCH] Disable PIE during link
-
-We have explcitly disabled PIE during compile so we
-just need to match it with linker flags
-
-Upstream-Status: Pending
-
-Signed-off-by: Khem Raj <raj.khem@gmail.com>
-
----
- purgatory/Makefile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/purgatory/Makefile b/purgatory/Makefile
-index 6673423..a7405ea 100644
---- a/purgatory/Makefile
-+++ b/purgatory/Makefile
-@@ -60,7 +60,7 @@ $(PURGATORY): CPPFLAGS=$($(ARCH)_PURGATORY_EXTRA_CFLAGS) \
-                        -Iinclude \
-                        -I$(shell $(CC) -print-file-name=include)
- $(PURGATORY): LDFLAGS=$($(ARCH)_PURGATORY_EXTRA_CFLAGS)\
--                       -Wl,--no-undefined -nostartfiles -nostdlib \
-+                       -Wl,--no-undefined -no-pie -nostartfiles -nostdlib \
-                        -nodefaultlibs -e purgatory_start -Wl,-r \
-                        -Wl,-Map=$(PURGATORY_MAP)
- 
diff --git a/meta/recipes-kernel/kexec/kexec-tools/kdump b/meta/recipes-kernel/kexec/kexec-tools/kdump
deleted file mode 100755
index 69e3cafe5c..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/kdump
+++ /dev/null
@@ -1,145 +0,0 @@
-#! /bin/sh
-#
-#  kdump
-#
-#  Description: The kdump script provides the support:
-#               1. Load a kdump kernel image into memory;
-#               2. Copy away vmcore when system panic.
-#
-
-#default
-KEXEC=/usr/sbin/kexec
-KEXEC_ARGS="-p"
-
-MAKEDUMPFILE=/usr/bin/makedumpfile
-MAKEDUMPFILE_ARGS="-E -d 1"
-
-LOGGER="logger -p info -t kdump"
-
-if [ -f /etc/sysconfig/kdump.conf ]; then
-        . /etc/sysconfig/kdump.conf
-else
-        echo "no /etc/sysconfig/kdump.conf"
-        exit 1;
-fi
-
-do_check()
-{
-        #check makedumpfile
-        if [ ! -e ${MAKEDUMPFILE} -o ! -x ${MAKEDUMPFILE} ] ;then
-                echo "No makedumpfile found."
-                exit 0
-        fi
-
-        #check kexec
-        if [ ! -e ${KEXEC} -o ! -x ${KEXEC} ] ;then
-                echo "No kexec found."
-                exit 0
-        fi
-
-        #check whether kdump kernel image exists on the system
-        if [ -z "${KDUMP_KIMAGE}" -o ! -f "${KDUMP_KIMAGE}" ]; then
-                echo "No kdump kernel image found."
-                exit 0
-        fi
-
-        if [ "${KDUMP_CMDLINE}"x = "x" ] ; then
-                echo "KDUMP_CMDLINE is not configured"
-                exit 0
-        fi
-}
-
-do_save_vmcore()
-{
-        if [ ${KDUMP_VMCORE_PATH}x = x ]; then
-                KDUMP_VMCORE_PATH="/var/crash/`date +"%Y-%m-%d"`"
-        fi
-
-        mkdir -p ${KDUMP_VMCORE_PATH}
-        echo "Saving a vmcore to ${KDUMP_VMCORE_PATH}."
-
-        ${MAKEDUMPFILE} ${MAKEDUMPFILE_ARGS} /proc/vmcore ${KDUMP_VMCORE_PATH}/vmcore-"`date +"%H:%M:%S"`"
-#       cp --sparse=always /proc/vmcore ${KDUMP_VMCORE_PATH}/vmcore-"`date +"%H:%M:%S"`"
-        rc=$?
-        if [ ${rc} == 0 ]; then
-                ${LOGGER} "Saved a vmcore to ${KDUMP_VMCORE_PATH}."
-        else
-                ${LOGGER} "Failed to save vmcore!"
-        fi
-        return ${rc}
-}
-
-do_start()
-{
-        #check file
-        do_check
-
-        #check whether the running kernel supports kdump.
-        if [ ! -e /sys/kernel/kexec_crash_loaded ]; then
-                echo "Kdump isn't supported on the running kernel!!!"
-                ${LOGGER} "Kdump isn't supported on the running kernel!!!"
-                return 1
-        fi
-
-        #check whether kdump kernel image has been loaded
-        rc=`cat /sys/kernel/kexec_crash_loaded`
-        if [ ${rc} != 0 ]; then
-                echo "Kdump is already running.";
-                ${LOGGER} "Kdump is already running."
-                return 0
-        fi
-
-        #check the running kernel cmdline option,insure "crashkernel=" always set.
-        grep -q crashkernel= /proc/cmdline
-        if [ $? != 0 ]; then
-                echo "Kdump isn't supported on the running kernel,please check boot option!!!"
-                ${LOGGER} "Kdump isn't supported on the running kernel,please check boot option!!!"
-                return 1
-        fi
-
-        #Load the kdump kernel image
-        ${KEXEC} ${KEXEC_ARGS} "${KDUMP_KIMAGE}" --append="${KDUMP_CMDLINE}"
-        if [ $? != 0 ]; then
-                echo "Failed to load kdump kernel!"
-                ${LOGGER} "Failed to load kdump kernel!"
-                return 1
-        fi
-
-        echo "Kdump started up."
-        ${LOGGER} "Kdump started up."
-}
-
-do_stop()
-{
-        ${KEXEC} -p -u 2>/dev/null
-        if [ $? == 0 ]; then
-                echo "Kdump has been stopped."
-                ${LOGGER} "Kdump has been stopped."
-        else
-                echo "Failed to stop kdump!"
-                ${LOGGER} "Failed to stop kdump!"
-        fi
-}
-
-case "$1" in
-  start)
-        if [ -s /proc/vmcore ]; then
-                do_save_vmcore
-                reboot
-        else
-                do_start
-        fi
-        ;;
- restart)
-        do_stop
-        do_start
-        ;;
-  stop)
-        do_stop
-        ;;
-   *)
-        echo $"Usage: $0 {start|stop|restart}"
-        exit 1
-esac
-
-exit $?
diff --git a/meta/recipes-kernel/kexec/kexec-tools/kdump.conf b/meta/recipes-kernel/kexec/kexec-tools/kdump.conf
deleted file mode 100644
index 38190d207a..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/kdump.conf
+++ /dev/null
@@ -1,14 +0,0 @@
-#the kdump kernel version string.
-#KDUMP_KVER="`uname -r`"
-
-#this will be passed to the kdump kernel as kdump kernel command line
-#KDUMP_CMDLINE="`cat /proc/cmdline`"
-
-#the kernel image for kdump
-#KDUMP_KIMAGE="/boot/bzImage-${KDUMP_KVER}"
-
-#Where to save the vmcore
-#KDUMP_VMCORE_PATH="/var/crash/`date +"%Y-%m-%d"`"
-
-#the arguments to makedumpfile
-MAKEDUMPFILE_ARGS="--dump-dmesg -x /boot/vmlinux-`uname -r`"
diff --git a/meta/recipes-kernel/kexec/kexec-tools/kdump.service b/meta/recipes-kernel/kexec/kexec-tools/kdump.service
deleted file mode 100644
index b4a2c0611d..0000000000
--- a/meta/recipes-kernel/kexec/kexec-tools/kdump.service
+++ /dev/null
@@ -1,14 +0,0 @@
-[Unit]
-Description=Reboot and dump vmcore via kexec
-DefaultDependencies=no
-Requires=sysinit.target
-After=sysinit.target
-
-[Service]
-Type=oneshot
-RemainAfterExit=yes
-ExecStart=@LIBEXECDIR@/kdump-helper start
-ExecStop=@LIBEXECDIR@/kdump-helper stop
-
-[Install]
-WantedBy=multi-user.target