Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752374AbbKBW1I (ORCPT ); Mon, 2 Nov 2015 17:27:08 -0500 Received: from mail-io0-f171.google.com ([209.85.223.171]:34194 "EHLO mail-io0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182AbbKBW1D (ORCPT ); Mon, 2 Nov 2015 17:27:03 -0500 MIME-Version: 1.0 In-Reply-To: References: <20151102204620.GF24668@usrtlx11787.corpusers.net> Date: Mon, 2 Nov 2015 14:27:02 -0800 Message-ID: Subject: Re: MMC/regulator boot hang in -next From: John Stultz To: Bjorn Andersson Cc: Sascha Hauer , Ulf Hansson , lkml , Mark Brown 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: 1434 Lines: 35 On Mon, Nov 2, 2015 at 2:03 PM, John Stultz wrote: > 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 > > So it looks like we're setting the voltage on lvs1, which then calls > get_voltage() on s4. At that point the lockdep spew hits. > > But as Mark noted *this* spew looks like a false positive, but I > suspect lockdep is then disabled and can't detect the real hang > happens shortly afterwards. Further on this, the lockdep spew happens w/ v4.3 as well. Its just the deadlock in -next got me to add lockdep in my config. 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/