linux-kernel - Re: kernel hang during reboot when cmdline include a non-exist console device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YS2fZ1sknFYKtJFi@google.com>
Date:   Tue, 31 Aug 2021 12:17:59 +0900
From:   Sergey Senozhatsky <senozhatsky@...omium.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <senozhatsky@...omium.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

On (21/08/30 19:53), Linus Torvalds wrote:
> 
> There's a bugzilla for this, but let's just move it to reguilar email,
> unless some of you want to track it that way.
> 
> The bugzilla entry says
> 
>   "When reboot， the capslock key of thinkpad x1 starts blinking"
> 
> which sounds like there's an oops that just isn't showing, quite
> possibly because the console has already been shut down.
> 
> I didn't test this out, and would sincerely hope that somebody else is
> willing to follow up on it since I'm in the busiest part of the merge
> window.

[..]

> > https://bugzilla.kernel.org/show_bug.cgi?id=214201

I think normally wrong/empty console boot argument should not cause
problems. We have a huge number of devices that use console="", for
instance. But on some hardware this triggers panic(), very early on.

I have the same symptoms on my laptop, and so far haven't been able
to figure out how to track it down, but I need to re-start my investigation.

In the meantime, we had a series [0] but ended up reverting it.
I think we need to revisit it, namely the part that starts with [1].

[0] https://lore.kernel.org/lkml/20201111135450.11214-1-pmladek@suse.com/
[1] https://lore.kernel.org/lkml/X%2FfWGjYI5LapMdGW@jagdpanzerIV.localdomain/