public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Tj <tj.iam.tj@proton.me>, dwmw2@infradead.org
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: crash hp: kexec_trylock() failed, kdump image may be inaccurate
Date: Mon, 12 Jan 2026 13:54:35 +0800	[thread overview]
Message-ID: <aWSMm/E1BNTMZ//a@fedora> (raw)
In-Reply-To: <M9wEb069tvcmJqpngM2EyYjyodw_HEmYt3KaW-XxRkVleH2qYeFvz16DLriKiOSRpLbPCVflvlCqhEFMZniF_Wb6YWL_gwhWAaPsHUYG2Bg=@proton.me>

On 01/07/26 at 04:43pm, Tj wrote:
> Currently debugging a KEXEC_JUMP preserve_context panic with amd iommu on kexec restart.

CC David to see if he knows this.

> 
> However, during shutdown, all but the bootstrap core (BSC) generate this message. Is it something that {c,sh}ould be silenced if the BSC CPU holds the lock (as I presume), or is it indicating a real problem because the elfheader cannot be updated? My limited understanding would suggest this should be ignored silently. From scanning the code it seems to suggest this is intended for sysfs directed CPU hotplug events.
> 
> [  141.722644] shutdown[1]: Rebooting with kexec.
> [  141.781931] Freezing user space processes
> [  141.787032] Freezing user space processes completed (elapsed 0.001 seconds)
> [  141.794028] OOM killer disabled.
> [  141.802428] pn533_usb 5-4.4:1.0: NFC: NXP PN533 NFC device disconnected
> [  142.726967] amdgpu 0000:0a:00.0: amdgpu: VCE busy: VCE_STATUS=0x100, SRBM_STATUS2=0x0
> [  142.966113] amdgpu 0000:0a:00.0: amdgpu: PCI CONFIG reset
> [  142.975667] Disabling non-boot CPUs ...
> [  143.004683] smpboot: CPU 15 is now offline
> [  143.008793] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.052741] smpboot: CPU 14 is now offline
> [  143.056894] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.088716] smpboot: CPU 13 is now offline
> [  143.092840] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.132714] smpboot: CPU 12 is now offline
> [  143.136857] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.160668] smpboot: CPU 11 is now offline
> [  143.164827] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.184791] smpboot: CPU 10 is now offline
> [  143.188924] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.208671] smpboot: CPU 9 is now offline
> [  143.212736] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.236943] smpboot: CPU 8 is now offline
> [  143.241005] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.248682] Spectre V2 : Update user space SMT mitigation: STIBP off
> [  143.280790] smpboot: CPU 7 is now offline
> [  143.284839] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.316796] smpboot: CPU 6 is now offline
> [  143.320844] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.352805] smpboot: CPU 5 is now offline
> [  143.356853] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.432608] smpboot: CPU 4 is now offline
> [  143.436642] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.468682] smpboot: CPU 3 is now offline
> [  143.472720] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.512698] smpboot: CPU 2 is now offline
> [  143.516743] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.536710] smpboot: CPU 1 is now offline
> [  143.540794] crash hp: kexec_trylock() failed, kdump image may be inaccurate
> [  143.548516] Calling amd_iommu_syscore_data_set+0x0/0x40
> [  143.553761] Checking wakeup interrupts
> [  143.557519] Calling kvm_suspend+0x0/0x30 [kvm]
> [  143.562023] Calling mce_syscore_suspend+0x0/0x30
> [  143.566655] Calling ledtrig_cpu_syscore_suspend+0x0/0x20
> [  143.571981] Calling timekeeping_syscore_suspend+0x0/0x10
> [  143.577331] Calling irq_gc_suspend+0x0/0x80
> [  143.581526] Calling ioapic_suspend+0x0/0x10
> [  143.585853] Calling i8259A_suspend+0x0/0x30
> [  143.590049] Calling perf_ibs_suspend+0x0/0x40
> [  143.594423] Calling amd_iommu_suspend+0x0/0x20
> [  143.598895] Calling fw_suspend+0x0/0x20
> [  143.602743] Calling acpi_save_bm_rld+0x0/0x30
> [  143.607118] Calling lapic_suspend+0x0/0x160
> [    0.000000] Linux version 6.19.0-rc3+debian+tj (linux@iam.tj) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #364 SMP PREEMPT_DYNAMIC Wed Jan  7 12:46:49 UTC 2026
> [    0.000000] Command line: root=/dev/mapper/SUNNY-rootfs ro debug systemd.log_level=info drm.edid_firmware=DP-2:edid/UE50NU7400.edid fbcon=rotate:3 modprobe.blacklist=radeon amdgpu.si_support=1 console=ttyS0,115200 console=tty0 no_console_suspend nosplash vt.handoff=7 pm_debug_messages=1 "dyndbg=file syscore.c +p" elfcorehdr=1032176K kexec_jump_back_entry=0x00000001ff34012b
> 
> $ grep KEXEC /boot/config-$(uname -r)
> CONFIG_KEXEC_CORE=y
> CONFIG_HAVE_IMA_KEXEC=y
> CONFIG_KEXEC=y
> CONFIG_KEXEC_FILE=y
> CONFIG_KEXEC_SIG=y
> # CONFIG_KEXEC_SIG_FORCE is not set
> CONFIG_KEXEC_BZIMAGE_VERIFY_SIG=y
> CONFIG_KEXEC_JUMP=y
> CONFIG_KEXEC_HANDOVER=y
> # CONFIG_KEXEC_HANDOVER_DEBUG is not set
> CONFIG_KEXEC_HANDOVER_DEBUGFS=y
> # CONFIG_KEXEC_HANDOVER_ENABLE_DEFAULT is not set
> CONFIG_ARCH_SUPPORTS_KEXEC=y
> CONFIG_ARCH_SUPPORTS_KEXEC_FILE=y
> CONFIG_ARCH_SELECTS_KEXEC_FILE=y
> CONFIG_ARCH_SUPPORTS_KEXEC_PURGATORY=y
> CONFIG_ARCH_SUPPORTS_KEXEC_SIG=y
> CONFIG_ARCH_SUPPORTS_KEXEC_SIG_FORCE=y
> CONFIG_ARCH_SUPPORTS_KEXEC_BZIMAGE_VERIFY_SIG=y
> CONFIG_ARCH_SUPPORTS_KEXEC_JUMP=y
> CONFIG_ARCH_SUPPORTS_KEXEC_HANDOVER=y
> # CONFIG_IMA_KEXEC is not set
> # CONFIG_TEST_KEXEC_HANDOVER is not set
> 
> Thanks for looking at this.
> 
> Tj.
> 



      reply	other threads:[~2026-01-12  5:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 16:43 crash hp: kexec_trylock() failed, kdump image may be inaccurate Tj
2026-01-12  5:54 ` Baoquan He [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=aWSMm/E1BNTMZ//a@fedora \
    --to=bhe@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=kexec@lists.infradead.org \
    --cc=tj.iam.tj@proton.me \
    /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