Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-ae
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-ae
  • Repository
Switch branch/tag
  • linux-ae
  • Documentation
  • kernel-parameters.txt
Find file BlameHistoryPermalink
  • Masami Hiramatsu's avatar
    kernel/panic.c: add "crash_kexec_post_notifiers" option for kdump after panic_notifers · f06e5153
    Masami Hiramatsu authored Jun 06, 2014
    
    
    Add a "crash_kexec_post_notifiers" boot option to run kdump after
    running panic_notifiers and dump kmsg.  This can help rare situations
    where kdump fails because of unstable crashed kernel or hardware failure
    (memory corruption on critical data/code), or the 2nd kernel is already
    broken by the 1st kernel (it's a broken behavior, but who can guarantee
    that the "crashed" kernel works correctly?).
    
    Usage: add "crash_kexec_post_notifiers" to kernel boot option.
    
    Note that this actually increases risks of the failure of kdump.  This
    option should be set only if you worry about the rare case of kdump
    failure rather than increasing the chance of success.
    
    Signed-off-by: default avatarMasami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
    Acked-by: default avatarMotohiro Kosaki <Motohiro.Kosaki@us.fujitsu.com>
    Acked-by: default avatarVivek Goyal <vgoyal@redhat.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
    Cc: Satoru MORIYA <satoru.moriya.br@hitachi.com>
    Cc: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
    Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
    Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    f06e5153