linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: khilman@baylibre.com, Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, linux-next@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	kernel-build-reports@lists.linaro.org
Subject: Re: 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>


[-- Attachment #1.1: Type: text/plain, Size: 1085 bytes --]

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.

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

       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
     [not found]     ` <69c0adb9-b784-4f73-fcc9-ff1a01ce27c5-5wv7dgnIgG8@public.gmane.org>
2018-06-19 14:41       ` Mark Brown
     [not found]         ` <20180619144143.GE11230-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
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=heiko@sntech.de \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-rockchip@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).