On 2019-05-01 14:48:44 [-0700], Kevin Hilman wrote: > "kernelci.org bot" <b...@kernelci.org> writes: > > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > * 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. * > > * Hope this helps! * > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > > > next/master boot bisection: next-20190430 on beagle-xm > > > > Summary: > > Start: f43b05fd4c17 Add linux-next specific files for 20190430 > > Details: https://kernelci.org/boot/id/5cc84d7359b514b7ab55847b > > Plain log: > > https://storage.kernelci.org//next/master/next-20190430/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-baylibre/boot-omap3-beagle-xm.txt > > HTML log: > > https://storage.kernelci.org//next/master/next-20190430/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-baylibre/boot-omap3-beagle-xm.html > > Result: 6d25be5782e4 sched/core, workqueues: Distangle worker > > accounting from rq lock > > I was able to reproduce this in next-20190430, but... > > I'm not sure what fixed it, but this is passing again in today's > linux-next (next-20190501)
Okay, thanks for the confirmation. > Kevin Sebastian
