2010/2/8 Paul Walmsley <paul@xxxxxxxxx>: > On Mon, 8 Feb 2010, Arno Steffen wrote: > >> Thanks Paul for your help. >> >> Switch on the "#define DEBUG" in this both files skip almost all >> kernel boot messages before this warning and gives just this: !?! > > You probably need to enable CONFIG_DEBUG_LL to see all of the messages. > >> Uncompressing Linux................ done, booting the kernel. >> lock: associated clk usbtll_ick to clkdm core_l4_clkdm >> Clocking rate (Crystal/Core/MPU): 12.0/332/600 MHz >> ------------[ cut here ]------------ >> WARNING: at arch/arm/mach-omap2/clock34xx.c:773 >> omap3_noncore_dpll_set_rate+0x1d4/0x308() >> Modules linked in: >> [<c002a924>] (unwind_backtrace+0x0/0xdc) from [<c004a168>] >> (warn_slowpath_common+0x48/0x60) >> .... >> >> I expected to get more messages, not less: >> You are right, my board is running at 12 instead of 13MHz, but this >> setting is (or should be) done in uboot. >> I don't know what this new line withb the "lock" means. > > The leading "c" was apparently dropped. You can recursively grep through > the source tree to locate messages, if you are curious as to where they > come from. > >> On my board there is no USB at all. > > If you're not using any of the DPLL5-connected devices (USB, USIM, etc.), > what happens if you comment out the omap3_clk_lock_dpll5() call in > clock34xx.c? This is not a proper fix, of course, but it may help narrow > down the problem. > - Paul Thanks Paul! Sorry for bothering you again: Although I set "#define DEBUG" in clock.c and clock34xx.c and checked that kernel has been new compiled with "CONFIG_DEBUG_LL=y" the debub messages are quite strange. Uncompressing Linux................. done, booting the kernel. kout2_src_ck to clkdm core_clkdm Clocking rate (Crystal/Core/MPU): 12.0/332/600 MHz Reprogramming SDRC clock to 332000000 Hz GPMC revision 5.0 ... This strange behaviour is just happend if I do a "#define DEBUG" in clock.c. Changing the debug setting in clock34xx.c has no effect at all ?!? Anyhow there are good news too: I removed the call of omap3_clk_lock_dpll5() and you are right - the message disappers. How did you know that? This call clk_set_rate(dpll5_clk, DPLL5_FREQ_FOR_USBHOST); causes the first message, and thus I assume that dpll5_clk might be wrong, which is get by this command: dpll5_clk = clk_get(NULL, "dpll5_ck"); I could live with this workaround (remove the call), but have to be sure, that clock is not powered (save energy). Best regards Arno -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
