Hi, On Wed, Jun 15, 2022 at 06:39:49PM +0200, Jan Kara wrote: > 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@xxxxxxx/ > > 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@xxxxxxxxxx The patch works for me, thank you! Do you also need me to reply to the discussion? Alex > > Honza > > -- > Jan Kara <jack@xxxxxxxx> > SUSE Labs, CR
