1. Release Notes for Unbreakable Enterprise Kernel Release 5 Update 4
  2. Known Issues
  3. [aarch64] Kdump issues

[aarch64] Kdump issues

Note the following issues when using Kdump on the 64-bit Arm (aarch64) architecture.

  • Kdump fails when using Mellanox ConnectX devices with a remote target

    On systems with Mellanox hardware devices that use either the mlx4_core or the mlx5_core driver modules, Kexec fails to load the crash kernel and hangs while the mlx4_core or mlx5_core driver is initialized if a remote dump target is used.

    The workaround is to either store the vmcore file locally or to disable loading the driver in the crash kernel by adding either rd.driver.blacklist=mlx4_core or rd.driver.blacklist=mlx5_core to the KDUMP_COMMANDLINE_APPEND option in /etc/sysconfig/kdump. (Bug IDs 27915989 and 27916214)

  • Kdump fails and hangs when configured to use a remote dump target over an igb device

    On systems where Kdump is configured to use a remote dump target over an igb network device, NETDEV WATCHDOG returns a timeout error and the network adapter is continually reset, resulting in a system hang when kexec attempts to load the crash kernel. (Bug ID 27916095)

  • Kdump might fail on some AMD hardware

    Kdump might fail on some AMD hardware that is running UEK R5U4 kernel. Impacted hardware includes the AMD EPYC CPU (codename Naples and Rome) servers.

    To work around this issue, modify the /etc/sysconfig/kdump configuration file, remove the "iommu=off" command-line option from KDUMP_COMMANDLINE_APPEND, then restart the kdump service for the changes to take effect.

    (Bug ID 31127379)