Several issues are noted when using Kdump on 64-bit Arm (aarch64) architecture platforms.

• Kdump fails when using Mellanox ConnectX devices

  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.

  The workaround is 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. Note that this solution is only possible if you have configured to store the vmcore file locally. If Kdump is configured to save the vmcore to a remote host via the device, this workaround fails. (Bug ID 27915989) (Bug ID 27916214)

• Kdump fails when configured to use remote dump target over an ixgbe device

  On systems where Kdump is configured to use a remote dump target over an ixgbe network device, the Kdump Vmcore Save Service is unable to save the vmcore file to the target destination. (Bug ID 27915827)

• 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)