On Jan 14, 2008 6:51 PM, Johannes Berg <[EMAIL PROTECTED]> wrote: > > > The warning that triggered (lockdep.c:700) means that one class (key) > > was used with more than one name. > > Right. > > > Looking at cleanup_workqueue_thread(), the lock_acquire() there works on > > wq->lockdep_map, and that is only initialized at one spot: > > __create_workqueue_key(), thus it stands to reason that that was > > mis-used. > > Oh ok, yes, makes sense. Maybe something is generating a workqueue with > a name that's passed in but the key is statically from that place. I'll > try to find it.
I add some debug printk and found the names : block_osm/exec_osm in drivers/message/i2o maybe this helps. Regards dave > > johannes > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
