From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org, lkft-triage@lists.linaro.org,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Benoit Cousson <bcousson@baylibre.com>,
Carlos Hernandez <ceh@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
Olof Johansson <olof@lixom.net>,
tomi.valkeinen@ti.com, Anders Roxell <anders.roxell@linaro.org>
Subject: Re: OF: ERROR: Bad of_node_put() on /ocp/interconnect@4a000000/segment@0/target-module@8000/cm_core@0/l4per-cm@1700/l4per-clkctrl@28
Date: Fri, 24 Apr 2020 08:38:06 -0700 [thread overview]
Message-ID: <20200424153806.GJ37466@atomide.com> (raw)
In-Reply-To: <6366d76c-b9dc-6fa5-afad-0b2f471f8ec5@ti.com>
* Tero Kristo <t-kristo@ti.com> [200424 12:41]:
> On 17/04/2020 18:29, Tony Lindgren wrote:
> > * Naresh Kamboju <naresh.kamboju@linaro.org> [200327 16:44]:
> > > The reported problem still happening on arm beagle board x15 device
> > > running Linux next kernel 20200327.
> > ...
> >
> > > [ 0.000000] OF: ERROR: Bad of_node_put() on
> > > /ocp/interconnect@4a000000/segment@0/target-module@8000/cm_core@0/l4per-cm@1700/l4per-clkctrl@28
> > > [ 0.000000] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W
> > > 5.6.0-rc7-next-20200327 #1
> > > [ 0.000000] Hardware name: Generic DRA74X (Flattened Device Tree)
> > > [ 0.000000] [<c0311810>] (unwind_backtrace) from [<c030ba14>]
> > > (show_stack+0x10/0x14)
> > > [ 0.000000] [<c030ba14>] (show_stack) from [<c0fb6604>]
> > > (dump_stack+0xbc/0xd0)
> > > [ 0.000000] [<c0fb6604>] (dump_stack) from [<c0fbb07c>]
> > > (kobject_put+0xc0/0x104)
> > > [ 0.000000] [<c0fbb07c>] (kobject_put) from [<c1639e4c>]
> > > (of_clk_init+0x18c/0x228)
> > > [ 0.000000] [<c1639e4c>] (of_clk_init) from [<c1611544>]
> > > (omap_clk_init+0x3c/0x58)
> > > [ 0.000000] [<c1611544>] (omap_clk_init) from [<c1611ea8>]
> > > (omap4_sync32k_timer_init+0x8/0x2c)
> > > [ 0.000000] [<c1611ea8>] (omap4_sync32k_timer_init) from
> > > [<c161213c>] (omap5_realtime_timer_init+0x8/0x234)
> > > [ 0.000000] [<c161213c>] (omap5_realtime_timer_init) from
> > > [<c1600c88>] (start_kernel+0x330/0x4b8)
> >
> > Just FYI, Tero is looking at the clock issues that seem to be
> > causing these warnings.
>
> Haven't seen this before, but easily reproducible with multi_v7_defconfig. I
> have a simple fix for it now, will post to lists soon.
OK thanks for tracking it down.
Tony
next prev parent reply other threads:[~2020-04-24 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:41 OF: ERROR: Bad of_node_put() on /ocp/interconnect@4a000000/segment@0/target-module@8000/cm_core@0/l4per-cm@1700/l4per-clkctrl@28 Naresh Kamboju
2020-03-27 16:43 ` Naresh Kamboju
2020-04-17 15:29 ` Tony Lindgren
2020-04-24 12:40 ` Tero Kristo
2020-04-24 15:38 ` Tony Lindgren [this message]
2020-04-24 15:48 ` Tero Kristo
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=20200424153806.GJ37466@atomide.com \
--to=tony@atomide.com \
--cc=anders.roxell@linaro.org \
--cc=bcousson@baylibre.com \
--cc=ceh@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=naresh.kamboju@linaro.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tglx@linutronix.de \
--cc=tomi.valkeinen@ti.com \
/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.