Skip to content

Commit

Permalink
Remove 'vm.panic_on_oom=1' (#7678)
Browse files Browse the repository at this point in the history
#### 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 '
  • Loading branch information
shlomibitton authored May 25, 2021
1 parent 6f884b7 commit 9930e73
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion files/image_config/kdump/vmcore-sysctl.conf
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,3 @@ kernel.panic_on_io_nmi=1
kernel.panic_on_stackoverflow=1
kernel.hung_task_panic=1
kernel.unknown_nmi_panic=1
vm.panic_on_oom=1

0 comments on commit 9930e73

Please sign in to comment.