From: Mark Brown <broonie@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: MMC/regulator boot hang in -next
Date: Mon, 2 Nov 2015 21:17:56 +0000 [thread overview]
Message-ID: <20151102211756.GK20228@sirena.org.uk> (raw)
In-Reply-To: <CALAqxLW30-dXBPKYEawvdZPaBotQHv2KGjMKHQVo8Q9r_ayWHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-11-02 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 19:57 John Stultz
2015-11-02 20:46 ` Bjorn Andersson
2015-11-02 20:50 ` John Stultz
2015-11-02 22:03 ` John Stultz
2015-11-02 22:27 ` John Stultz
2015-11-02 22:58 ` Mark Brown
2015-11-02 23:04 ` John Stultz
2015-11-03 5:35 ` Mark Brown
2015-11-02 21:17 ` Mark Brown [this message]
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=20151102211756.GK20228@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®