From: George Nychis <gnychis@cmu.edu>
To: lkml <linux-kernel@vger.kernel.org>
Subject: 2.6.18-rc2-git4: BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug()
Date: Tue, 25 Jul 2006 13:57:43 -0400 [thread overview]
Message-ID: <44C65B97.7010404@cmu.edu> (raw)
Hey everyone,
I recently compiled a 2.6.18-rc2-git4 kernel and get this with cpu
hotplug enabled:
Lukewarm IQ detected in hotplug locking
BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug()
[<c0138635>] lock_cpu_hotplug+0x74/0x7d
[<c012f815>] __create_workqueue+0x44/0x13c
[<c0340df6>] cpufreq_stat_notifier_policy+0x22/0x1d2
[<c03418c0>] cpufreq_governor_dbs+0x2c7/0x31d
[<c033f5ff>] __cpufreq_governor+0x1d/0x150
[<c033f7f3>] __cpufreq_set_policy+0xc1/0xf7
[<c03403a7>] store_scaling_governor+0xa2/0x180
[<c033fbd6>] handle_update+0x0/0x5
[<c0222800>] kobject_cleanup+0x59/0x60
[<c0340305>] store_scaling_governor+0x0/0x180
[<c033fe79>] store+0x2e/0x3e
[<c018ed8d>] sysfs_write_file+0x8b/0xc7
[<c015dd9b>] vfs_write+0x87/0xf5
[<c018ed02>] sysfs_write_file+0x0/0xc7
[<c015e350>] sys_write+0x41/0x6a
[<c0102f15>] sysenter_past_esp+0x56/0x79
Lukewarm IQ detected in hotplug locking
BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug()
[<c0138635>] lock_cpu_hotplug+0x74/0x7d
[<c0341697>] cpufreq_governor_dbs+0x9e/0x31d
[<c033f5ff>] __cpufreq_governor+0x1d/0x150
[<c033f803>] __cpufreq_set_policy+0xd1/0xf7
[<c03403a7>] store_scaling_governor+0xa2/0x180
[<c033fbd6>] handle_update+0x0/0x5
[<c0222800>] kobject_cleanup+0x59/0x60
[<c0340305>] store_scaling_governor+0x0/0x180
[<c033fe79>] store+0x2e/0x3e
[<c018ed8d>] sysfs_write_file+0x8b/0xc7
[<c015dd9b>] vfs_write+0x87/0xf5
[<c018ed02>] sysfs_write_file+0x0/0xc7
[<c015e350>] sys_write+0x41/0x6a
[<c0102f15>] sysenter_past_esp+0x56/0x79
Just wanted to report this.
Thanks!
George
reply other threads:[~2006-07-25 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44C65B97.7010404@cmu.edu \
--to=gnychis@cmu.edu \
--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