Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Olof Johansson <olof@lixom.net>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	Tony Lindgren <tony@atomide.com>,
	Kevin Hilman <khilman@baylibre.com>,
	LinusW <linus.walleij@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	matthew.hart@linaro.org,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: mainline/master boot bisection: v4.19-12838-g71e56028173b on beagle-xm
Date: Wed, 7 Nov 2018 16:09:17 +0000	[thread overview]
Message-ID: <4b7922f2-6428-3011-0338-9c0662712b8a@collabora.com> (raw)
In-Reply-To: <0ca97dae-86ee-8b75-52be-09cdaea3999f@collabora.com>

On 06/11/2018 10:54, Guillaume Tucker wrote:
> On 05/11/2018 14:33, Olof Johansson wrote:
>> On Mon, Nov 5, 2018 at 1:43 AM Guillaume Tucker
>> <guillaume.tucker@collabora.com> wrote:
>>>
>>> Hi Linus,
>>>
>>> Please see below, the kernelci.org automated boot bisection found
>>> that the OMAP3 BeagleBoard-xM is failing to boot with SMP
>>> disabled and PREEMPT enabled in multi_v7_defconfig.  There is no
>>> log output after the bootloader so the kernel seems to be
>>> crashing very early on.
>>
>> Can you enable DEBUG_LL to capture what goes wrong?
> 
> Yes I've scheduled a re-run of the automated bisection with
> DEBUG_LL turned on, but the beagle-xm board is currently offline
> in lab-baylibre.  I'll keep you posted when I get some results.

Unfortunately, enabling the DEBUG_LL config didn't help.  There's
still no visible kernel log at all from the failing LAVA jobs:

    http://lava.baylibre.com:10080/scheduler/alljobs?length=25&search=lava-bisect-9638#table


This might be a hard one to debug without physical access to the
board, but please let me know if you think there's anything else
I can try.  For example, if there's a known older kernel revision
where the combination of SMP=n and PREEMPT=y worked then I could
try to run an automated boot bisection based on that.

Guillaume

>> The regression is on me. Linus sent the patch, but I was trigger happy
>> and applied it to fixes instead of letting it soak in -next longer.
>>
>> I'll revert it in our fixes branch and send it in quickly, and apply
>> it to a branch picked up by -next instead.
> 
> Ack - will also keep an eye on boot reports.
> 
> Guillaume
> 

  reply	other threads:[~2018-11-07 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5bdebe88.1c69fb81.3857a.05d1@mx.google.com>
2018-11-05  9:43 ` mainline/master boot bisection: v4.19-12838-g71e56028173b on beagle-xm Guillaume Tucker
2018-11-05 14:33   ` Olof Johansson
2018-11-06 10:54     ` Guillaume Tucker
2018-11-07 16:09       ` Guillaume Tucker [this message]
2018-11-07 16:16         ` Olof Johansson
2018-11-08 15:54           ` Tony Lindgren
2018-11-08 22:34         ` Kevin Hilman
2018-11-09  0:32           ` Olof Johansson
2018-11-09  8:52           ` Linus Walleij

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=4b7922f2-6428-3011-0338-9c0662712b8a@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=broonie@kernel.org \
    --cc=enric.balletbo@collabora.com \
    --cc=khilman@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=matthew.hart@linaro.org \
    --cc=olof@lixom.net \
    --cc=tomeu.vizoso@collabora.com \
    --cc=tony@atomide.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