Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
  • linux
  • kernel
  • panic.c
Find file BlameHistoryPermalink
  • Aaro Koskinen's avatar
    panic: Fix panic message visibility by calling bust_spinlocks(0) before dying · d014e889
    Aaro Koskinen authored Oct 02, 2009
    Commit ffd71da4
    
     ("panic: decrease oops_in_progress only after
    having done the panic") moved bust_spinlocks(0) to the end of the
    function, which in practice is never reached.
    
    As a result console_unblank() is not called, and on some systems
    the user may not see the panic message.
    
    Move it back up to before the unblanking.
    
    Signed-off-by: default avatarAaro Koskinen <aaro.koskinen@nokia.com>
    Reviewed-by: default avatarFrederic Weisbecker <fweisbec@gmail.com>
    LKML-Reference: <1254483680-25578-1-git-send-email-aaro.koskinen@nokia.com>
    Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
    d014e889
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7