[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e66f501a-0ba9-77f1-b5a2-9a759f8e00d6@linux.alibaba.com>
Date: Tue, 31 Aug 2021 22:38:42 +0800
From: James Wang <jnwang@...ux.alibaba.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kernel hang during reboot when cmdline include a non-exist
console device
在 2021/8/31 PM10:33, Petr Mladek 写道:
> 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").
OK. But I suppose you could find a quick workaround to mitigate this issue.
James
Powered by blists - more mailing lists