From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 44C18C00140 for ; Tue, 26 Jul 2022 14:55:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=2LnyZPWXivEaYKSgHvK/H1Q35Ouuhv1/ix7UUqm1L4c=; b=clrI8yoi+QVqwh irrW+HVxMPxOWsa7Q0xHgMMltC0H/lCpDjbWKaUBRZRUQHIkrZ/l1PpVWNqgdPQ8L5EA0cYIUNqkQ ZdUgpISiOhDb300ITb62KZl2btALtKuxo09Ol9o32PP7xPAWdCdvnAMPr6lbsEgVhwxpVkG07koyO Ic3NigDNpxfUjrrO5yssYaqv5dddxMRdWG4fh1evzNvm5Y2l2Xryq2B0pM7ELQk1qj+o/GGUbN2gO mDWSPCAAacylCdVJUf/T2nJAlLWB8SXv1Nj9/6Rq5ALEUnGCshMsi/xMR3gDZsWzehUXyB25YmJcO w5ODnxHmAjXBee8vT6lA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oGLxM-000MwY-1F; Tue, 26 Jul 2022 14:54:44 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oGLxG-000Msx-Lf for linux-arm-kernel@lists.infradead.org; Tue, 26 Jul 2022 14:54:42 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4F9241FB; Tue, 26 Jul 2022 07:54:34 -0700 (PDT) Received: from bogus (e103737-lin.cambridge.arm.com [10.1.197.49]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id CCBB33F73B; Tue, 26 Jul 2022 07:54:32 -0700 (PDT) Date: Tue, 26 Jul 2022 15:54:30 +0100 From: Sudeep Holla To: Mark Rutland Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Sudeep Holla , Peter Zijlstra Subject: Re: [-next] Lockdep warnings Message-ID: <20220726145430.bfwidmw6xmeppbfb@bogus> References: <20220726104134.3b3awfphvafljdgp@bogus> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220726_075438_789898_20C343D5 X-CRM114-Status: GOOD ( 21.48 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jul 26, 2022 at 03:44:31PM +0100, Mark Rutland wrote: > On Tue, Jul 26, 2022 at 11:41:34AM +0100, Sudeep Holla wrote: > > I was seeing the below lockdep warnings on my arm64 Juno development > > platform almost 2 weeks back with -next. I wanted to check for similar > > reports before post and forgot. > > [...] > > > However I don't see the above warning with the latest -next. When I tried > > yesterday's -next now, I see a different warning. Not sure if they are > > related. I haven't tried to bisect. > > > > --->8 > > ============================= > > [ BUG: Invalid wait context ] > > 5.19.0-rc8-next-20220725 #38 Not tainted > > ----------------------------- > > swapper/0/0 is trying to lock: > > (&drvdata->spinlock){....}-{3:3}, at: cti_cpu_pm_notify+0x54/0x114 > > Hmmm... do you have CONFIG_PROVE_RAW_LOCK_NESTING enabled? > Yes. > IIUC that should be {2:2} otherwise... > > > other info that might help us debug this: > > context-{5:5} > > 1 lock held by swapper/0/0: > > #0: (cpu_pm_notifier.lock){....}-{2:2}, at: cpu_pm_enter+0x2c/0x80 > > ... and this is telling us that we're trying to take a regular spinlock under a > raw spinlock, which is not as intended. > > The Kconfig text notes: > > NOTE: There are known nesting problems. So if you enable this > option expect lockdep splats until these problems have been fully > addressed which is work in progress. This config switch allows to > identify and analyze these problems. It will be removed and the > check permanently enabled once the main issues have been fixed. > Ah, I hadn't seen or read this. Thanks for digging this and sharing. Sorry for the noise. Good I got to know this limitation, will try to remember this. Thanks again for your time Mark. -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel