From: Mark Brown <broonie@kernel•org>
To: Maxime Ripard <maxime.ripard@bootlin•com>, Chen-Yu Tsai <wens@csie•org>
Cc: linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
kernel-build-reports@lists•infradead.org
Subject: Re: next/master boot: 257 boots: 11 failed, 229 passed with 16 offline, 1 conflict (next-20190604)
Date: Tue, 4 Jun 2019 17:23:53 +0100 [thread overview]
Message-ID: <20190604162353.GJ2456@sirena.org.uk> (raw)
In-Reply-To: <5cf685d0.1c69fb81.e3d89.43ae@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 962 bytes --]
On Tue, Jun 04, 2019 at 07:53:04AM -0700, kernelci.org bot wrote:
The past week of -next has been failing to boot on the h2 and h3 plus
boards:
> sunxi_defconfig:
> gcc-8:
> sun8i-h2-plus-libretech-all-h3-cc:
> lab-baylibre: failing since 7 days (last pass: next-20190523 - first fail: next-20190528)
> sun8i-h3-libretech-all-h3-cc:
> lab-baylibre: failing since 7 days (last pass: next-20190524 - first fail: next-20190528)
In both cases it seems like it boots quite a way through but hangs at
some point trying to get userspace:
https://kernelci.org/boot/id/5cf6569859b5149b53d514fd/
https://kernelci.org/boot/id/5cf6569959b5149b53d514fe/
multi_v7_defconfig comes up fine on those systems, looking at the boot
reports for them it jumps out at me that the regulators never appear and
things like MMC that use them don't either:
https://kernelci.org/boot/id/5cf6550659b514995fd51538/
[-- 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
prev parent reply other threads:[~2019-06-04 16:23 UTC|newest]
Thread overview: 3+ 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
2019-06-04 16:23 ` Mark Brown [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=20190604162353.GJ2456@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)infradead.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=maxime.ripard@bootlin$(echo .)com \
--cc=wens@csie$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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