From: Maxime Ripard <maxime@cerno.tech>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Boyd <sboyd@kernel.org>, Heiko Stuebner <heiko@sntech.de>,
kernelci-results@groups.io, bot@kernelci.org,
gtucker@collabora.com,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux Kernel Functional Testing <lkft@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: next/master bisection: baseline.login on rk3328-rock64
Date: Mon, 10 Oct 2022 16:50:10 +0200 [thread overview]
Message-ID: <20221010145010.ibodo56smlokfouu@houat> (raw)
In-Reply-To: <Y0QNSx+ZgqKSvPOC@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1410 bytes --]
Hi Mark,
On Mon, Oct 10, 2022 at 01:17:15PM +0100, Mark Brown wrote:
> On Fri, Oct 07, 2022 at 02:10:11PM -0700, KernelCI bot wrote:
>
> The KernelCI bisection bot found a boot problem on today's -next
> on rk3328-rock64 with a defconfig plus debug fragments triggered by
> cb1b1dd96241f ("clk: Set req_rate on reparenting"). The log doesn't
> show any obvious warnings but simply stalls out after:
>
> [ 258.676722][ T1] pps_core: LinuxPPS API ver. 1 registered
> [ 258.684929][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
> [ 258.788655][ T1] PTP clock support registered
> [ 259.246358][ T1] EDAC MC: Ver: 3.0.0
>
> It seems like the performance of the system has been dramatically
> reduced, current mainline boots with the same kernel config show we're
> reaching that point after only 5s:
>
> [ 5.577047][ T1] PTP clock support registered
> [ 5.585556][ T1] EDAC MC: Ver: 3.0.0
>
> and getting to a prompt after a bit over a minute which is much more
> viable.
Thanks for the report
It might be related to https://lore.kernel.org/linux-clk/0acc7217-762c-7c0d-45a0-55c384824ce4@samsung.com/
I've sent a series that might address this issue:
https://lore.kernel.org/linux-clk/20221010-rpi-clk-fixes-again-v1-0-d87ba82ac404@cerno.tech/
Let me know if it fixes things for you
Maxime
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-10-10 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <634095b3.a70a0220.ad568.42a8@mx.google.com>
2022-10-10 12:17 ` next/master bisection: baseline.login on rk3328-rock64 Mark Brown
2022-10-10 14:50 ` Maxime Ripard [this message]
2022-10-10 15:40 ` Mark Brown
2022-10-11 12:13 ` Maxime Ripard
2022-10-12 8:25 ` Maxime Ripard
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=20221010145010.ibodo56smlokfouu@houat \
--to=maxime@cerno.tech \
--cc=alexander.stein@ew.tq-group.com \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=gtucker@collabora.com \
--cc=heiko@sntech.de \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lkft@linaro.org \
--cc=m.szyprowski@samsung.com \
--cc=naresh.kamboju@linaro.org \
--cc=sboyd@kernel.org \
/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