On IBM Power Systems, *kdump* fails if *fadump* was used previously and both use a network target

Solution In Progress - Updated -

Issue

  • The kdump kernel crash dumping mechanism will fail to save dumps to a network location if the same system was previously configured to instead use firmware-assisted dumping (fadump) and also save dumps remotely. This is because when the mechanism is switched back to kdump, the kdump- prefix is added to the configured network interface, but configuring fadump already added the same prefix before. The resulting interface name becomes kdump-kdump-eth0, and the final 0 is then truncated. This results in an invalid interface name kdump-kdump-eth, and kdump then fails to access the interface and save crash dumps to a remote target.

Environment

  • Red Hat Enterprise Linux(RHEL) 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.