From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-rc6 + firstfloor patches: BUG: sleeping function called from invalid context at kernel/sched,.c:3643
Date: Sat, 14 Apr 2007 14:12:25 -0700 [thread overview]
Message-ID: <462143B9.6080907@goop.org> (raw)
In-Reply-To: <200704141338.50058.ak@suse.de>
Andi Kleen wrote:
> Fixed now. The latest sched-clock was leaking preempt counts during
> cpu frequency changes.
>
No, that didn't help. I think its cpufreq:
Apr 14 13:58:29 localhost kernel: BUG: scheduling while atomic: swapper/0x00000002/1
Apr 14 13:58:29 localhost kernel: 2 locks held by swapper/1:
Apr 14 13:58:29 localhost kernel: #0: (&per_cpu(cpu_policy_rwsem, cpu)){--..}, at: [<c02af1ec>] lock_policy_rwsem_write
+0x35/0x5f
Apr 14 13:58:29 localhost kernel: #1: (userspace_mutex){--..}, at: [<c032046b>] mutex_lock+0x1f/0x23
Apr 14 13:58:29 localhost kernel: [<c0106f25>] show_trace_log_lvl+0x1a/0x30
Apr 14 13:58:29 localhost kernel: [<c0107588>] show_trace+0x12/0x14
Apr 14 13:58:29 localhost kernel: [<c0107650>] dump_stack+0x16/0x18
Apr 14 13:58:29 localhost kernel: [<c031e971>] __sched_text_start+0x79/0x86a
Apr 14 13:58:29 localhost kernel: [<c031f1ee>] wait_for_completion+0x74/0xaa
Apr 14 13:58:29 localhost kernel: [<c011bea3>] set_cpus_allowed+0x6e/0x8c
Apr 14 13:58:29 localhost kernel: [<c010f490>] acpi_cpufreq_target+0x18d/0x262
Apr 14 13:58:29 localhost kernel: [<c02ae6d5>] __cpufreq_driver_target+0x27/0x32
Apr 14 13:58:29 localhost kernel: [<c02aff0b>] cpufreq_governor_userspace+0x120/0x154
Apr 14 13:58:29 localhost kernel: [<c02ae888>] __cpufreq_governor+0x77/0xab
Apr 14 13:58:29 localhost kernel: [<c02aee6a>] __cpufreq_set_policy+0x109/0x11a
Apr 14 13:58:29 localhost kernel: [<c02af32d>] cpufreq_set_policy+0x32/0x6c
Apr 14 13:58:29 localhost kernel: [<c02afc11>] cpufreq_add_dev+0x347/0x3ea
Apr 14 13:58:29 localhost kernel: [<c024a15e>] sysdev_driver_register+0x62/0xaf
Apr 14 13:58:29 localhost kernel: [<c02af85a>] cpufreq_register_driver+0x82/0xf2
Apr 14 13:58:29 localhost kernel: [<c0454f24>] acpi_cpufreq_init+0x8d/0x93
Apr 14 13:58:29 localhost kernel: [<c04497c7>] init+0x14b/0x241
Apr 14 13:58:29 localhost kernel: [<c0106b07>] kernel_thread_helper+0x7/0x10
Apr 14 13:58:29 localhost kernel: =======================
Apr 14 13:58:29 localhost kernel: initcall at 0xc0454e97: acpi_cpufreq_init+0x0/0x93(): returned with preemption imbalance
J
next prev parent reply other threads:[~2007-04-14 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 6:20 2.6.21-rc6 + firstfloor patches: BUG: sleeping function called from invalid context at kernel/sched,.c:3643 Jeremy Fitzhardinge
2007-04-14 11:38 ` Andi Kleen
2007-04-14 21:12 ` Jeremy Fitzhardinge [this message]
2007-04-15 10:23 ` Andi Kleen
2007-04-16 16:11 ` Jeremy Fitzhardinge
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=462143B9.6080907@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--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 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.