99-kdump.conf: Omit xe driver in kdump initramfs - #164
Open
rajucheerla wants to merge 1 commit into
Open
Conversation
Kdump fails with OOM during device probe in the secondary kernel because of the 'xe' driver. Specifically on Intel platforms (Panther Lake), the driver loads multiple required firmware binaries (guc, huc, gsc) which require more memory, leading to OOM under default crashkernel reservations. Furthermore, even if crashkernel memory is increased, the xe driver leaves the secondary kernel in an unstable condition, causing the kdump kernel to panic during shutdown after vmcore collection (e.g., "Kernel panic - not syncing: DMAR hardware is malfunctioning"). Since GPU display capability is unnecessary for dump capture, omit the 'xe' driver from the kdump initramfs. This allows the crash kernel to boot with default memory reservation and complete vmcore collection and system reboot cleanly. Resolves: RHEL-234472 Signed-off-by: Raju Cheerla <rcheerla@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Kdump fails with OOM during device probe in the secondary kernel because of the 'xe' driver. Specifically on Intel platforms (Panther Lake), the driver loads multiple required firmware binaries (guc, huc, gsc) which require more memory, leading to OOM under default crashkernel reservations.
Furthermore, even if crashkernel memory is increased, the xe driver leaves the secondary kernel in an unstable condition, causing the kdump kernel to panic during shutdown after vmcore collection (e.g., "Kernel panic - not syncing: DMAR hardware is malfunctioning").
Since GPU display capability is unnecessary for dump capture, omit the 'xe' driver from the kdump initramfs. This allows the crash kernel to boot with default memory reservation and complete vmcore collection and system reboot cleanly.
Resolves: RHEL-234472