From: Ilya Zykov <ilya@ilyx.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [BUG -next] cpufreq: cpufreq_governor.
Date: Mon, 10 Dec 2012 10:59:18 +0400 [thread overview]
Message-ID: <50C58846.7000408@ilyx.ru> (raw)
In-Reply-To: <1619333.jM1smpk2m8@vostro.rjw.lan>
On 10.12.2012 3:08, Rafael J. Wysocki wrote:
> On Sunday, December 09, 2012 09:17:04 PM Ilya Zykov wrote:
>> On 05.12.2012 22:53, Ilya Zykov wrote:
>>> What do I do wrong?
>>>
>>> After: modprobe cpufreq_ondemand
>>> I have:
>>>
>>> WARNING: Error inserting freq_table (/lib/modules/3.7.0-rc8-next-20121205-ttybuf.1+/kernel/drivers/cpufreq/freq_table.ko): Unknown symbol in module, or unknown parameter (see dmesg)
>>> FATAL: Error inserting cpufreq_ondemand (/lib/modules/3.7.0-rc8-next-20121205-ttybuf.1+/kernel/drivers/cpufreq/cpufreq_ondemand.ko): Unknown symbol in module, or unknown parameter (see dmesg)
>>>
>>> dmesg:
>>> Dec 5 22:26:11 bm kernel: cpufreq_governor: Unknown symbol __cpufreq_driver_getavg (err 0)
>>> Dec 5 22:26:11 bm kernel: cpufreq_governor: Unknown symbol sysfs_create_group (err 0)
>>> Dec 5 22:26:11 bm kernel: cpufreq_governor: Unknown symbol sysfs_remove_group (err 0)
>>> Dec 5 22:26:11 bm kernel: cpufreq_governor: Unknown symbol __cpufreq_driver_target (err 0)
>>> Dec 5 22:26:11 bm kernel: cpufreq_governor: Unknown symbol get_cpu_idle_time_us (err 0)
>>> Dec 5 22:26:11 bm kernel: cpufreq_governor: Unknown symbol delayed_work_timer_fn (err 0)
>>> Dec 5 22:26:11 bm kernel: cpufreq_governor: Unknown symbol get_cpu_iowait_time_us (err 0)
>>>
>>> cat /proc/kallsyms |grep freq_dr
>>> ffffffff814976e0 T __cpufreq_driver_target
>>> ffffffff814987e0 T __cpufreq_driver_getavg
>>> ffffffff81498850 T cpufreq_driver_target
>>> ffffffff81881650 r __ksymtab___cpufreq_driver_getavg
>>> ffffffff81881660 r __ksymtab___cpufreq_driver_target
>>> ffffffff81883b40 r __ksymtab_cpufreq_driver_target
>>> ffffffff81894290 r __kcrctab___cpufreq_driver_getavg
>>> ffffffff81894298 r __kcrctab___cpufreq_driver_target
>>> ffffffff81895508 r __kcrctab_cpufreq_driver_target
>>> ffffffff818b3080 r __kstrtab___cpufreq_driver_getavg
>>> ffffffff818b3098 r __kstrtab_cpufreq_driver_target
>>> ffffffff818b30ae r __kstrtab___cpufreq_driver_target
>>> ffffffff81e240c8 b cpufreq_driver_lock
>>> ffffffff81e240d0 b cpufreq_driver
>>> ffffffffa0c42000 d acpi_cpufreq_driver [acpi_cpufreq]
>>
>> I managed to fix:
>>
>> git checkout 16642a2e7be23bb -- drivers/cpufreq
>> git checkout 250f6715a4112d668 -- include/linux/cpufreq.h
>
> Can you please send your .config?
>
> Rafael
>
>
gcc --version
gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4)
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
prev parent reply other threads:[~2012-12-10 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 18:37 [BUG -next] cpufreq: cpufreq_governor Ilya Zykov
2012-12-05 18:53 ` Ilya Zykov
2012-12-09 17:17 ` Ilya Zykov
2012-12-09 23:08 ` Rafael J. Wysocki
2012-12-10 6:51 ` Ilya Zykov
2012-12-10 6:59 ` Ilya Zykov [this message]
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=50C58846.7000408@ilyx.ru \
--to=ilya@ilyx.ru \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.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 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.