From: Stephen Boyd <sboyd@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Cc: Maxime Ripard <maxime@cerno.tech>
Subject: Re: Boot lockup on imx8mp in llinux-next
Date: Thu, 31 Mar 2022 15:02:03 -0700 [thread overview]
Message-ID: <20220331220205.A93DDC340ED@smtp.kernel.org> (raw)
In-Reply-To: <1911426.usQuhbGJ8B@steina-w>
Quoting Alexander Stein (2022-03-30 00:49:31)
> Hello everyone,
>
> I noticed that my imx8mp based board (TQMa8MPxL, not yet mainline) locked up
> during boot in linux-next. I bisected it down to commit [1].
> I found out that disabling 'fec' and 'eqos' (both ethernet controller) nodes
> in DT resulted in booting Kernel, alas NFS boot failed eventually obviously.
> Reverting make things working again.
> I have no idea which clock is the actual culprit here and how to fix it. I
> just wanted to make you aware of this issue.
Thanks. Please try to help debug hit on the thread at
https://lore.kernel.org/r/20220325161144.1901695-4-maxime@cerno.tech
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Cc: Maxime Ripard <maxime@cerno.tech>
Subject: Re: Boot lockup on imx8mp in llinux-next
Date: Thu, 31 Mar 2022 15:02:03 -0700 [thread overview]
Message-ID: <20220331220205.A93DDC340ED@smtp.kernel.org> (raw)
In-Reply-To: <1911426.usQuhbGJ8B@steina-w>
Quoting Alexander Stein (2022-03-30 00:49:31)
> Hello everyone,
>
> I noticed that my imx8mp based board (TQMa8MPxL, not yet mainline) locked up
> during boot in linux-next. I bisected it down to commit [1].
> I found out that disabling 'fec' and 'eqos' (both ethernet controller) nodes
> in DT resulted in booting Kernel, alas NFS boot failed eventually obviously.
> Reverting make things working again.
> I have no idea which clock is the actual culprit here and how to fix it. I
> just wanted to make you aware of this issue.
Thanks. Please try to help debug hit on the thread at
https://lore.kernel.org/r/20220325161144.1901695-4-maxime@cerno.tech
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-31 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 7:49 Boot lockup on imx8mp in llinux-next Alexander Stein
2022-03-30 7:49 ` Alexander Stein
2022-03-31 22:02 ` Stephen Boyd [this message]
2022-03-31 22:02 ` Stephen Boyd
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=20220331220205.A93DDC340ED@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=maxime@cerno.tech \
/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.