On 12/08, Marek Szyprowski wrote: > Hi Krzysztof, > > On 2017-12-08 13:33, Krzysztof Kozlowski wrote: > >On Fri, Dec 8, 2017 at 1:27 PM, Mark Brown <broonie@xxxxxxxxxx> wrote: > >>On Fri, Dec 08, 2017 at 12:20:07PM +0000, Mark Brown wrote: > >>>On Thu, Dec 07, 2017 at 03:54:47PM -0800, kernelci.org bot wrote: > >>> > >>>Today's -next failed to boot on peach-pi: > >>> > >>>> exynos_defconfig: > >>>> exynos5800-peach-pi: > >>>> lab-collabora: new failure (last pass: next-20171205) > >>>with details at https://kernelci.org/boot/id/5a2a2e7859b5141bc2afa17c/ > >>>(including logs and comparisons with other boots, the last good boot was > >>>Wednesday). It looks like it hangs somewhere late on in boot, the last > >>>output on the console is: > >>> > >>>[ 4.827139] smsc95xx 3-1.1:1.0 eth0: register 'smsc95xx' at usb-xhci-hcd.3.auto-1.1, smsc95xx USB 2.0 Ethernet, 94:eb:2c:00:03:c0 > >>>[ 5.781037] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330 > >>>[ 5.786247] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 > >>>[ 5.819200] dma-pl330 3880000.adma: PM domain MAU will not be powered off > >>>[ 64.529228] random: crng init done > >>> > >>>and there's failures earlier to instantiate the display. > >>I just noticed that further up the log there's a lockdep splat with a > >>conflict between the genpd and clock API locking - an ABBA issue with > >>genpd->mlock and the clock API prepare_lock. > >+Cc Marek Szyprowski, > > > >The lockdep issue and display failures (including regulator warning) > >were present for some time. They also appear in boot log for > >next-20171206 (https://storage.kernelci.org/next/master/next-20171206/arm/exynos_defconfig/lab-collabora/boot-exynos5800-peach-pi.html). > >The difference is that 20171208 hangs on "random: crng init done" > >which did not appear before at all. I haven't looked at the lockdep splat yet, but is that happening because of runtime PM usage by the clk framework? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |