From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.9-rc1: swapper/0 [ INFO: possible circular locking dependency detected ]
Date: Wed, 06 Mar 2013 15:11:05 +0100 [thread overview]
Message-ID: <51374E79.9050408@free-electrons.com> (raw)
In-Reply-To: <CAB7JpEHJdKeOhkME-6mMdPY6VyTQwFvM33+gxg4X9ZpQv1=6RQ@mail.gmail.com>
Hi Alexander,
Thanks for your reply.
Le 06/03/2013 14:43, Alexander Shishkin a ?crit :
> On 6 March 2013 12:33, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
>> Just noticed this in 3.9-rc1 on an iMX28 (ARM) board with a config
>> based on mxs_defconfig. I'm using the patchset "Add tested id
>> switch and vbus connect detect support for Chipidea" from Peter
>> Chen in its 10th version [1], rebased on top of 3.9-rc1, but since
>> this doesn't modify the locks present in the udc_irq function, I
>> think the problem is elsewhere.
>
> From a quick look at the current chipidea code, I don't see any place
> where we might try to take cdev->lock under ci->lock. I should have a
> better look at Peter's patchset to see if it can trigger that.
And from a quick git blame on top of Peter patches, it seems like
udc_irq has been left untouched by his patches.
> Peter, have you seen anything like that with your code? Is this easy
> to trigger (I would assume it is)?
Quite easy yes, just plug a usb cable in gadget mode.
> Can you post the contents of "events" debug file in sysfs?
http://code.bulix.org/64liql-83101
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-06 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 10:33 v3.9-rc1: swapper/0 [ INFO: possible circular locking dependency detected ] Maxime Ripard
2013-03-06 13:43 ` Alexander Shishkin
2013-03-06 14:11 ` Maxime Ripard [this message]
2013-03-07 8:08 ` Peter Chen
2013-03-07 10:24 ` Maxime Ripard
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=51374E79.9050408@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--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).