From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: sunjunchao2870@gmail.com, jack@suse.cz, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
pmladek@suse.com, 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: Tue, 14 Jun 2022 11:51:19 +0900 [thread overview]
Message-ID: <Yqf3pxG16lQcacUA@google.com> (raw)
In-Reply-To: <Yqdry+IghSWnJ6pe@monolith.localdoman>
On (22/06/13 17:54), Alexandru Elisei wrote:
[..]
> [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
> [ 0.000001] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
> [ 0.005107] Console: colour dummy device 80x25
> [ 0.005549] printk: console [tty0] enabled
> [ 0.005956] printk: bootconsole [uart0] disabled
>
> Config can be found at [1] (expires after 6 months). I've also built the
> kernel with gcc 10.3.1 [2] (aarch64-none-linux-gnu), same issue.
>
> I've bisected the build failure to commit 10e14073107d ("writeback: Fix
> inode->i_io_list not be protected by inode->i_lock error"); I've confirmed
> that that commit is responsible by successfully booting the board with a
> kernel built from v5.19-rc2 + the above commit reverted.
Hmm, interesting and puzzling.
If you disable console kthreads (__printk_fallback_preferred_direct) and
keep 10e14073107d, are you able to successfully boot the board or does it
boot to a panic?
> I tried to do some investigating, it seems that the kernel is stuck at
> printk.c::console_init() -> drivers/tty/vt/vt.c::con_init() ->
> printk.c::register_console() -> unregister_console() -> console_lock().
Is it console lock (console_kthreads_block() -> mutex_lock(&con->lock))
that we cannot grab or is it console semaphore?
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: sunjunchao2870@gmail.com, jack@suse.cz, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
pmladek@suse.com, 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: Tue, 14 Jun 2022 11:51:19 +0900 [thread overview]
Message-ID: <Yqf3pxG16lQcacUA@google.com> (raw)
In-Reply-To: <Yqdry+IghSWnJ6pe@monolith.localdoman>
On (22/06/13 17:54), Alexandru Elisei wrote:
[..]
> [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
> [ 0.000001] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
> [ 0.005107] Console: colour dummy device 80x25
> [ 0.005549] printk: console [tty0] enabled
> [ 0.005956] printk: bootconsole [uart0] disabled
>
> Config can be found at [1] (expires after 6 months). I've also built the
> kernel with gcc 10.3.1 [2] (aarch64-none-linux-gnu), same issue.
>
> I've bisected the build failure to commit 10e14073107d ("writeback: Fix
> inode->i_io_list not be protected by inode->i_lock error"); I've confirmed
> that that commit is responsible by successfully booting the board with a
> kernel built from v5.19-rc2 + the above commit reverted.
Hmm, interesting and puzzling.
If you disable console kthreads (__printk_fallback_preferred_direct) and
keep 10e14073107d, are you able to successfully boot the board or does it
boot to a panic?
> I tried to do some investigating, it seems that the kernel is stuck at
> printk.c::console_init() -> drivers/tty/vt/vt.c::con_init() ->
> printk.c::register_console() -> unregister_console() -> console_lock().
Is it console lock (console_kthreads_block() -> mutex_lock(&con->lock))
that we cannot grab or is it console semaphore?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: sunjunchao2870@gmail.com, jack@suse.cz, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
pmladek@suse.com, 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: Tue, 14 Jun 2022 11:51:19 +0900 [thread overview]
Message-ID: <Yqf3pxG16lQcacUA@google.com> (raw)
In-Reply-To: <Yqdry+IghSWnJ6pe@monolith.localdoman>
On (22/06/13 17:54), Alexandru Elisei wrote:
[..]
> [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
> [ 0.000001] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
> [ 0.005107] Console: colour dummy device 80x25
> [ 0.005549] printk: console [tty0] enabled
> [ 0.005956] printk: bootconsole [uart0] disabled
>
> Config can be found at [1] (expires after 6 months). I've also built the
> kernel with gcc 10.3.1 [2] (aarch64-none-linux-gnu), same issue.
>
> I've bisected the build failure to commit 10e14073107d ("writeback: Fix
> inode->i_io_list not be protected by inode->i_lock error"); I've confirmed
> that that commit is responsible by successfully booting the board with a
> kernel built from v5.19-rc2 + the above commit reverted.
Hmm, interesting and puzzling.
If you disable console kthreads (__printk_fallback_preferred_direct) and
keep 10e14073107d, are you able to successfully boot the board or does it
boot to a panic?
> I tried to do some investigating, it seems that the kernel is stuck at
> printk.c::console_init() -> drivers/tty/vt/vt.c::con_init() ->
> printk.c::register_console() -> unregister_console() -> console_lock().
Is it console lock (console_kthreads_block() -> mutex_lock(&con->lock))
that we cannot grab or is it console semaphore?
next prev parent reply other threads:[~2022-06-14 2:51 UTC|newest]
Thread overview: 42+ 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-13 16:54 ` Alexandru Elisei
2022-06-13 16:54 ` Alexandru Elisei
2022-06-14 2:51 ` Sergey Senozhatsky [this message]
2022-06-14 2:51 ` Sergey Senozhatsky
2022-06-14 2:51 ` Sergey Senozhatsky
2022-06-14 5:15 ` Jiri Slaby
2022-06-14 5:15 ` Jiri Slaby
2022-06-14 5:15 ` Jiri Slaby
2022-06-14 6:52 ` Jiri Slaby
2022-06-14 6:52 ` Jiri Slaby
2022-06-14 6:52 ` Jiri Slaby
2022-06-14 12:23 ` Petr Mladek
2022-06-14 12:23 ` Petr Mladek
2022-06-14 12:23 ` Petr Mladek
2022-06-14 13:23 ` Alexandru Elisei
2022-06-14 13:23 ` Alexandru Elisei
2022-06-14 13:23 ` Alexandru Elisei
2022-06-14 15:00 ` Petr Mladek
2022-06-14 15:00 ` Petr Mladek
2022-06-14 15:00 ` Petr Mladek
2022-06-15 12:50 ` Alexandru Elisei
2022-06-15 12:50 ` Alexandru Elisei
2022-06-15 12:50 ` Alexandru Elisei
2022-06-15 16:39 ` Jan Kara
2022-06-15 16:39 ` Jan Kara
2022-06-15 16:39 ` Jan Kara
2022-06-15 16:49 ` Alexandru Elisei
2022-06-15 16:49 ` Alexandru Elisei
2022-06-15 16:49 ` Alexandru Elisei
2022-06-15 21:22 ` Jan Kara
2022-06-15 21:22 ` Jan Kara
2022-06-15 21:22 ` Jan Kara
2022-06-14 13:58 ` Jan Kara
2022-06-14 13:58 ` Jan Kara
2022-06-14 13:58 ` Jan Kara
2022-06-14 14:53 ` Alexandru Elisei
2022-06-14 14:53 ` Alexandru Elisei
2022-06-14 14:53 ` Alexandru Elisei
2022-06-14 15:09 ` Sergey Senozhatsky
2022-06-14 15:09 ` Sergey Senozhatsky
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=Yqf3pxG16lQcacUA@google.com \
--to=senozhatsky@chromium.org \
--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=jack@suse.cz \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.