[kdump] Remove vm.panic_on_oom=1 to change it back to 2#7678
Merged
qiluo-msft merged 1 commit intosonic-net:masterfrom May 25, 2021
shlomibitton:shlomi_kernel_oom
Merged
[kdump] Remove vm.panic_on_oom=1 to change it back to 2#7678qiluo-msft merged 1 commit intosonic-net:masterfrom shlomibitton:shlomi_kernel_oom
qiluo-msft merged 1 commit intosonic-net:masterfrom
shlomibitton:shlomi_kernel_oom
Conversation
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
lguohan
approved these changes
May 23, 2021
yxieca
pushed a commit
that referenced
this pull request
May 26, 2021
#### Why I did it If a process limits using nodes by mempolicy/cpusets, and those nodes become memory exhaustion status, one process may be killed by oom-killer. No panic occurs in this case, because other node's memory may be free. This means system total status may be not fatal yet. #### How I did it Remove 'vm.panic_on_oom=1' kernel flag from 'vmcore-sysctl.conf '
carl-nokia
pushed a commit
to carl-nokia/sonic-buildimage
that referenced
this pull request
Aug 7, 2021
#### Why I did it If a process limits using nodes by mempolicy/cpusets, and those nodes become memory exhaustion status, one process may be killed by oom-killer. No panic occurs in this case, because other node's memory may be free. This means system total status may be not fatal yet. #### How I did it Remove 'vm.panic_on_oom=1' kernel flag from 'vmcore-sysctl.conf '
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
4 participants
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.
Signed-off-by: Shlomi Bitton shlomibi@nvidia.com
Why I did it
If a process limits using nodes by mempolicy/cpusets, and those nodes become memory exhaustion status, one process may be killed by oom-killer.
No panic occurs in this case, because other node's memory may be free.
This means system total status may be not fatal yet.
How I did it
Remove 'vm.panic_on_oom=1' kernel flag from 'vmcore-sysctl.conf '
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)