Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-84824

Local dumping failed with crashkernel=256M for RHCOS 4.18.1

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • rhel-9.7
    • kexec-tools
    • None
    • No
    • Moderate
    • rhel-kernel-debug
    • ssg_core_kernel
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      Local dumping failed with crashkernel=256M,

      [    1.097354] Run /init as init process
      /usr/bin/sh: error while loading shared libraries: libtinfo.so.6: cannot open shared object file: No such file or directory
      [    1.099622] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
      [    1.100420] CPU: 0 PID: 1 Comm: init Not tainted 5.14.0-427.50.1.el9_4.x86_64 #1
      ...
      

      What is the impact of this issue to you?

      All kinds of vmcore dumping will fail for RHCOS with RAM < 64G.

      Please provide the package NVR for which the bug is seen:

      kexec-tools-2.0.27-8.el9_4.3.x86_64

      How reproducible is this bug?:

      always

      Steps to reproduce

      1. Download and boot RHCOS
      2. rpm-ostree kargs --apend=crashkernel=256M
      3. systemctl reboot
      4. systemctl enable --now kdump
      5. echo c > /proc/sysrq-trigger

      Expected results

      kdump works.

      Actual results

      kdump failed.

              rh-ee-lichliu Lichen Liu
              coxu@redhat.com Coiby Xu
              kdump team kdump team
              kdump team kdump team
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: