From: Jan Kara <jack@suse.cz>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: Petr Mladek <pmladek@suse.com>,
jack@suse.cz, 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
Date: Wed, 15 Jun 2022 18:39:49 +0200 [thread overview]
Message-ID: <20220615163949.z22puioui322ktla@quack3.lan> (raw)
In-Reply-To: <YqnVWCYx0L2RlckB@monolith.localdoman>
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@suse.com>
SUSE Labs, CR
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-06-15 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 16:54 [BUG] rockpro64 board hangs in console_init() after commit 10e14073107d Alexandru Elisei
2022-06-14 2:51 ` Sergey Senozhatsky
2022-06-14 5:15 ` Jiri Slaby
2022-06-14 6:52 ` Jiri Slaby
2022-06-14 12:23 ` Petr Mladek
2022-06-14 13:23 ` Alexandru Elisei
2022-06-14 15:00 ` Petr Mladek
2022-06-15 12:50 ` Alexandru Elisei
2022-06-15 16:39 ` Jan Kara [this message]
2022-06-15 16:49 ` Alexandru Elisei
2022-06-15 21:22 ` Jan Kara
2022-06-14 13:58 ` Jan Kara
2022-06-14 14:53 ` Alexandru Elisei
2022-06-14 15:09 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220615163949.z22puioui322ktla@quack3.lan \
--to=jack@suse.cz \
--cc=alexandru.elisei@arm.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=heiko@sntech.de \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maco@android.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sunjunchao2870@gmail.com \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox