From: Petr Mladek <pmladek@suse.com>
To: James Wang <jnwang@linux.alibaba.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel hang during reboot when cmdline include a non-exist console device
Date: Tue, 31 Aug 2021 16:33:52 +0200 [thread overview]
Message-ID: <YS490P27YM6UlB2z@alley> (raw)
In-Reply-To: <fc18d17a-b185-7a1e-2135-ec83f3f8c70f@linux.alibaba.com>
On Tue 2021-08-31 21:45:05, James Wang wrote:
>
> 在 2021/8/31 PM4:47, Sergey Senozhatsky 写道:
> > And may I ask, just in case, if James can revert a revert of Petr's commit:
> >
> > revert a91bd6223ecd46addc71ee6fcd432206d39365d2
> >
> > boot with wrong console argument and see if the kernel reboots without
> > any problems.
>
> After test, revert Petr's commit can work; reboot without any problem;
Interesting, it looks like the panic() is really caused by missing
stdout, stdin, and stderr, for the init process.
Unfortunately, the fix is not easy, as described in the commit
a91bd6223ecd46addc71e ("Revert "init/console: Use ttynull as
a fallback when there is no console").
Best Regards,
Petr
next prev parent reply other threads:[~2021-08-31 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 2:53 kernel hang during reboot when cmdline include a non-exist console device Linus Torvalds
2021-08-31 3:17 ` Sergey Senozhatsky
2021-08-31 7:34 ` John Ogness
2021-08-31 8:14 ` Petr Mladek
2021-08-31 8:31 ` James Wang
2021-08-31 8:47 ` Sergey Senozhatsky
2021-08-31 13:45 ` James Wang
2021-08-31 14:33 ` Petr Mladek [this message]
2021-08-31 14:38 ` James Wang
2021-08-31 14:52 ` Petr Mladek
2021-09-01 1:52 ` James Wang
2021-09-01 11:48 ` Petr Mladek
2021-09-01 13:53 ` James Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YS490P27YM6UlB2z@alley \
--to=pmladek@suse.com \
--cc=jnwang@linux.alibaba.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).