lkml.org 
[lkml]   [2010]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: sysfs lockdep complaint
From
Date
On Sat, 2010-02-20 at 17:26 +0800, Américo Wang wrote:
> On Thu, Feb 18, 2010 at 5:32 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > Get this when powernowd starts on my G5:
> >
> > [ 30.490674] =============================================
> > [ 30.490708] [ INFO: possible recursive locking detected ]
> > [ 30.490727] 2.6.33-rc8-wl-64012-g6917413 #160
> > [ 30.490744] ---------------------------------------------
> > [ 30.490763] powernowd/2577 is trying to acquire lock:
> > [ 30.490782] (s_active){++++.+}, at: [<c0000000001efa94>]
> .sysfs_addrm_finish+0x58/0xc0
> > [ 30.490831]
> > [ 30.490833] but task is already holding lock:
> > [ 30.490854] (s_active){++++.+}, at: [<c0000000001eff80>]
> .sysfs_get_active_two+0x3c/0x84
> > [ 30.490895]
>
> This should be fixed by the patchset from Eric:
>
> http://lkml.org/lkml/2010/2/11/334

Oh wow, well ..... I get like a thousand of these now:
BUG: key c0000002165eb478 not in .data!
instead of the lockdep complaint above.

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2010-02-20 12:23    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site