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 -- 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
