Flashes (Alerts)
Abstract
If a hard lockup crashes the system, then Kdump can fail to collect the memory dump during a memory hot plug operation.
Content
Linux Release Affected
SUSE Linux Enterprise Server (SLES) 16
IBM Systems Affected
Power Systems with panic on hard lockup enabled.
Symptoms
The kernel crashes and the system hangs with the following message on the console:
Call Trace
__list_del_entry_valid_or_report+0xdc/0x128 (unreliable)
move_freepages_block_isolate+0x50c/0x520
set_migratetype_isolate+0x210/0x4a0
isolate_single_pageblock.isra.0+0x1d8/0x2e0
start_isolate_page_range+0xd0/0x2c0
offline_pages+0x240/0x790
memory_subsys_offline+0x18c/0x2b0
device_offline+0x124/0x1d0
state_store+0xc4/0x130
dev_attr_store+0x34/0x50
sysfs_kf_write+0x64/0x80
kernfs_fop_write_iter+0x19c/0x2a0
vfs_write+0x220/0x500
ksys_write+0x88/0x150
system_call_exception+0x12c/0x240
system_call_vectored_common+0x15c/0x2ec
--- interrupt: 3000 at 0x7fff98d45de4
NIP: 00007fff98d45de4 LR: 00007fff98d45de4 CTR: 0000000000000000
REGS: c0000002644efe80 TRAP: 3000 Not tainted (6.12.0-160000.5-default)
MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 44004422 XER: 00000000
<snip>
--- interrupt: 3000
<snip>
---[ end trace 0000000000000000 ]---
pstore: backend (nvram) writing error (-1)
Workaround
Using firmware-assisted dump (FADump) as an alternative mechanism for memory dump collection can prevent this issue.
Fix outlook
SLES 16.1
I/O device impacted
None
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SGMV168","label":"IBM Support for SUSE Linux Enterprise Server"},"ARM Category":[{"code":"a8m0z000000GnlCAAS","label":"SUSE Linux Enterprise Server"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0.0;12.0.0;15.0.0"}]
Was this topic helpful?
Document Information
Modified date:
10 November 2025
UID
ibm17245180