linux-kernel - Re: MMC/regulator boot hang in -next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Nov 2015 21:17:56 +0000
From:	Mark Brown <broonie@...nel.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	Sascha Hauer <s.hauer@...gutronix.de>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	Bjorn Andersson <bjorn.andersson@...ymobile.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: MMC/regulator boot hang in -next

On Mon, Nov 02, 2015 at 11:57:40AM -0800, John Stultz wrote:
> Trying to move my nexus7 work to -next, I started seeing boot time
> hangs. Enabling some debug options provided with a lockdep spew.

Please don't send upstream things to my work address, it's unlikely to
get read normally.

> Reverting "regulator: core: Propagate voltage changes to supply
> regulators" -  fc42112c0eaa avoids the hang, but I still see lockdep
> noise.

To repeat what I said off-list the lockdep splat looks like yet another
case of lockdep generating false positives by being unable to work out
that two different instances of objects of the same type are different
objects.  

Without more information on the system you're looking at, especially
what regulators are involved and how they are related it's hard to tell
what's going on as a result, getting some trace from the tracepoints
would be more useful.  Nothing obvious is jumping out from the code.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)