From: "art" <art@usfltd.com>
To: linux-kernel@vger.kernel.org
Cc: davej@redhat.com, michal.k.k.piotrowski@gmail.com
Subject: Re: 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51/unlock_cpu_hotplug()
Date: Sat, 05 Aug 2006 17:14:10 -0500 [thread overview]
Message-ID: <20060805221410.22397.qmail@mail.webhostingstar.com> (raw)
same for 2.6.18.rc3-git7 on smp amd64 x2 (dualcore)
after
# echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
dmesg
....
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
Lukewarm IQ detected in hotplug locking
BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug()
Call Trace:
[<ffffffff802a0e72>] lock_cpu_hotplug+0x50/0x73
[<ffffffff80299a36>] __create_workqueue+0x5d/0x146
[<ffffffff803f437d>] cpufreq_governor_dbs+0xa8/0x2f4
[<ffffffff803f22ac>] __cpufreq_governor+0xa4/0x194
[<ffffffff803f2516>] __cpufreq_set_policy+0x17a/0x1f4
[<ffffffff803f2792>] store_scaling_governor+0x17c/0x1d8
[<ffffffff803f35f8>] handle_update+0x0/0x28
[<ffffffff8026650b>] _spin_unlock_irqrestore+0x15/0x30
[<ffffffff803f1a00>] cpufreq_cpu_get+0xb5/0x143
[<ffffffff80272dbf>] store+0x44/0x5b
[<ffffffff802f1ddc>] sysfs_write_file+0xc5/0xf4
[<ffffffff80215e1b>] vfs_write+0xce/0x174
[<ffffffff802166a9>] sys_write+0x45/0x6e
[<ffffffff8025fa8e>] system_call+0x7e/0x83
------------------------------------------------------
my old message from 2006/08/03
2.6.18-rc3-git1-smp-amd64 - Lukewarm IQ detected in hotplug
what i have in dmesg
Linux version 2.6.18-rc3-git1 (xxx@xxx.xxx) (gcc version 4.1.1 20060525)) #1
SMP PREEMPT Tue Aug 1 09:46:44 CDT 2006
...
AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 01
...
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses
genfs_contexts
ip_tables: (C) 2000-2006 Netfilter Core Team
BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
Call Trace:
[<ffffffff802a0e51>] unlock_cpu_hotplug+0x3f/0x6c
[<ffffffff803f3937>] store_speed+0xc2/0xd1
[<ffffffff80272d3f>] store+0x44/0x5b
[<ffffffff802f1c8a>] sysfs_write_file+0xc5/0xf4
[<ffffffff80215e14>] vfs_write+0xce/0x174
[<ffffffff802166a2>] sys_write+0x45/0x6e
[<ffffffff8025fa0e>] system_call+0x7e/0x83
Netfilter messages via NETLINK v0.30.
...
...
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
Lukewarm IQ detected in hotplug locking
BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug()
Call Trace:
[<ffffffff802a0def>] lock_cpu_hotplug+0x50/0x73
[<ffffffff802999ab>] __create_workqueue+0x5d/0x146
[<ffffffff803f4108>] cpufreq_governor_dbs+0xa8/0x2f4
[<ffffffff803f2006>] __cpufreq_governor+0xa4/0x194
[<ffffffff803f225f>] __cpufreq_set_policy+0x169/0x1d9
[<ffffffff803f24a8>] store_scaling_governor+0x153/0x18d
[<ffffffff803f32ed>] handle_update+0x0/0x28
[<ffffffff8026648b>] _spin_unlock_irqrestore+0x15/0x30
[<ffffffff803f1800>] cpufreq_cpu_get+0xb4/0x143
[<ffffffff80272d3f>] store+0x44/0x5b
[<ffffffff802f1c8a>] sysfs_write_file+0xc5/0xf4
[<ffffffff80215e14>] vfs_write+0xce/0x174
[<ffffffff802166a2>] sys_write+0x45/0x6e
[<ffffffff8025fa0e>] system_call+0x7e/0x83
hdc: CHECK for good STATUS
...
the same in 2.6.18-rc3-git3 any clue ?
-------------------------------------------------
xboom
art@usfltd.com
next reply other threads:[~2006-08-05 22:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 22:14 art [this message]
2006-08-06 1:23 ` 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51/unlock_cpu_hotplug() Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 19:04 Michal Piotrowski
2006-08-04 19:24 ` Linus Torvalds
2006-08-04 22:24 ` Dave Jones
2006-08-05 0:31 ` Dave Jones
2006-08-05 2:10 ` Dave Jones
2006-08-05 2:23 ` Dave Jones
2006-08-05 2:49 ` Dave Jones
2006-08-05 6:47 ` Dave Jones
2006-08-05 7:46 ` Andrew Morton
2006-08-05 19:47 ` Dave Jones
2006-08-05 20:02 ` Andrew Morton
2006-08-06 1:12 ` Andrew Morton
2006-08-05 10:54 ` Michal Piotrowski
2006-08-05 11:11 ` Michal Piotrowski
2006-08-05 11:26 ` Michal Piotrowski
2006-08-05 18:47 ` Dave Jones
2006-08-05 21:15 ` Michal Piotrowski
2006-08-06 16:59 ` Michal Piotrowski
2006-08-06 18:05 ` Dave Jones
2006-08-06 19:32 ` Andrew Morton
2006-08-07 1:26 ` Andi Kleen
2006-08-07 8:18 ` Jan Beulich
2006-08-15 12:23 ` Jan Beulich
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=20060805221410.22397.qmail@mail.webhostingstar.com \
--to=art@usfltd.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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.