Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753696AbbKBUum (ORCPT ); Mon, 2 Nov 2015 15:50:42 -0500 Received: from mail-io0-f179.google.com ([209.85.223.179]:33074 "EHLO mail-io0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753582AbbKBUuj (ORCPT ); Mon, 2 Nov 2015 15:50:39 -0500 MIME-Version: 1.0 In-Reply-To: <20151102204620.GF24668@usrtlx11787.corpusers.net> References: <20151102204620.GF24668@usrtlx11787.corpusers.net> Date: Mon, 2 Nov 2015 12:50:38 -0800 Message-ID: Subject: Re: MMC/regulator boot hang in -next From: John Stultz To: Bjorn Andersson Cc: Sascha Hauer , Mark Brown , Ulf Hansson , lkml Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 27 On Mon, Nov 2, 2015 at 12:46 PM, Bjorn Andersson wrote: > On Mon 02 Nov 11:57 PST 2015, 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. >> >> Reverting "regulator: core: Propagate voltage changes to supply >> regulators" - fc42112c0eaa avoids the hang, but I still see lockdep >> noise. >> >> Full log of -next based tree without any reverts follows: > > It sure does lock like a deadlock to me. Can you figure out which > regulator we're talking about here? And confirm that this is 8064 we're > talking about Yep. It is an 8064. I'll add some debug messages to figure out which regulators are having trouble. thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/