Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756691Ab0A2EnJ (ORCPT ); Thu, 28 Jan 2010 23:43:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756666Ab0A2EnI (ORCPT ); Thu, 28 Jan 2010 23:43:08 -0500 Received: from gate.crashing.org ([63.228.1.57]:49013 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756665Ab0A2EnG (ORCPT ); Thu, 28 Jan 2010 23:43:06 -0500 Subject: [2.6.33-rc5] Weird deadlock when shutting down From: Benjamin Herrenschmidt To: "linux-kernel@vger.kernel.org" Cc: Ingo Molnar , Peter Zijlstra , Johannes Berg Content-Type: text/plain; charset="UTF-8" Date: Fri, 29 Jan 2010 15:41:47 +1100 Message-ID: <1264740107.20211.53.camel@pasglop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 978 Lines: 32 Hi Ingo ! Johannes and I see this on our quad G5s... it -could- be similar to one reported a short while ago by Xiaotian Feng under the subject [2.6.33-rc4] sysfs lockdep warnings on cpu hotplug. Basically, the machine deadlocks right after printing the following when doing a shutdown: halt/4071 is trying to acquire lock: (s_active){++++.+}, at: [] .sysfs_addrm_finish+0x58/0xc0 but task is already holding lock: (&per_cpu(cpu_policy_rwsem, cpu)){+.+.+.}, at: [] .lock_policy_rwsem_write+0x84/0xf4 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: Any idea ? Cheers, Ben. -- 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/