From: Mark Brown <broonie@kernel.org>
To: Maxime Ripard <maxime@cerno.tech>
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:40:30 +0100 [thread overview]
Message-ID: <Y0Q87tddypPtzZB3@sirena.org.uk> (raw)
In-Reply-To: <20221010145010.ibodo56smlokfouu@houat>
[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]
On Mon, Oct 10, 2022 at 04:50:10PM +0200, Maxime Ripard wrote:
> 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
> 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
Unfortunately I can't schedule tests directly, the board is in the
Baylibre lab so I've CCed Corentan and Kevin who might be able to help.
You should be able to see results via KernelCI for any tree that's
included and runs the debug builds (including -next).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 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 15:41 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
2022-10-10 15:40 ` Mark Brown [this message]
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=Y0Q87tddypPtzZB3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=bot@kernelci.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=maxime@cerno.tech \
--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