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: 2.6.21-rc6 + firstfloor patches: BUG: sleeping function called from invalid context at kernel/sched,.c:3643
Date: Fri, 13 Apr 2007 23:20:50 -0700 [thread overview]
Message-ID: <462072C2.4070605@goop.org> (raw)
I'm seeing this:
Apr 13 21:55:34 localhost kernel: BUG: sleeping function called from invalid context at kernel/sched.c:3643
Apr 13 21:55:34 localhost kernel: in_atomic():1, irqs_disabled():0
Apr 13 21:55:34 localhost kernel: 1 lock held by events/0/8:
Apr 13 21:55:34 localhost kernel: #0: (dbs_mutex){--..}, at: [<c032046b>] mutex_lock+0x1f/0x23
Apr 13 21:55:34 localhost kernel: [<c0106f25>] show_trace_log_lvl+0x1a/0x30
Apr 13 21:55:34 localhost kernel: [<c0107588>] show_trace+0x12/0x14
Apr 13 21:55:34 localhost kernel: [<c0107650>] dump_stack+0x16/0x18
Apr 13 21:55:34 localhost kernel: [<c011a56a>] __might_sleep+0xe5/0xeb
Apr 13 21:55:34 localhost kernel: [<c031f194>] wait_for_completion+0x1a/0xaa
Apr 13 21:55:34 localhost kernel: [<c011bea3>] set_cpus_allowed+0x6e/0x8c
Apr 13 21:55:34 localhost kernel: [<c010f490>] acpi_cpufreq_target+0x18d/0x262
Apr 13 21:55:34 localhost kernel: [<c02ae6d5>] __cpufreq_driver_target+0x27/0x32
Apr 13 21:55:34 localhost kernel: [<c02b0d2b>] do_dbs_timer+0x190/0x1d2
Apr 13 21:55:34 localhost kernel: [<c012ecde>] run_workqueue+0x8f/0x15f
Apr 13 21:55:34 localhost kernel: [<c012f4ab>] worker_thread+0xf8/0x124
Apr 13 21:55:34 localhost kernel: [<c0131cf0>] kthread+0xb5/0xe1
Apr 13 21:55:34 localhost kernel: [<c0106b07>] kernel_thread_helper+0x7/0x10
Apr 13 21:55:34 localhost kernel: =======================
Apr 13 21:55:34 localhost kernel: BUG: scheduling while atomic: events/0/0x00000002/8
Apr 13 21:55:34 localhost kernel: 1 lock held by events/0/8:
Apr 13 21:55:34 localhost kernel: #0: (dbs_mutex){--..}, at: [<c032046b>] mutex_lock+0x1f/0x23
Apr 13 21:55:34 localhost kernel: [<c0106f25>] show_trace_log_lvl+0x1a/0x30
Apr 13 21:55:34 localhost kernel: [<c0107588>] show_trace+0x12/0x14
Apr 13 21:55:34 localhost kernel: [<c0107650>] dump_stack+0x16/0x18
Apr 13 21:55:34 localhost kernel: [<c031e971>] __sched_text_start+0x79/0x86a
Apr 13 21:55:34 localhost kernel: [<c031f1ee>] wait_for_completion+0x74/0xaa
Apr 13 21:55:34 localhost kernel: [<c011bea3>] set_cpus_allowed+0x6e/0x8c
Apr 13 21:55:34 localhost kernel: [<c010f490>] acpi_cpufreq_target+0x18d/0x262
Apr 13 21:55:34 localhost kernel: [<c02ae6d5>] __cpufreq_driver_target+0x27/0x32
Apr 13 21:55:34 localhost kernel: [<c02b0d2b>] do_dbs_timer+0x190/0x1d2
Apr 13 21:55:34 localhost kernel: [<c012ecde>] run_workqueue+0x8f/0x15f
Apr 13 21:55:34 localhost kernel: [<c012f4ab>] worker_thread+0xf8/0x124
Apr 13 21:55:34 localhost kernel: [<c0131cf0>] kthread+0xb5/0xe1
Apr 13 21:55:34 localhost kernel: [<c0106b07>] kernel_thread_helper+0x7/0x10
[...repeat ad nauseum...]
next reply other threads:[~2007-04-14 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 6:20 Jeremy Fitzhardinge [this message]
2007-04-14 11:38 ` 2.6.21-rc6 + firstfloor patches: BUG: sleeping function called from invalid context at kernel/sched,.c:3643 Andi Kleen
2007-04-14 21:12 ` Jeremy Fitzhardinge
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=462072C2.4070605@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox