lkml.org 
[lkml]   [2010]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.34-rc5-git3 - INFO: possible circular locking dependency detected - (s_active#91){++++.+}, at: [<ffffffff81142c4a>] sysfs_addrm_finish+0x31/0x50
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



\
 
 \ /
  Last update: 2010-04-24 04:13    [W:0.020 / U:1.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site