System hangs after displaying "systemd-journald[xx]: Received SIGTERM from PID 1 (systemd)"

Solution Verified - Updated -

Issue

  • System hangs after switching root as shown below

    [  OK  ] Reached target Switch Root.
    [  OK  ] Started Plymouth switch root service.
        Starting Switch Root...
    [   4.918903] systemd-journald[xx]: Received SIGTERM from PID 1 (systemd)
    
  • Booting an older kernel doesn't solve the issue

  • When serial console is configured, the serial console shows the following stack trace ((timestamps may vary))

    [    4.948513] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
    [    4.948513] 
    [    4.952201] CPU: 0 PID: 1 Comm: systemd Not tainted 3.10.0-957.5.1.el7.x86_64 #1
    [    4.955057] Hardware name: XXX
    [    4.957592] Call Trace:
    [    4.958917]  [<ffffffffa6361e41>] dump_stack+0x19/0x1b
    [    4.961080]  [<ffffffffa635b550>] panic+0xe8/0x21f
    [    4.963215]  [<ffffffffa5c9e406>] do_exit+0xa36/0xa40
    [    4.965744]  [<ffffffffa5c9e48f>] do_group_exit+0x3f/0xa0
    [    4.968339]  [<ffffffffa5c9e504>] SyS_exit_group+0x14/0x20
    [    4.971171]  [<ffffffffa6374ddb>] system_call_fastpath+0x22/0x27    
    

Environment

  • Red Hat Enterprise Linux 7
    • systemd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content