When kdump is configured in the Linux OS, an error message is displayed indicating that the service fails to start.
The size and start position of crashkernel are specified when kdump is configured for some documents, as shown in the following figure.
However, the kdump service cannot be started after the configuration, as shown in the following figure.
The error persists after a system restarting, and the following error information is recorded in the kernel log:
Based on the log, the memory space for kdump cannot be reserved during the startup. Therefore, the kdump service cannot be started.
The reason is that the 128M@16M parameter is used when the memory space is specified. Because the system occupies the memory space starting from 16 MB, the memory space cannot be reserved for kdump.
To prevent this error, you are advised not to set the start position of the reserved memory, that is, keep the parameter as crashkernel=128M. You can also change 16M to another value, for example, crashkernel=128M@64M.
Follow the troubleshooting procedure described in the handling process.