linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mark Brown <broonie@kernel.org>, Sasha Levin <sashal@kernel.org>,
	Tero Kristo <kristo@kernel.org>,
	kernelci-results@groups.io, bot@kernelci.org,
	gtucker@collabora.com, stable@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-clk@vger.kernel.org
Subject: Re: stable-rc/linux-5.10.y bisection: baseline.login on panda
Date: Tue, 11 Oct 2022 08:15:58 +0300	[thread overview]
Message-ID: <Y0T8DhAawSA3GYw7@atomide.com> (raw)
In-Reply-To: <20221011005552.62D85C433D6@smtp.kernel.org>

* Stephen Boyd <sboyd@kernel.org> [221011 00:47]:
> Quoting Mark Brown (2022-10-10 04:29:03)
> > The KernelCI bisection bot bisected a boot failure on the 5.10-rc stable
> > tree on Panda to d86c6447ee250 ("clk: ti: Stop using legacy clkctrl names
> > for omap4") in the v5.10 stable tree.  There's a lot of clock related
> > warnings/errors including:
> > 
> > <4>[    0.000000] WARNING: CPU: 0 PID: 0 at drivers/clk/clk.c:3778 __clk_register+0x464/0x868
> > <4>[    0.000000] ti_dt_clocks_register: failed to lookup clock node abe-clkctrl:0008:24, ret=-517
> > <4>[    0.416076] omap_hwmod: debugss: cannot _init_clocks
> > <4>[    0.421447] ------------[ cut here ]------------
> > <4>[    0.426513] WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2371 _init+0x428/0x488
> > 
> > (there's a *lot* of probe deferrals and hwmods that fail to init). The
> > last output from the kernel is:
> > 
> > <3>[   10.523590] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1410000 Vs max 1316660
> > <6>[   10.531890] Power Management for TI OMAP4+ devices.
> > <4>[   10.537048] OMAP4 PM: u-boot >= v2012.07 is required for full PM support
> > <5>[   10.544555] Loading compiled-in X.509 certificates
> > 
> > I've left the full report from the bot with more information including
> > full logs and a reported-by tag below:
> 
> I don't think we want that commit on stable. It depends on a DT change
> that may not be present. Tony?

Correct, that commit depends on devicetree data being available.

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-10-11  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6341c30d.170a0220.2bfa7.6117@mx.google.com>
2022-10-10 11:29 ` stable-rc/linux-5.10.y bisection: baseline.login on panda Mark Brown
2022-10-11  0:55   ` Stephen Boyd
2022-10-11  5:15     ` Tony Lindgren [this message]
2022-10-11 12:54   ` Sasha Levin

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=Y0T8DhAawSA3GYw7@atomide.com \
    --to=tony@atomide.com \
    --cc=bot@kernelci.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gtucker@collabora.com \
    --cc=kernelci-results@groups.io \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).