* RX51: kernel message spam from CPUfreq driver
@ 2013-08-11 14:13 Sebastian Reichel
2013-08-12 6:29 ` Rajendra Nayak
0 siblings, 1 reply; 3+ messages in thread
From: Sebastian Reichel @ 2013-08-11 14:13 UTC (permalink / raw)
To: linux-omap; +Cc: Santosh Shilimkar, Rajendra Nayak, Tony Lindgren
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi,
On RX-51 (Nokia N900) the (mainline) kernel constantly outputs the
following message about 2-3x per second since some releases:
[ 1038.314514] cpu cpu0: CPUfreq: Cannot find matching frequency for 125000000
(The message is from drivers/cpufreq/omap-cpufreq.c, line 100)
This is really annoying and makes debug output without a "grep -v"
basically useless. Can you give me some hints how to solve the
problem?
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: RX51: kernel message spam from CPUfreq driver
2013-08-11 14:13 RX51: kernel message spam from CPUfreq driver Sebastian Reichel
@ 2013-08-12 6:29 ` Rajendra Nayak
2013-08-13 12:25 ` Sebastian Reichel
0 siblings, 1 reply; 3+ messages in thread
From: Rajendra Nayak @ 2013-08-12 6:29 UTC (permalink / raw)
To: Sebastian Reichel; +Cc: linux-omap, Santosh Shilimkar, Tony Lindgren
On Sunday 11 August 2013 07:43 PM, Sebastian Reichel wrote:
> Hi,
>
> On RX-51 (Nokia N900) the (mainline) kernel constantly outputs the
> following message about 2-3x per second since some releases:
>
> [ 1038.314514] cpu cpu0: CPUfreq: Cannot find matching frequency for 125000000
>
> (The message is from drivers/cpufreq/omap-cpufreq.c, line 100)
>
> This is really annoying and makes debug output without a "grep -v"
> basically useless. Can you give me some hints how to solve the
> problem?
Whats the system clock frequency used on RX-51? I guess omap2_dpll_round_rate()
for some reason thinks that with the given sys clock its not possible to
lock the DPLL at 125Mhz. If you can send the debug logs from omap2_dpll_round_rate()
that should probably help know whats going wrong.
>
> -- Sebastian
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: RX51: kernel message spam from CPUfreq driver
2013-08-12 6:29 ` Rajendra Nayak
@ 2013-08-13 12:25 ` Sebastian Reichel
0 siblings, 0 replies; 3+ messages in thread
From: Sebastian Reichel @ 2013-08-13 12:25 UTC (permalink / raw)
To: Rajendra Nayak; +Cc: linux-omap, Santosh Shilimkar, Tony Lindgren
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
Hi,
On Mon, Aug 12, 2013 at 11:59:28AM +0530, Rajendra Nayak wrote:
> Whats the system clock frequency used on RX-51? I guess omap2_dpll_round_rate()
> for some reason thinks that with the given sys clock its not possible to
> lock the DPLL at 125Mhz. If you can send the debug logs from omap2_dpll_round_rate()
> that should probably help know whats going wrong.
It's also not possible to lock the DPLL at other frequencies. During
the boot process at least 125MHz, 250MHz and 550MHz cannot be locked.
I uploaded a full serial dump from the n900 with debug output from
omap2_dpll_round_rate to the following url:
http://paste.debian.net/24628/
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-08-13 12:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-11 14:13 RX51: kernel message spam from CPUfreq driver Sebastian Reichel
2013-08-12 6:29 ` Rajendra Nayak
2013-08-13 12:25 ` Sebastian Reichel
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.