From: Dave Jones <davej@redhat.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.34-rc5-git3 - INFO: possible circular locking dependency detected - (s_active#91){++++.+}, at: [<ffffffff81142c4a>] sysfs_addrm_finish+0x31/0x50
Date: Fri, 23 Apr 2010 22:11:08 -0400 [thread overview]
Message-ID: <20100424021108.GB19662@redhat.com> (raw)
In-Reply-To: <l2na44ae5cd1004231856gb03a023cnaf941169a044ab19@mail.gmail.com>
On Fri, Apr 23, 2010 at 09:56:20PM -0400, Miles Lane wrote:
> [ 2564.720395] Disabling non-boot CPUs ...
> [ 2564.764388]
> [ 2564.764391] =======================================================
> [ 2564.764395] [ INFO: possible circular locking dependency detected ]
> [ 2564.764400] 2.6.34-rc5-git3 #22
> [ 2564.764403] -------------------------------------------------------
> [ 2564.764408] pm-suspend/5388 is trying to acquire lock:
> [ 2564.764412] (s_active#91){++++.+}, at: [<ffffffff81142c4a>]
> sysfs_addrm_finish+0x31/0x50
> [ 2564.764432]
> [ 2564.764434] but task is already holding lock:
> [ 2564.764437] (&per_cpu(cpu_policy_rwsem, cpu)){+++++.}, at:
> [<ffffffff8132dd4d>] lock_policy_rwsem_write+0x4a/0x7b
> [ 2564.764450]
> [ 2564.764451] which lock already depends on the new lock.
> [ 2564.764454]
gah, this has been fixed in cpufreq.git for a while. I thought I'd
already pushed that along to Linus. I just sent him another pull request.
thanks,
Dave
prev parent reply other threads:[~2010-04-24 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 1:56 Miles Lane
2010-04-24 2:11 ` Dave Jones [this message]
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=20100424021108.GB19662@redhat.com \
--to=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®