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 23:22:06 +0200
From:   Jan Kara <jack@suse.cz>
To:     Alexandru Elisei <alexandru.elisei@arm.com>
Cc:     Jan Kara <jack@suse.cz>, Petr Mladek <pmladek@suse.com>,
        sunjunchao2870@gmail.com, viro@zeniv.linux.org.uk,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        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
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit
 10e14073107d
Message-ID: <20220615212206.ykqvui4tthpfme2u@quack3.lan>
References: <Yqdry+IghSWnJ6pe@monolith.localdoman>
 <Yqh9xIwBVcabpSLe@alley>
 <YqiJH1phG/LWu9bs@monolith.localdoman>
 <YqiidNPMUZQPRIvy@alley>
 <YqnVWCYx0L2RlckB@monolith.localdoman>
 <20220615163949.z22puioui322ktla@quack3.lan>
 <YqoNtvyZA2s4cSgW@monolith.localdoman>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YqoNtvyZA2s4cSgW@monolith.localdoman>
Precedence: bulk

On Wed 15-06-22 17:49:58, Alexandru Elisei wrote:
> 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@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
> 
> The patch works for me, thank you!

Thanks for testing!
 
> Do you also need me to reply to the discussion?

No, I don't need that.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR