Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 15 Jun 2022 00:09:28 +0900
From:   Sergey Senozhatsky <senozhatsky@chromium.org>
To:     Alexandru Elisei <alexandru.elisei@arm.com>
Cc:     sunjunchao2870@gmail.com, jack@suse.cz, viro@zeniv.linux.org.uk,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        pmladek@suse.com, senozhatsky@chromium.org, rostedt@goodmis.org,
        john.ogness@linutronix.de, keescook@chromium.org, anton@enomsg.org,
        ccross@android.com, tony.luck@intel.com, heiko@sntech.de,
        linux-arm-kernel@lists.infradead.org,
        linux-rockchip@lists.infradead.org, maco@android.com, hch@lst.de,
        gregkh@linuxfoundation.org, jirislaby@kernel.org,
        suzuki.poulose@arm.com
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit
 10e14073107d
Message-ID: <YqikqHUv51PXOjwq@google.com>
References: <Yqdry+IghSWnJ6pe@monolith.localdoman>
 <Yqigw6vu6RYBIqHK@monolith.localdoman>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Yqigw6vu6RYBIqHK@monolith.localdoman>
Precedence: bulk

On (22/06/14 15:53), Alexandru Elisei wrote:
> (+Suzuki)
>
> I was able to boot the board after applying this patch from Suzuki [1].

OK, so the board actually boots to panic and the issue is that printk
does not flush panic messages. I think Petr has a patch for it.