From: Tony Lindgren <tony@atomide.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "kernelci.org bot" <bot@kernelci.org>, Tejun Heo <tj@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
tomeu.vizoso@collabora.com, guillaume.tucker@collabora.com,
mgalka@collabora.com, Thomas Gleixner <tglx@linutronix.de>,
broonie@kernel.org, matthew.hart@linaro.org,
khilman@baylibre.com, enric.balletbo@collabora.com,
Ingo Molnar <mingo@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Kevin Hilman <khilman@kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: next/master boot bisection: next-20190430 on beagle-xm
Date: Wed, 1 May 2019 09:29:44 -0700 [thread overview]
Message-ID: <20190501162944.GW8004@atomide.com> (raw)
In-Reply-To: <20190501153711.pxmapo2k3n5ynqrc@linutronix.de>
Hi,
* Sebastian Andrzej Siewior <bigeasy@linutronix.de> [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@linutronix.de>
> > 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.
> 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?
Regards,
Tony
next prev parent reply other threads:[~2019-05-01 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 20:51 next/master boot bisection: next-20190430 on beagle-xm kernelci.org bot
2019-05-01 15:37 ` Sebastian Andrzej Siewior
2019-05-01 16:29 ` Tony Lindgren [this message]
2019-05-01 16:44 ` Sebastian Andrzej Siewior
2019-05-01 16:52 ` Tony Lindgren
2019-05-01 17:01 ` Sebastian Andrzej Siewior
2019-05-01 17:44 ` Tony Lindgren
2019-05-01 19:03 ` Sebastian Andrzej Siewior
2019-05-01 20:21 ` Tony Lindgren
2019-05-01 21:13 ` Sebastian Andrzej Siewior
2019-05-01 21:17 ` Tony Lindgren
2019-05-01 21:48 ` Kevin Hilman
2019-05-02 7:16 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190501162944.GW8004@atomide.com \
--to=tony@atomide.com \
--cc=bigeasy@linutronix.de \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=hannes@cmpxchg.org \
--cc=jiangshanlai@gmail.com \
--cc=khilman@baylibre.com \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=mgalka@collabora.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tomeu.vizoso@collabora.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).