Hi,
* H. Nikolaus Schaller hns@goldelico.com [160423 09:48]:
Hi Tony, Sometimes after reboot I am facing this message (not on poweroff + fresh boot). It repeats 4 times and then the kernel continues:
...
[ 0.087502] pinctrl core: initialized pinctrl subsystem [ 0.088814] driver_register 'reg-dummy' [ 0.092258] NET: Registered protocol family 16 [ 0.097064] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.098983] omap_hwmod: l3_main_3 using broken dt data from ocp [ 0.101014] omap_hwmod: l3_main_2 using broken dt data from ocp [ 1.504807] clock: dpll_abe_ck failed transition to 'locked' [ 2.804409] clock: dpll_abe_ck failed transition to 'locked' [ 4.104043] clock: dpll_abe_ck failed transition to 'locked' [ 5.403667] clock: dpll_abe_ck failed transition to 'locked' [ 5.406310] ------------[ cut here ]------------ [ 5.406331] WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:679 clk_disable+0x34/0x40 [ 5.406338] Modules linked in: [ 5.406354] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.6.0-rc4-letux+ #122 [ 5.406361] Hardware name: Generic OMAP5 (Flattened Device Tree) [ 5.406384] [<c022789c>] (unwind_backtrace) from [<c022403c>] (show_stack+0x10/0x14) [ 5.406401] [<c022403c>] (show_stack) from [<c0517e44>] (dump_stack+0x88/0xc0) [ 5.406418] [<c0517e44>] (dump_stack) from [<c0249860>] (__warn+0xc0/0xec) [ 5.406434] [<c0249860>] (__warn) from [<c02498a8>] (warn_slowpath_null+0x1c/0x20) [ 5.406449] [<c02498a8>] (warn_slowpath_null) from [<c06e5854>] (clk_disable+0x34/0x40) [ 5.406467] [<c06e5854>] (clk_disable) from [<c0235f0c>] (_disable_clocks+0x18/0x70) [ 5.406481] [<c0235f0c>] (_disable_clocks) from [<c0237104>] (_enable.part.15+0x20c/0x248) [ 5.406494] [<c0237104>] (_enable.part.15) from [<c0e0ec94>] (_setup+0xc0/0x200) [ 5.406507] [<c0e0ec94>] (_setup) from [<c023769c>] (omap_hwmod_for_each+0x28/0x58) [ 5.406519] [<c023769c>] (omap_hwmod_for_each) from [<c0e0efc4>] (__omap_hwmod_setup_all+0x30/0x40) [ 5.406533] [<c0e0efc4>] (__omap_hwmod_setup_all) from [<c02018c0>] (do_one_initcall+0x100/0x1b8) [ 5.406549] [<c02018c0>] (do_one_initcall) from [<c0e00d28>] (do_basic_setup+0x98/0xd4) [ 5.406564] [<c0e00d28>] (do_basic_setup) from [<c0e00de8>] (kernel_init_freeable+0x84/0x124) [ 5.406581] [<c0e00de8>] (kernel_init_freeable) from [<c080381c>] (kernel_init+0x8/0x110) [ 5.406595] [<c080381c>] (kernel_init) from [<c02207c8>] (ret_from_fork+0x14/0x2c) [ 5.406657] ---[ end trace 35a58c46f27cd4a1 ]--- [ 5.406667] omap_hwmod: dmic: _wait_target_ready failed: -16 [ 5.406681] omap_hwmod: dmic: cannot be enabled for reset (3) [ 6.733460] clock: dpll_abe_ck failed transition to 'locked' [ 8.033089] clock: dpll_abe_ck failed transition to 'locked' [ 8.035732] ------------[ cut here ]------------
...
You had reported that:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/309047.h...
and there was a patch for OMAP4:
http://www.spinics.net/lists/linux-omap/msg95381.html
So what is the state for OMAP5?
I think I'm only seeing this with igepv5 on every warm reset. I don't think it happens on omap5-uevm. Most likely it depends on the u-boot revision somehow? Should be fixed for the kernel though.
Could this be the reason for all our spurious kernel hangs and problems?
For reboots at least :) For me it eventually boots with tons of errors.
Regards,
Tony