On 2019-05-01 09:29:44 [-0700], Tony Lindgren wrote: > Hi, > > * Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> [190501 15:37]: > > > > On 2019-04-30 13:51:40 [-0700], kernelci.org bot wrote: > > > 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 > > > > > > Checks: > > > revert: PASS > > > verify: PASS > > > > > > Parameters: > > > Tree: next > > > URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > > Branch: master > > > Target: beagle-xm > > > CPU arch: arm > > > Lab: lab-baylibre > > > Compiler: gcc-7 > > > Config: multi_v7_defconfig+CONFIG_SMP=n > > > Test suite: boot > > > > > > Breaking commit found: > > > > > > ------------------------------------------------------------------------------- > > > commit 6d25be5782e482eb93e3de0c94d0a517879377d0 > > > Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > > > Date: Wed Mar 13 17:55:48 2019 +0100 > > > > > > sched/core, workqueues: Distangle worker accounting from rq lock > > > > According to the bootlog it just stopped its output. This commit is in > > next since a week or two so I don't understand why this pops up now. > > Adding Kevin to Cc, he just confirmed on #armlinux irc that he is able to > reproduce this with CONFIG_SMP=n and root=/dev/ram0. I could not reproduce > this issue so far on omap3 with NFSroot at least. So that problem remains even that the job for today passed? > > I just revived my BBB and I can boot that commit in question. Currently > > that as close as I get to a beagle-xm. > > Looking at > > https://kernelci.org/boot/id/5cc9a64359b514a77f5584af/ > > it seems that the very same board managed to boot linux-next for > > next-20190501. > > > > Side note: I can't boot next-20190501 on my BBB, bisect points to commit > > 1a5cd7c23cc52 ("bus: ti-sysc: Enable all clocks directly during init to read revision") > > > > any idea? > > Oh interesting thanks for letting me know. Next boots fine for me here > with NFSroot on BBB. > > Do you have some output on what happens so I can investigate? Nope, the console remains dark. > Regards, > > Tony Sebastian
