[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <297b268a-85de-bc8c-88eb-b8d050ac1ec3@kernel.org>
Date: Tue, 14 Jun 2022 07:15:48 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Alexandru Elisei <alexandru.elisei@....com>,
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
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit
10e14073107d
On 13. 06. 22, 18:54, Alexandru Elisei wrote:
> I've booted a kernel compiled with CONFIG_PROVE_LOCKING=y, as the offending
> commit fiddles with locks, but no splat was produced that would explain the
> hang.
It's too early for lockdep. Could you try to move lockdep_init() before
console_init() in start_kernel()?
You'd need to use early console (which you already do).
thanks,
--
js
suse labs
Powered by blists - more mailing lists