Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp5179443ybb; Tue, 24 Mar 2020 12:23:04 -0700 (PDT) X-Google-Smtp-Source: ADFU+vumq+v9trQNuNIDF0b5SfTGm8Cw1IRIGONNDK+yxiqjJiBDQJ0++LTqhWFGWUDC3J8HWsWI X-Received: by 2002:a9d:2269:: with SMTP id o96mr14442731ota.173.1585077784459; Tue, 24 Mar 2020 12:23:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585077784; cv=none; d=google.com; s=arc-20160816; b=HevM/YM64WsIpPzPu2nHnrN6TbYJHF6thIWS/T57+9HVMzOVsRh2zuzB/CrKybr5zE xBYu0NhxZzI+RkrUVUJsV2GcLdrWneK20+zFHycatVsrfdyKbCILNjqcIhSFfayfRb2Q ifs1SQlmD2vz3qxYvFMG+W/asAQGmpbHjOmK977IPPvCwECMRi3u8z9dKBRIHirL1pYi DEYE45UdlWy/sySdcUFOOozSn5XTSuOckt8Stb8CbPehDQyLMKNJJcWe+676VPFrtqfy sgihockRxAXQe0yszohxN3Kp+KdKpGkTrbNhEz1nuBof/n3dep6PPwW2T+/lxxfcMLGh +wAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:in-reply-to :subject:cc:to:from:date; bh=Invcc16Pi0DJenPbGIMWgmpW0C0gkSIemmbKLz3zF10=; b=IS3I+9KLfFYgCE9OEwkgteclV3Fhh9JvE2dQkjVfGk1LtxFEf9qqNfBreFZI8TGeTE wyL7gW1Lbz4aqiuVOE/yFACVGWAXq7QL5KodeRTnS4HkuLfPJ4oZtHgrDhnLEj5VY8TA DcyX4Q2Lsqbk6P1IQYKfzPaimw6WOxbnyvZaMlG+JOG+VL8ZXAUAhS1eVyE60ZWxWryE YjhiKtc1S1WawHDCuhQcAwPb9aVITAMk/XdSf7o9rr4T7i07xHgKVzT5mq1RsGA0ED9S poigwCl5FHF0mpM+IFnKvOrVnIILaRbMyPPyTTtqFJfFgB7lMrRHspXfXTubYuBlrsdC OnKQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f136si10146922oig.9.2020.03.24.12.22.49; Tue, 24 Mar 2020 12:23:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726034AbgCXTWZ (ORCPT + 99 others); Tue, 24 Mar 2020 15:22:25 -0400 Received: from netrider.rowland.org ([192.131.102.5]:46377 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1725900AbgCXTWZ (ORCPT ); Tue, 24 Mar 2020 15:22:25 -0400 Received: (qmail 12890 invoked by uid 500); 24 Mar 2020 15:22:24 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Mar 2020 15:22:24 -0400 Date: Tue, 24 Mar 2020 15:22:24 -0400 (EDT) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Qais Yousef cc: Oliver Neukum , Greg Kroah-Hartman , , Subject: Re: lockdep warning in urb.c:363 usb_submit_urb In-Reply-To: <20200324172235.bsxea6qb3id6bhb3@e107158-lin> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 24 Mar 2020, Qais Yousef wrote: > On 03/24/20 11:56, Alan Stern wrote: > > This certainly reinforces the initial impression that the cause of the > > warnings is a bug in the platform code. You should ask the appropriate > > maintainer. > > The device-tree compatible node returns "generic-ohci". > drivers/usb/host/ohci-platform.c returns you as the maintainer :-) I'm the maintainer of the driver for the device. But the device structure itself (the one named 7ffb0000.ohci) gets created by device-tree -- that's what I was referring to. Here's the first error message: usb usb2: runtime PM trying to activate child device usb2 but parent (7ffb0000.ohci) is not active The runtime PM status of 7ffb0000.ohci is set in ohci_platform_probe(), which does: pm_runtime_set_active(&dev->dev); The runtime PM status can change, and there aren't any debugging statements in ohci_platform_suspend() or ohci_platform_resume() (or ohci_suspend()/ohci_resume() in ohci-hcd.c, for that matter). Maybe you can add some so we can see if anything strange is going on. Any maybe you can find out exactly where that error message is coming from by calling dump_stack() immediately after the dev_err() line (approximately line 1198 in drivers/base/power/runtime.c). (Also, you might want to turn off rcutorture. It adds a lot of messages to the system log that are irrelevant for our purposes.) Alan Stern