From: James Hogan <james.hogan@imgtec•com>
To: Bryan Wu <cooloney@gmail•com>
Cc: patrice.chotard@st•com, Linus Walleij <linus.walleij@linaro•org>,
Stephen Warren <swarren@wwwdotorg•org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: Re: Tegra 30 System hangs because of commit "pinctrl: move subsystem mutex to pinctrl_dev struct"
Date: Mon, 29 Apr 2013 20:48:36 +0100 [thread overview]
Message-ID: <517ECE94.4020806@imgtec.com> (raw)
In-Reply-To: <CAK5ve-KXdS8az=Gtja-mF=Z3_EeZVA7bLYSU0EE2mf5bHmSUKw@mail.gmail.com>
On 29/04/13 19:15, Bryan Wu wrote:
> 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 spent a while tracking this one down today too, then found it was
already fixed. See the patch "[PATCH, for-next] pinctrl: fix mutex
deadlock in get_pinctrl_dev_from_of_node()" from Daniel Mack.
Cheers
James
next prev parent reply other threads:[~2013-04-29 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 18:15 Tegra 30 System hangs because of commit "pinctrl: move subsystem mutex to pinctrl_dev struct" Bryan Wu
2013-04-29 19:48 ` James Hogan [this message]
2013-04-29 20:53 ` Bryan Wu
2013-05-03 14:19 ` Linus Walleij
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=517ECE94.4020806@imgtec.com \
--to=james.hogan@imgtec$(echo .)com \
--cc=cooloney@gmail$(echo .)com \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=patrice.chotard@st$(echo .)com \
--cc=swarren@wwwdotorg$(echo .)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