linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
	linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: next/master boot: 254 boots: 11 failed, 227 passed with 16 offline (v5.3-rc4-5755-g8e72ac275c63)
Date: Mon, 12 Aug 2019 18:37:11 +0100	[thread overview]
Message-ID: <20190812173711.GN4592@sirena.co.uk> (raw)
In-Reply-To: <5d519859.1c69fb81.531c0.088a@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

On Mon, Aug 12, 2019 at 09:48:25AM -0700, kernelci.org bot wrote:

Today's -next fails to boot on qcs404-evb-4k:

> arm64:
>     defconfig:
>         gcc-8:

The boot appears to suddenly drop into a bootloader near the end of
boot:

05:14:44.500307  [    1.886858] Key type dns_resolver registered
05:14:44.500345  [    1.892544] registered taskstats version 1
05:14:44.500382  [    1.895502] Loading compiled-in X.509 certificates
05:14:44.515903  [    1.916067] hctosys: unable to open rtc device (rtc0)
05:14:51.562124  
05:14:51.562251  Format: Log Type - Time(microsec) - Message - Optional Info
05:14:51.562306  Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
05:14:51.562383  S - QC_IMAGE_VERSION_STRING=BOOT.XF.0.1-00080-QCS405LZB-2
05:14:51.562427  S - IMAGE_VARIANT_STRING=Qcs405LA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

       reply	other threads:[~2019-08-12 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5d519859.1c69fb81.531c0.088a@mx.google.com>
2019-08-12 17:37 ` Mark Brown [this message]
2019-08-12 16:48 next/master boot: 254 boots: 11 failed, 227 passed with 16 offline (v5.3-rc4-5755-g8e72ac275c63) kernelci.org bot

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=20190812173711.GN4592@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-next@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 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).