[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YqikqHUv51PXOjwq@google.com>
Date: Wed, 15 Jun 2022 00:09:28 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Alexandru Elisei <alexandru.elisei@....com>
Cc: sunjunchao2870@...il.com, jack@...e.cz, viro@...iv.linux.org.uk,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
pmladek@...e.com, senozhatsky@...omium.org, rostedt@...dmis.org,
john.ogness@...utronix.de, keescook@...omium.org, anton@...msg.org,
ccross@...roid.com, tony.luck@...el.com, heiko@...ech.de,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, maco@...roid.com, hch@....de,
gregkh@...uxfoundation.org, jirislaby@...nel.org,
suzuki.poulose@....com
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit
10e14073107d
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.
Powered by blists - more mailing lists