Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753129AbbKBUq0 (ORCPT ); Mon, 2 Nov 2015 15:46:26 -0500 Received: from seldrel01.sonyericsson.com ([37.139.156.2]:11911 "EHLO seldrel01.sonyericsson.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752533AbbKBUqZ (ORCPT ); Mon, 2 Nov 2015 15:46:25 -0500 Date: Mon, 2 Nov 2015 12:46:20 -0800 From: Bjorn Andersson To: John Stultz CC: Sascha Hauer , Mark Brown , Ulf Hansson , lkml Subject: Re: MMC/regulator boot hang in -next Message-ID: <20151102204620.GF24668@usrtlx11787.corpusers.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 812 Lines: 22 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 Regards, Bjorn -- 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/