From: Oliver Neukum <oneukum@suse.de>
To: Qais Yousef <qais.yousef@arm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: lockdep warning in urb.c:363 usb_submit_urb
Date: Mon, 23 Mar 2020 17:20:02 +0100 [thread overview]
Message-ID: <1584980402.27949.21.camel@suse.de> (raw)
In-Reply-To: <20200323155746.du2ogtvy6gnjzpb4@e107158-lin.cambridge.arm.com>
Am Montag, den 23.03.2020, 15:57 +0000 schrieb Qais Yousef:
> On 03/23/20 16:36, Oliver Neukum wrote:
> > Am Montag, den 23.03.2020, 14:38 +0000 schrieb Qais Yousef:
> > > Hi
> > >
> > > I've hit the following lockdep warning when I trigger hibernate on arm64
> > > platform (Juno-r2)
> > >
> > >
> > > echo suspend > /sys/power/disk
> > > echo disk > /sys/power/state
> > >
> > > I only had a usb flash drive attached to it. Let me know if you need more info.
> >
> > Hi,
> >
> > that is not a lockdep issue, but the hub driver is not properly killing
> > its URB presumably. Yet, the driver looks correct to me. Please use
> > the additional patch and activate dynamic debugging for usbcore.
>
> Yes sorry my bad, it's a WARN_ONCE().
>
> I applied your patch and will reproduce, but meanwhile not sure if you noticed
> this line in my previous email
>
> [ 327.154849] usb usb2: runtime PM trying to activate child device usb2 but parent (7ffb0000.ohci) is not active
Hi,
yes I noticed, but that did not trigger the WARN(). One thing at a time
please.
Regards
Oliver
next prev parent reply other threads:[~2020-03-23 16:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 14:38 lockdep warning in urb.c:363 usb_submit_urb Qais Yousef
2020-03-23 15:36 ` Oliver Neukum
2020-03-23 15:54 ` Alan Stern
2020-03-23 16:02 ` Qais Yousef
2020-03-23 16:18 ` Oliver Neukum
2020-03-23 15:57 ` Qais Yousef
2020-03-23 16:20 ` Oliver Neukum [this message]
2020-03-23 17:29 ` Qais Yousef
2020-03-24 9:08 ` Oliver Neukum
2020-03-24 10:46 ` Qais Yousef
2020-03-24 13:20 ` Oliver Neukum
2020-03-24 13:43 ` Qais Yousef
2020-03-24 13:52 ` Alan Stern
2020-03-24 14:06 ` Qais Yousef
2020-03-24 15:56 ` Alan Stern
2020-03-24 17:22 ` Qais Yousef
2020-03-24 19:22 ` Alan Stern
2020-03-25 15:00 ` Qais Yousef
2020-03-25 20:49 ` Alan Stern
2020-03-25 21:28 ` Rafael J. Wysocki
2020-03-26 12:27 ` Qais Yousef
2020-03-27 20:45 ` Alan Stern
2020-03-28 14:15 ` Rafael J. Wysocki
2020-03-28 19:58 ` Alan Stern
2020-03-29 9:16 ` Rafael J. Wysocki
2020-03-29 13:56 ` Rafael J. Wysocki
2020-03-29 16:27 ` Alan Stern
2020-04-03 15:04 ` Rafael J. Wysocki
2020-04-03 16:13 ` Rafael J. Wysocki
2020-04-03 16:41 ` Alan Stern
2020-04-03 18:32 ` Rafael J. Wysocki
2020-04-03 20:15 ` Alan Stern
2020-04-06 16:45 ` Rafael J. Wysocki
2020-04-06 20:25 ` Alan Stern
2020-04-09 18:45 ` Rafael J. Wysocki
2020-04-11 2:41 ` Alan Stern
2020-04-13 21:32 ` Rafael J. Wysocki
2020-04-14 13:43 ` Rafael J. Wysocki
2020-04-14 17:47 ` Alan Stern
2020-04-15 22:20 ` Rafael J. Wysocki
2020-04-16 15:18 ` Alan Stern
2020-04-17 9:57 ` Rafael J. Wysocki
2020-04-17 16:10 ` Alan Stern
2020-04-17 21:54 ` Rafael J. Wysocki
2020-04-17 23:37 ` Alan Stern
2020-04-18 9:40 ` Rafael J. Wysocki
2020-04-03 17:08 ` Rafael J. Wysocki
2020-04-20 20:26 ` Alan Stern
2020-04-21 11:15 ` Qais Yousef
2020-03-24 13:47 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1584980402.27949.21.camel@suse.de \
--to=oneukum@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=qais.yousef@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).