[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7d512002-e33c-198f-52df-a89a30bc665b@roeck-us.net>
Date: Tue, 6 Oct 2020 07:22:54 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Petr Mladek <pmladek@...e.com>
Cc: Shreyas Joshi <shreyas.joshi@...mp.com>, rostedt@...dmis.org,
shreyasjoshi15@...il.com, linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] printk: handle blank console arguments passed in.
On 10/6/20 6:33 AM, Sergey Senozhatsky wrote:
> On (20/10/06 11:54), Petr Mladek wrote:
>> On Tue 2020-10-06 15:59:07, Sergey Senozhatsky wrote:
>>> On (20/10/05 20:35), Guenter Roeck wrote:
>>>> On a side note, I don't see the problem presumably fixed with this
>>>> patch in any of my tests.
>>>
>>> Hmm. This is rather interesting. Empty console= certainly oops-es my laptop,
>>
>> Just by chance. Do you have any log with the Oops? Or does it die
>> silently?
>
> The laptop in question has fbdev and no serial. It dies with blank screen.
> I'll try to dig it and get some backtrace or anything useful.
>
Some versions of systemd (and possibly other distributions) apparently
react allergic if no console is present. See [1]. Maybe that is what
happens with your laptop ?
That exchange leads to the question what should be done with /dev/console
if there is no console. On Chromebooks we see an error when trying
to open it if I recall correctly.
Guenter
---
[1] https://github.com/systemd/systemd/issues/13332
Powered by blists - more mailing lists