Hi Javier, Javier Martinez Canillas <javier@xxxxxxxxxxxxxxx> writes: > Hello Kevin, > > On 03/24/2017 08:57 PM, Kevin Hilman wrote: >> + Sjoerd, Javier, >> >> kernelci.org bot <bot@xxxxxxxxxxxx> writes: >> >>> stable-rc boot: 233 boots: 1 failed, 222 passed with 10 offline (v4.9.17-25-g4d90baeca3c8) >>> >>> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.17-25-g4d90baeca3c8/ >>> Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.9.17-25-g4d90baeca3c8/ >>> >>> Tree: stable-rc >>> Branch: local/linux-4.9.y >>> Git Describe: v4.9.17-25-g4d90baeca3c8 >>> Git Commit: 4d90baeca3c8aebdcb6e3ec8a6b31d4279cfbf3d >>> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >>> Tested: 62 unique boards, 16 SoC families, 24 builds out of 199 >>> >>> Boot Regressions Detected: >>> >>> arm: >>> >>> exynos_defconfig: >>> exynos5250-snow: >>> lab-collabora: new failure (last pass: v4.9.17) >> >> This one a new regression, but this board is in the Collabora lab and I >> can't currently bisect remotely. >> >> @Sjoerd, Javier: can either of you have a closer look at this? >> >> Looks like a failure in the DRM component init path. >> > > This seems to be the bug that's fixed by commit f0a8b49c03d2 ("drm/bridge: > analogix dp: Fix runtime PM state on driver bind") [0]. I thought it was > only a regression for v4.10, but it looks like that also affects v4.9. Thanks for checking. Do you plan to request a backport to stable v4.9 also? Thanks, Kevin