From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: Fwd: Tegra 30 System hangs because of commit "pinctrl: move subsystem mutex to pinctrl_dev struct"
Date: Mon, 29 Apr 2013 13:59:39 -0600 [thread overview]
Message-ID: <517ED12B.8080502@wwwdotorg.org> (raw)
In-Reply-To: <CAK5ve-KBDyvjNRVMcXgfnhYcajdcGsuAKaepzCBt+epiXoYvSw@mail.gmail.com>
On 04/29/13 12:41, Bryan Wu wrote:
> Forward to ARM and Tegra mail list.
>
> ---------- Forwarded message ----------
> From: Bryan Wu <cooloney@gmail•com>
> Date: Mon, Apr 29, 2013 at 11:15 AM
> Subject: Tegra 30 System hangs because of commit "pinctrl: move
> subsystem mutex to pinctrl_dev struct"
> To: patrice.chotard at st.com, Linus Walleij <linus.walleij@linaro•org>
> Cc: Stephen Warren <swarren@wwwdotorg•org>,
> "linux-next at vger.kernel.org" <linux-next@vger•kernel.org>
>
>
> Hi Patrice and Linus,
>
> I'm running linux-next on my Tegra 30 system everyday. But since
> next-20130426 release, the linux-next kernel will hang on my Tegra 30
> boards like Cardhu and Beaver.
>
> After some bisect and comparing to next-20130424, I found the commit
> "pinctrl: move subsystem mutex to pinctrl_dev struct" introduced this
> issue. If I simply revert this patch in next-20130429, system boots up
> as before.
>
> Could you please help to check this?
I would suggest simply dropping or reverting this patch; I had pointed
out a long time ago that it was unlikely to be correct.
My guess/suspicion is a recursive lock attempt during processing hogs
during pinctrl device registration, or perhaps during dt->map
conversion. Bryan, are you able to confirm this?
next parent reply other threads:[~2013-04-29 19:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK5ve-KXdS8az=Gtja-mF=Z3_EeZVA7bLYSU0EE2mf5bHmSUKw@mail.gmail.com>
[not found] ` <CAK5ve-KBDyvjNRVMcXgfnhYcajdcGsuAKaepzCBt+epiXoYvSw@mail.gmail.com>
2013-04-29 19:59 ` Stephen Warren [this message]
2013-04-29 20:54 ` Fwd: Tegra 30 System hangs because of commit "pinctrl: move subsystem mutex to pinctrl_dev struct" Bryan Wu
2013-05-03 14:22 ` Linus Walleij
2013-05-04 13:30 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-04 20:52 ` Linus Walleij
2013-05-05 11:28 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-05 19:57 ` Linus Walleij
2013-05-05 20:22 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 19:29 ` Linus Walleij
2013-05-06 19:32 ` Bryan Wu
2013-05-06 19:41 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 19:54 ` Russell King - ARM Linux
2013-05-06 20:12 ` Linus Walleij
2013-05-09 13:25 ` Grant Likely
2013-05-09 16:13 ` Olof Johansson
2013-05-09 17:51 ` Fathi Boudra
2013-05-10 9:29 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-14 20:39 ` Rob Herring
2013-05-15 14:13 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 20:14 ` Stephen Warren
2013-05-06 20:19 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 20:40 ` Bryan Wu
2013-05-06 20:25 ` Jean-Christophe PLAGNIOL-VILLARD
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=517ED12B.8080502@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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