From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: regression: Clock changes in next-20141205 break at least omap4
Date: Fri, 5 Dec 2014 08:55:39 -0800 [thread overview]
Message-ID: <20141205165539.GA30437@atomide.com> (raw)
Hi,
Looks like commit 646cafc6aa4d ("clk: Change clk_ops->determine_rate
to return a clk_hw as the best parent") breaks booting at least for
omap4.
Below is the output from omap4-sdp with DEBUG_LL and earlyprintk
enabled.
Regards,
Tony
[ 1.670806] clock: dpll_abe_ck failed transition to 'locked'
[ 2.966735] clock: dpll_abe_ck failed transition to 'locked'
[ 4.262634] clock: dpll_abe_ck failed transition to 'locked'
[ 4.268554] ------------[ cut here ]------------
[ 4.273406] WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:846 clk_disable+0x24/0x30()
[ 4.281341] Modules linked in:
[ 4.284576] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.18.0-rc7-next-20141205-00004-g24aaa63b #141
[ 4.293945] Hardware name: Generic OMAP4 (Flattened Device Tree)
[ 4.300231] [<c0015614>] (unwind_backtrace) from [<c0011cdc>] (show_stack+0x10/0x14)
[ 4.308288] [<c0011cdc>] (show_stack) from [<c05b7fb8>] (dump_stack+0x80/0x9c)
[ 4.315795] [<c05b7fb8>] (dump_stack) from [<c003e4e8>] (warn_slowpath_common+0x78/0xb4)
[ 4.324188] [<c003e4e8>] (warn_slowpath_common) from [<c003e540>] (warn_slowpath_null+0x1c/0x24)
[ 4.333282] [<c003e540>] (warn_slowpath_null) from [<c04c386c>] (clk_disable+0x24/0x30)
[ 4.341583] [<c04c386c>] (clk_disable) from [<c00252a0>] (_disable_clocks+0x18/0x68)
[ 4.349609] [<c00252a0>] (_disable_clocks) from [<c0026810>] (_idle+0x15c/0x240)
[ 4.357299] [<c0026810>] (_idle) from [<c0844cb8>] (_setup+0x174/0x22c)
[ 4.364166] [<c0844cb8>] (_setup) from [<c0026c4c>] (omap_hwmod_for_each+0x30/0x5c)
[ 4.372131] [<c0026c4c>] (omap_hwmod_for_each) from [<c08450c4>] (__omap_hwmod_setup_all+0x30/0x40)
[ 4.381500] [<c08450c4>] (__omap_hwmod_setup_all) from [<c0008b44>] (do_one_initcall+0x80/0x1d4)
[ 4.390594] [<c0008b44>] (do_one_initcall) from [<c0837e9c>] (kernel_init_freeable+0x1f4/0x2cc)
[ 4.399627] [<c0837e9c>] (kernel_init_freeable) from [<c05b211c>] (kernel_init+0x8/0xe4)
[ 4.408020] [<c05b211c>] (kernel_init) from [<c000ea48>] (ret_from_fork+0x14/0x2c)
[ 4.415954] ---[ end trace f968bc068c5b0ccc ]---
[ 5.710815] clock: dpll_abe_ck failed transition to 'locked'
[ 7.006744] clock: dpll_abe_ck failed transition to 'locked'
next reply other threads:[~2014-12-05 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 16:55 Tony Lindgren [this message]
2014-12-05 18:21 ` regression: Clock changes in next-20141205 break at least omap4 Stephen Boyd
2014-12-05 18:38 ` Tony Lindgren
[not found] ` <20141212194238.20398.33333@quantum>
[not found] ` <alpine.DEB.2.02.1412122310570.29716@utopia.booyaka.com>
[not found] ` <20141215220224.20398.98259@quantum>
2014-12-16 0:21 ` Paul Walmsley
2014-12-16 0:38 ` Tony Lindgren
2014-12-16 1:31 ` Paul Walmsley
2014-12-16 19:01 ` Stephen Boyd
2014-12-16 20:01 ` Paul Walmsley
2014-12-16 20:23 ` Russell King - ARM Linux
2014-12-16 20:45 ` Paul Walmsley
2014-12-16 20:57 ` Russell King - ARM Linux
2014-12-16 22:25 ` Paul Walmsley
2014-12-17 9:52 ` Lucas Stach
2014-12-17 11:59 ` Tero Kristo
2014-12-19 16:45 ` Paul Walmsley
2014-12-18 19:23 ` Paul Walmsley
2014-12-18 23:37 ` Mike Turquette
2014-12-19 2:15 ` Paul Walmsley
2014-12-20 0:23 ` Mike Turquette
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=20141205165539.GA30437@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).