Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751562Ab3F1Enf (ORCPT ); Fri, 28 Jun 2013 00:43:35 -0400 Received: from mail-ob0-f182.google.com ([209.85.214.182]:64876 "EHLO mail-ob0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750922Ab3F1EnP (ORCPT ); Fri, 28 Jun 2013 00:43:15 -0400 MIME-Version: 1.0 In-Reply-To: <20130625211544.GA2270@swordfish> References: <20130625211544.GA2270@swordfish> Date: Fri, 28 Jun 2013 10:13:14 +0530 Message-ID: Subject: Re: [LOCKDEP] cpufreq: possible circular locking dependency detected From: Viresh Kumar To: Sergey Senozhatsky Cc: Michael Wang , Jiri Kosina , Borislav Petkov , "Rafael J. Wysocki" , "Srivatsa S. Bhat" , linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1247 Lines: 28 On 26 June 2013 02:45, Sergey Senozhatsky wrote: > > [ 60.277396] ====================================================== > [ 60.277400] [ INFO: possible circular locking dependency detected ] > [ 60.277407] 3.10.0-rc7-dbg-01385-g241fd04-dirty #1744 Not tainted > [ 60.277411] ------------------------------------------------------- > [ 60.277417] bash/2225 is trying to acquire lock: > [ 60.277422] ((&(&j_cdbs->work)->work)){+.+...}, at: [] flush_work+0x5/0x280 > [ 60.277444] > but task is already holding lock: > [ 60.277449] (cpu_hotplug.lock){+.+.+.}, at: [] cpu_hotplug_begin+0x2b/0x60 > [ 60.277465] > which lock already depends on the new lock. Hi Sergey, Can you try reverting this patch? commit 2f7021a815f20f3481c10884fe9735ce2a56db35 Author: Michael Wang Date: Wed Jun 5 08:49:37 2013 +0000 cpufreq: protect 'policy->cpus' from offlining during __gov_queue_work() -- 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/