[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220615163949.z22puioui322ktla@quack3.lan>
Date: Wed, 15 Jun 2022 18:39:49 +0200
From: Jan Kara <jack@...e.cz>
To: Alexandru Elisei <alexandru.elisei@....com>
Cc: Petr Mladek <pmladek@...e.com>, jack@...e.cz,
sunjunchao2870@...il.com, viro@...iv.linux.org.uk,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
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
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit
10e14073107d
Hi Alexandru!
On Wed 15-06-22 13:50:24, Alexandru Elisei wrote:
> On Tue, Jun 14, 2022 at 05:00:04PM +0200, Petr Mladek 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. I've also tried to boot a v5,19-rc2 kernel on my odroid-c4, the board
> > > > > is booting just fine, so I'm guessing it only affects of subset of arm64
> > > > > boards.
> > > >
> > > > You might try to switch the order of console_init() and lockdep_init()
> > > > in start_kernel() in init/main.c
> > >
> > > Did so above.
> >
> > Unfortunately, it did not print anything :-(
>
> With this patch [1] I was able to succefully boot the board. So I guess
> problem should be fixed.
>
> [1] https://lore.kernel.org/all/20220614124618.2830569-1-suzuki.poulose@arm.com/
Can you please try booting with the patch I've posted at [2]? After some
discussion with Linus that would be a preferable fix... Thanks!
[2] https://lore.kernel.org/all/20220615133845.o2lzfe5s4dzdfvtg@quack3.lan
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists