All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>,
	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
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit 10e14073107d
Date: Tue, 14 Jun 2022 07:15:48 +0200	[thread overview]
Message-ID: <297b268a-85de-bc8c-88eb-b8d050ac1ec3@kernel.org> (raw)
In-Reply-To: <Yqdry+IghSWnJ6pe@monolith.localdoman>

On 13. 06. 22, 18:54, Alexandru Elisei 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.

It's too early for lockdep. Could you try to move lockdep_init() before 
console_init() in start_kernel()?

You'd need to use early console (which you already do).

thanks,
-- 
js
suse labs

_______________________________________________
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: Jiri Slaby <jirislaby@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>,
	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
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit 10e14073107d
Date: Tue, 14 Jun 2022 07:15:48 +0200	[thread overview]
Message-ID: <297b268a-85de-bc8c-88eb-b8d050ac1ec3@kernel.org> (raw)
In-Reply-To: <Yqdry+IghSWnJ6pe@monolith.localdoman>

On 13. 06. 22, 18:54, Alexandru Elisei 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.

It's too early for lockdep. Could you try to move lockdep_init() before 
console_init() in start_kernel()?

You'd need to use early console (which you already do).

thanks,
-- 
js
suse labs

_______________________________________________
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: Jiri Slaby <jirislaby@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>,
	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
Subject: Re: [BUG] rockpro64 board hangs in console_init() after commit 10e14073107d
Date: Tue, 14 Jun 2022 07:15:48 +0200	[thread overview]
Message-ID: <297b268a-85de-bc8c-88eb-b8d050ac1ec3@kernel.org> (raw)
In-Reply-To: <Yqdry+IghSWnJ6pe@monolith.localdoman>

On 13. 06. 22, 18:54, Alexandru Elisei 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.

It's too early for lockdep. Could you try to move lockdep_init() before 
console_init() in start_kernel()?

You'd need to use early console (which you already do).

thanks,
-- 
js
suse labs

  parent reply	other threads:[~2022-06-14  5:16 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
2022-06-14  2:51   ` Sergey Senozhatsky
2022-06-14  2:51   ` Sergey Senozhatsky
2022-06-14  5:15 ` Jiri Slaby [this message]
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=297b268a-85de-bc8c-88eb-b8d050ac1ec3@kernel.org \
    --to=jirislaby@kernel.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=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 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.