From: Sergei Trofimovich <slyich@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: v2.6.35-rc3: BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/1255
Date: Tue, 15 Jun 2010 22:04:42 +0300 [thread overview]
Message-ID: <20100615220442.55b5271e@mosly> (raw)
In-Reply-To: <20100613124246.07f98bd7@mosly>
[-- Attachment #1: Type: text/plain, Size: 3289 bytes --]
> [ 7.582027] BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/1255
> [ 7.582038] caller is nr_iowait_cpu+0x15/0x2b
> [ 7.582044] Pid: 1255, comm: modprobe Not tainted 2.6.35-rc3 #87
> [ 7.582048] Call Trace:
> [ 7.582059] [<ffffffff81185470>] debug_smp_processor_id+0xc4/0xe0
> [ 7.582067] [<ffffffff810265cd>] nr_iowait_cpu+0x15/0x2b
> [ 7.582075] [<ffffffff81053b78>] update_ts_time_stats+0x37/0x72
> [ 7.582083] [<ffffffff8104f5b5>] ? ktime_get+0x60/0xb9
> [ 7.582089] [<ffffffff81053d2d>] get_cpu_idle_time_us+0x44/0x63
> [ 7.582100] [<ffffffff8126f516>] cpufreq_governor_dbs+0xe1/0x3cf
> [ 7.582109] [<ffffffff8104bb5e>] ? notifier_call_chain+0x32/0x5e
> [ 7.582116] [<ffffffff8126c87e>] __cpufreq_governor+0xc7/0x105
> [ 7.582124] [<ffffffff8126d66c>] __cpufreq_set_policy+0x1a8/0x222
> [ 7.582131] [<ffffffff8126d977>] cpufreq_add_dev_interface+0x291/0x2ac
> [ 7.582139] [<ffffffff8126e22e>] ? handle_update+0x0/0x33
> [ 7.582147] [<ffffffff8126e107>] cpufreq_add_dev+0x4b9/0x4c9
> [ 7.582157] [<ffffffff811ff373>] sysdev_driver_register+0xbf/0x119
> [ 7.582164] [<ffffffff8126c9a8>] cpufreq_register_driver+0xb9/0x1a5
> [ 7.582174] [<ffffffffa02e40d7>] acpi_cpufreq_init+0xd7/0x10d [acpi_cpufreq]
> [ 7.582183] [<ffffffffa02e4000>] ? acpi_cpufreq_init+0x0/0x10d [acpi_cpufreq]
> [ 7.582191] [<ffffffff810001ef>] do_one_initcall+0x59/0x149
> [ 7.582199] [<ffffffff8105cced>] sys_init_module+0x9c/0x1db
> [ 7.582206] [<ffffffff81001eeb>] system_call_fastpath+0x16/0x1b
>
> Attached whole config and dmesg.
It seems to be reproducible on each boot. Today's one:
[ 20.242755] BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/1462
[ 20.242765] caller is nr_iowait_cpu+0x15/0x2b
[ 20.242770] Pid: 1462, comm: modprobe Not tainted 2.6.35-rc3 #87
[ 20.242774] Call Trace:
[ 20.242784] [<ffffffff81185470>] debug_smp_processor_id+0xc4/0xe0
[ 20.242790] [<ffffffff810265cd>] nr_iowait_cpu+0x15/0x2b
[ 20.242798] [<ffffffff81053b78>] update_ts_time_stats+0x37/0x72
[ 20.242805] [<ffffffff8104f5b5>] ? ktime_get+0x60/0xb9
[ 20.242811] [<ffffffff81053d2d>] get_cpu_idle_time_us+0x44/0x63
[ 20.242820] [<ffffffff8126f516>] cpufreq_governor_dbs+0xe1/0x3cf
[ 20.242828] [<ffffffff8104bb5e>] ? notifier_call_chain+0x32/0x5e
[ 20.242835] [<ffffffff8126c87e>] __cpufreq_governor+0xc7/0x105
[ 20.242842] [<ffffffff8126d66c>] __cpufreq_set_policy+0x1a8/0x222
[ 20.242848] [<ffffffff8126d977>] cpufreq_add_dev_interface+0x291/0x2ac
[ 20.242855] [<ffffffff8126e22e>] ? handle_update+0x0/0x33
[ 20.242863] [<ffffffff8126e107>] cpufreq_add_dev+0x4b9/0x4c9
[ 20.242871] [<ffffffff811ff373>] sysdev_driver_register+0xbf/0x119
[ 20.242878] [<ffffffff8126c9a8>] cpufreq_register_driver+0xb9/0x1a5
[ 20.242887] [<ffffffffa02e40d7>] acpi_cpufreq_init+0xd7/0x10d [acpi_cpufreq]
[ 20.242894] [<ffffffffa02e4000>] ? acpi_cpufreq_init+0x0/0x10d [acpi_cpufreq]
[ 20.242902] [<ffffffff810001ef>] do_one_initcall+0x59/0x149
[ 20.242909] [<ffffffff8105cced>] sys_init_module+0x9c/0x1db
[ 20.242915] [<ffffffff81001eeb>] system_call_fastpath+0x16/0x1b
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-15 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 9:42 v2.6.35-rc3: BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/1255 Sergei Trofimovich
2010-06-15 19:04 ` Sergei Trofimovich [this message]
2010-07-15 17:09 ` [SOLVED] " Sergei Trofimovich
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=20100615220442.55b5271e@mosly \
--to=slyich@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).