On 04/29/13 12:41, Bryan Wu wrote:
Forward to ARM and Tegra mail list.
---------- Forwarded message ----------
From: Bryan Wu <[email protected]>
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: [email protected], Linus Walleij <[email protected]>
Cc: Stephen Warren <[email protected]>,
"[email protected]" <[email protected]>
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
