All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	linux-next@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Kevin Hilman" <khilman@baylibre.com>
Subject: Re: next/master boot: 257 boots: 11 failed, 229 passed with 16 offline, 1 conflict (next-20190604)
Date: Sun, 9 Jun 2019 23:41:45 -0700	[thread overview]
Message-ID: <20190610064145.GS5447@atomide.com> (raw)
In-Reply-To: <20190604160018.GI2456@sirena.org.uk>

Hi,

* Mark Brown <broonie@kernel.org> [190604 16:00]:
> On Tue, Jun 04, 2019 at 07:53:04AM -0700, kernelci.org bot wrote:
> 
> Today's -next fails to boot omap2plus_defconfig on Beagle XM:
> 
> >     omap2plus_defconfig:
> >         gcc-8:
> >           omap3-beagle-xm:
> >               lab-baylibre: failing since 1 day (last pass: next-20190531 - first fail: next-20190603)
> 
> The boot fails silently with no output after the bootloader:
> 
>     https://kernelci.org/boot/id/5cf655fc59b5149acad51504/
> 
> which isn't much to go on, it does seem to have been OK in
> multi_v7_defconfig though.

Thanks for the report, adding Kevin to Cc. I think this is the same
board that seems to have started randomly failing?

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Kevin Hilman" <khilman@baylibre.com>,
	linux-omap@vger.kernel.org, linux-next@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Benoît Cousson" <bcousson@baylibre.com>
Subject: Re: next/master boot: 257 boots: 11 failed, 229 passed with 16 offline, 1 conflict (next-20190604)
Date: Sun, 9 Jun 2019 23:41:45 -0700	[thread overview]
Message-ID: <20190610064145.GS5447@atomide.com> (raw)
In-Reply-To: <20190604160018.GI2456@sirena.org.uk>

Hi,

* Mark Brown <broonie@kernel.org> [190604 16:00]:
> On Tue, Jun 04, 2019 at 07:53:04AM -0700, kernelci.org bot wrote:
> 
> Today's -next fails to boot omap2plus_defconfig on Beagle XM:
> 
> >     omap2plus_defconfig:
> >         gcc-8:
> >           omap3-beagle-xm:
> >               lab-baylibre: failing since 1 day (last pass: next-20190531 - first fail: next-20190603)
> 
> The boot fails silently with no output after the bootloader:
> 
>     https://kernelci.org/boot/id/5cf655fc59b5149acad51504/
> 
> which isn't much to go on, it does seem to have been OK in
> multi_v7_defconfig though.

Thanks for the report, adding Kevin to Cc. I think this is the same
board that seems to have started randomly failing?

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Kevin Hilman" <khilman@baylibre.com>,
	linux-omap@vger.kernel.org, linux-next@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Benoît Cousson" <bcousson@baylibre.com>
Subject: Re: next/master boot: 257 boots: 11 failed, 229 passed with 16 offline, 1 conflict (next-20190604)
Date: Sun, 9 Jun 2019 23:41:45 -0700	[thread overview]
Message-ID: <20190610064145.GS5447@atomide.com> (raw)
In-Reply-To: <20190604160018.GI2456@sirena.org.uk>

Hi,

* Mark Brown <broonie@kernel.org> [190604 16:00]:
> On Tue, Jun 04, 2019 at 07:53:04AM -0700, kernelci.org bot wrote:
> 
> Today's -next fails to boot omap2plus_defconfig on Beagle XM:
> 
> >     omap2plus_defconfig:
> >         gcc-8:
> >           omap3-beagle-xm:
> >               lab-baylibre: failing since 1 day (last pass: next-20190531 - first fail: next-20190603)
> 
> The boot fails silently with no output after the bootloader:
> 
>     https://kernelci.org/boot/id/5cf655fc59b5149acad51504/
> 
> which isn't much to go on, it does seem to have been OK in
> multi_v7_defconfig though.

Thanks for the report, adding Kevin to Cc. I think this is the same
board that seems to have started randomly failing?

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-06-10  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5cf685d0.1c69fb81.e3d89.43ae@mx.google.com>
2019-06-04 16:00 ` next/master boot: 257 boots: 11 failed, 229 passed with 16 offline, 1 conflict (next-20190604) Mark Brown
2019-06-10  6:41   ` Tony Lindgren [this message]
2019-06-10  6:41     ` Tony Lindgren
2019-06-10  6:41     ` Tony Lindgren
2019-06-04 16:23 ` Mark Brown

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=20190610064145.GS5447@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.