From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] pxa27x_udc: possible recursive locking detected in pxa_ep_queue
Date: Mon, 28 Dec 2009 21:23:55 +0100 [thread overview]
Message-ID: <87vdfqx2xw.fsf@free.fr> (raw)
In-Reply-To: <20091223005313.13ba5061.ospite@studenti.unina.it> (Antonio Ospite's message of "Wed\, 23 Dec 2009 00\:53\:13 +0100")
Antonio Ospite <ospite@studenti.unina.it> writes:
> With your latest patch on top of 2.6.32 I get the "possible recursive
> locking" message at the *first* cable unplug/plug cycle, I am appending
> it here, the log is partial because I dumped it from RAM and something
> was lost.
Thanks.
Now, lets have another try. This patch is a bit saner, and though I got the
"locking detected" you noticed without it, I didn't manage to get it with this
patch applied.
As your test platform is far better than mine, would you mind a bit of testing
... again. This patch applies on top of v2.6.32.
Cheers.
--
Robert
next prev parent reply other threads:[~2009-12-28 20:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 10:57 [BUG] pxa27x_udc: possible recursive locking detected in pxa_ep_queue Antonio Ospite
2009-12-06 18:34 ` Robert Jarzmik
2009-12-06 20:01 ` Alan Stern
2009-12-06 20:23 ` David Brownell
2009-12-10 17:58 ` Robert Jarzmik
2009-12-10 21:01 ` David Brownell
2009-12-06 20:13 ` David Brownell
2009-12-10 17:49 ` Robert Jarzmik
2009-12-12 14:28 ` Robert Jarzmik
2009-12-12 16:31 ` Antonio Ospite
2009-12-20 18:36 ` Robert Jarzmik
2009-12-22 23:53 ` Antonio Ospite
2009-12-28 20:23 ` Robert Jarzmik [this message]
2009-12-28 23:03 ` Antonio Ospite
2010-01-17 12:41 ` Antonio Ospite
2010-01-17 19:33 ` Robert Jarzmik
2010-03-30 21:26 ` Michael Trimarchi
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=87vdfqx2xw.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/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).