Hi Krzysztof, On 07.10.2019 19:09, Krzysztof Kozlowski wrote: > On Mon, 7 Oct 2019 at 02:43, kernelci.org bot <bot@xxxxxxxxxxxx> wrote: >> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * >> * This automated bisection report was sent to you on the basis * >> * that you may be involved with the breaking commit it has * >> * found. No manual investigation has been done to verify it, * >> * and the root cause of the problem may be somewhere else. * >> * * >> * If you do send a fix, please include this trailer: * >> * Reported-by: "kernelci.org bot" <bot@xxxxxxxxxxxx> * >> * * >> * Hope this helps! * >> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * >> >> krzysztof/for-next boot bisection: v5.4-rc1-48-g0bc9c79979ea on peach-pi >> >> Summary: >> Start: 0bc9c79979ea Merge branch 'for-v5.5/memory-samsung-dmc-dt' into for-next >> Details: https://protect2.fireeye.com/url?k=57d30a4c-0ab44e6a-57d28103-0cc47a31384a-5c0d93fa4eb95f2e&u=https://kernelci.org/boot/id/5d9a50af59b5141ce5857c07 >> Plain log: https://protect2.fireeye.com/url?k=7e18d090-237f94b6-7e195bdf-0cc47a31384a-b693d6da384e8a14&u=https://storage.kernelci.org//krzysztof/for-next/v5.4-rc1-48-g0bc9c79979ea/arm/multi_v7_defconfig/gcc-8/lab-collabora/boot-exynos5800-peach-pi.txt >> HTML log: https://protect2.fireeye.com/url?k=e9c39b5b-b4a4df7d-e9c21014-0cc47a31384a-5f31e671f969cef8&u=https://storage.kernelci.org//krzysztof/for-next/v5.4-rc1-48-g0bc9c79979ea/arm/multi_v7_defconfig/gcc-8/lab-collabora/boot-exynos5800-peach-pi.html >> Result: 0899a480ac65 ARM: dts: exynos: Add initial data for coupled regulators for Exynos5422/5800 > Thanks for the report. Marek Szyprowski reported it on last Friday. I > dropped the patch as of now as it exposes some deadlock in regulator > code. Thanks for dropping this patch. This turned out to be an issue in the regulator core logic, not the deadlock as I initially suspected. See https://lkml.org/lkml/2019/10/8/265 for more details. I will send an updated version of this patch, because it turned out that the v7 had incorrectly resolved conflicts and in case of Odroids coupling were added to wrong regulators, what hide the issue in my initial tests on Odroid XU4. Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland
