On Mon, Nov 2, 2015 at 2:03 PM, John Stultz <[email protected]> wrote: > On Mon, Nov 2, 2015 at 12:46 PM, Bjorn Andersson > <[email protected]> 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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
