From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
davej@codemonkey.org.uk
Subject: rc4: lukewarm irq warning during boot
Date: Wed, 9 Aug 2006 10:55:35 +0200 [thread overview]
Message-ID: <20060809085534.GA1694@elf.ucw.cz> (raw)
Hi!
I'm getting this... I guess this is known and too hard to fix for
2.6.18... but perhaps warning should be disabled? (Or is that already
a plan for 2.6.18?)
Pavel
Lukewarm IQ detected in hotplug locking
BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug()
[<c0104343>] show_trace_log_lvl+0x163/0x190
[<c01057af>] show_trace+0xf/0x20
[<c01057d5>] dump_stack+0x15/0x20
[<c01427fc>] lock_cpu_hotplug+0x7c/0x90
[<c0138af7>] __create_workqueue+0x47/0x140
[<c04bb58b>] cpufreq_governor_dbs+0x2cb/0x320
[<c04b97d6>] __cpufreq_governor+0x46/0xf0
[<c04b9a82>] __cpufreq_set_policy+0xf2/0x140
[<c04b9d22>] store_scaling_governor+0xd2/0x1c0
[<c04b95cd>] store+0x3d/0x60
[<c01ab55f>] sysfs_write_file+0x8f/0xe0
[<c016e056>] vfs_write+0xa6/0x160
[<c016ea11>] sys_write+0x41/0x70
[<c010303f>] syscall_call+0x7/0xb
[<b7ec52ce>] 0xb7ec52ce
[<c01427fc>] lock_cpu_hotplug+0x7c/0x90
[<c0138af7>] __create_workqueue+0x47/0x140
[<c04bb58b>] cpufreq_governor_dbs+0x2cb/0x320
[<c013531b>] notifier_call_chain+0x2b/0x60
[<c04b97d6>] __cpufreq_governor+0x46/0xf0
[<c04b9a82>] __cpufreq_set_policy+0xf2/0x140
[<c04b9d22>] store_scaling_governor+0xd2/0x1c0
[<c04ba710>] handle_update+0x0/0x10
[<c0269500>] kobject_set_name+0x20/0xb0
[<c04b9c50>] store_scaling_governor+0x0/0x1c0
[<c04b95cd>] store+0x3d/0x60
[<c01ab55f>] sysfs_write_file+0x8f/0xe0
[<c016e056>] vfs_write+0xa6/0x160
[<c01ab4d0>] sysfs_write_file+0x0/0xe0
[<c016ea11>] sys_write+0x41/0x70
[<c010303f>] syscall_call+0x7/0xb
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2006-08-09 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 8:55 Pavel Machek [this message]
2006-08-09 15:24 ` Andrew Morton
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=20060809085534.GA1694@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=davej@codemonkey.org.uk \
--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
Powered by JetHome