From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: next/master boot: 138 boots: 8 failed, 112 passed with 18 offline (next-20180619)
Date: Tue, 19 Jun 2018 15:13:24 +0100 [thread overview]
Message-ID: <20180619141324.GD11230@sirena.org.uk> (raw)
In-Reply-To: <5b290c6d.1c69fb81.fc936.98ee@mx.google.com>
On Tue, Jun 19, 2018 at 07:00:13AM -0700, kernelci.org bot wrote:
Today and yesterday's -next is failing to boot on rk3399-firefly in two
configs:
> defconfig:
> rk3399-firefly:
> lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)
> defconfig+CONFIG_RANDOMIZE_BASE=y:
> rk3399-firefly:
> lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)
The log ends with:
[ 2.629278] SWITCH_REG2: supplied by vcc3v3_sys
[ 2.633030] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
[ 2.633723] fan53555-reg: supplied by vcc_sys
[ 2.6353|] Internal error: undefined instruction: 0 [#1] PREEMPT SMP
which is rather entertaining.
The pending fixes -next branch is fine. More diagnostics can be seen
at:
https://kernelci.org/boot/id/5b28eadb59b514636d79a877/
(that's the defconfig.) Other boards don't seem to be affected, there's
some other boards that are failing but don't seem to be related.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180619/0dbabfd4/attachment.sig>
next parent reply other threads:[~2018-06-19 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5b290c6d.1c69fb81.fc936.98ee@mx.google.com>
2018-06-19 14:13 ` Mark Brown [this message]
2018-06-19 14:22 ` next/master boot: 138 boots: 8 failed, 112 passed with 18 offline (next-20180619) Sudeep Holla
2018-06-19 14:41 ` Mark Brown
2018-06-19 14:57 ` Heiko Stübner
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=20180619141324.GD11230@sirena.org.uk \
--to=broonie@kernel.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).