linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: next/master boot: 179 boots: 11 failed, 167 passed with 1 offline (next-20180731)
Date: Wed, 1 Aug 2018 13:50:27 -0700	[thread overview]
Message-ID: <20180801205027.GC24465@builder> (raw)
In-Reply-To: <20180801093102.GB5509@sirena.org.uk>

On Wed 01 Aug 02:31 PDT 2018, Mark Brown wrote:

> On Tue, Jul 31, 2018 at 09:50:37PM +0200, Niklas Cassel wrote:
> 
> > I guess it could be a bug that does not trigger on every boot,
> > or it could be a problem in the kernelci infrastructure.
> 
> Infrastructure bugs *tend* to manifest differently to this FWIW, though
> it can never be excluded.

No, that's not an infrastructure issue.

The board did warn about not finding the ath10k firmware, which is
always does, so that's not the issue - in itself. Then nothing happened
for 266 seconds, so my lab decided to terminate the agony.

So this is either an issue with the stability of next-20180731 or with
the specific board.


PS. Today's next did boot successfully on the board.

Regards,
Bjorn

      reply	other threads:[~2018-08-01 20:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5b607cc4.1c69fb81.6c1d6.6534@mx.google.com>
2018-07-31 16:06 ` next/master boot: 179 boots: 11 failed, 167 passed with 1 offline (next-20180731) Mark Brown
2018-08-01  8:19   ` Ludovic BARRE
2018-08-01  9:58     ` Ulf Hansson
2018-08-01 10:05   ` Ulf Hansson
2018-07-31 16:11 ` Mark Brown
2018-07-31 19:50   ` Niklas Cassel
2018-08-01  9:31     ` Mark Brown
2018-08-01 20:50       ` Bjorn Andersson [this message]

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=20180801205027.GC24465@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 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).