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

Vmcore dumping to remote fs failed because of kernel panic caused by insufficient crashkernel

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

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • rhel-9.7
    • rhel-9.6
    • kexec-tools
    • None
    • kexec-tools-2.0.29-7.el9
    • No
    • Moderate
    • 1
    • rhel-kernel-debug
    • ssg_core_kernel
    • 11
    • 13
    • 1
    • Dev ack
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • CK-March-2025
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

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

      Dumping vmcore to remote fs failed for systems with RAM < 4G,

      [    1.071864] Run /init as init process
      [    1.072674] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
      ...
      

      What is the impact of this issue to you?

      Dumping vmcore to remote fs will fail with RAM < 4G.

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

      kexec-tools-2.0.29-5.el9.x86_64

      How reproducible is this bug?:

      always

      Steps to reproduce

      1.  Set up NFS dumping
      2.  Trigger a kernel crash

      Expected results

      Dumping vmcore to remote fs works.

      Actual results

      Dumping vmcore to remote fs failed,

      [  468.264036] sysrq: Trigger a crash
      [  468.264092] Kernel panic - not syncing: sysrq triggered crash
      [  468.265324] CPU: 1 PID: 1220 Comm: bash Kdump: loaded Not tainted 5.14.0-545.el9.x86_64 #1
      ...
      [    1.071864] Run /init as init process
      [    1.072674] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
      [    1.073729] CPU: 0 PID: 1 Comm: init Not tainted 5.14.0-545.el9.x86_64 #1
      [    1.074651] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-3.fc41 04/01/2014
      [    1.075810] Call Trace:
      [    1.076154]  <TASK>
      [    1.076455]  dump_stack_lvl+0x34/0x48
      [    1.076962]  panic+0x107/0x2bb
      [    1.077392]  do_exit.cold+0x15/0x15
      [    1.077873]  do_group_exit+0x2d/0x90
      [    1.078372]  get_signal+0x839/0x860
      [    1.078854]  arch_do_signal_or_restart+0x25/0x100
      [    1.079498]  ? force_sig_info_to_task+0xdd/0x110
      [    1.080133]  exit_to_user_mode_loop+0x9c/0x130
      [    1.080743]  exit_to_user_mode_prepare+0xb9/0x100
      [    1.081391]  irqentry_exit_to_user_mode+0x5/0x30
      [    1.082023]  asm_exc_page_fault+0x22/0x30
      [    1.082574] RIP: 0033:0x7f18fefb7e1a
      [    1.083066] Code: 0f 61 c0 66 0f 70 c0 00 48 83 fa 10 0f 82 7e 00 00 00 48 83 fa 20 77 12 0f 11 44 17 f0 0f 11 07 c3 0f 11 47 e0 0f 11 47 f0 c3 <0f> 11 07 0f 11 47 10 48 01 d7 48 83 fa 4
      0 76 e7 0f 11 40 20 0f 11
      [    1.085592] RSP: 002b:00007ffc2e5d3cf8 EFLAGS: 00010202
      [    1.086306] RAX: 00007f18fef8f4e0 RBX: 0000000000000004 RCX: 00007f18fef8f970
      [    1.087271] RDX: 0000000000000490 RSI: 0000000000000000 RDI: 00007f18fef8f4e0
      [    1.088232] RBP: 00007ffc2e5d4060 R08: 00007f18fef8f4e0 R09: 000000000002a000
      [    1.089195] R10: 0000000000000003 R11: 0000000000000206 R12: 00007ffc2e5d3d90
      [    1.090168] R13: 00007ffc2e5d4100 R14: 00007f18fef8f970 R15: 00007f18fef90000
      [    1.091141]  </TASK>
      [    1.091475] Kernel Offset: disabled
      [    1.092903] Rebooting in 10 seconds..
      

      Additional notes

      1. To fix RHEL-53364, the dracut fips module is now enabled unconditionally. If FIPS is disabled, the current default crashkernel value still works.

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

                Created:
                Updated: