From: Mark Brown <broonie@kernel.org>
To: khilman@baylibre.com, Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-oxnas@groups.io, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730)
Date: Tue, 30 Jul 2019 13:34:25 +0100 [thread overview]
Message-ID: <20190730123425.GB4264@sirena.org.uk> (raw)
In-Reply-To: <5d403574.1c69fb81.14163.65d3@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1246 bytes --]
On Tue, Jul 30, 2019 at 05:17:56AM -0700, kernelci.org bot wrote:
> Boot Failures Detected:
>
> arm:
> oxnas_v6_defconfig:
> gcc-8:
> ox820-cloudengines-pogoplug-series-3: 1 failed lab
For some time now -next and mainline have been failing to boot on
Pogoplug 3 with the oxnas_v6_defconfig, the kernel seems to start fine
but fails to parse the ramdisk it's passed:
08:50:02.086589 <6>[ 7.719854] IP-Config: Complete:
08:50:02.087213 <6>[ 7.723330] device=eth0, hwaddr=0a:a2:89:27:10:1b, ipaddr=10.201.4.144, mask=255.255.0.0, gw=10.201.0.1
08:50:02.087413 <6>[ 7.733409] host=10.201.4.144, domain=, nis-domain=(none)
08:50:02.088056 <6>[ 7.739499] bootserver=10.201.1.1, rootserver=10.201.1.1, rootpath=
08:50:02.088248 <6>[ 7.739504] nameserver0=10.201.1.1
08:50:02.129966 <5>[ 7.752025] RAMDISK: Couldn't find valid RAM disk image starting at 0.
08:50:02.130381 <4>[ 7.759616] List of all partitions:
08:50:02.131333 <4>[ 7.763363] 0100 65536 ram0
Possibly an issue with the ramdisk getting overwritten or something?
Full details for today's -next can be seen here:
https://kernelci.org/boot/id/5d4004bb59b51489d631b28d/
[-- 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
next parent reply other threads:[~2019-07-30 12:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d403574.1c69fb81.14163.65d3@mx.google.com>
2019-07-30 12:34 ` Mark Brown [this message]
2019-08-02 13:03 ` next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730) Neil Armstrong
2019-07-30 13:00 ` Mark Brown
2019-07-30 13:28 ` Mark Brown
2019-07-30 13:41 ` Mark Brown
2019-07-31 8:48 ` Linus Walleij
2019-07-31 10:39 ` Mark Brown
2019-08-05 9:23 ` Lee Jones
2019-07-31 15:13 ` Stephen Boyd
2019-07-31 17:58 ` Jeffrey Hugo
2019-08-01 3:49 ` Timur Tabi
2019-08-01 8:09 ` Linus Walleij
2019-08-01 16:17 ` Jeffrey Hugo
2019-08-02 2:51 ` Timur Tabi
2019-08-03 9:42 ` Linus Walleij
2019-08-12 14:07 ` Jeffrey Hugo
2019-08-14 9:05 ` Linus Walleij
2019-08-05 9:20 ` Lee Jones
2019-07-31 22:40 ` Linus Walleij
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=20190730123425.GB4264@sirena.org.uk \
--to=broonie@kernel.org \
--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-oxnas@groups.io \
--cc=narmstrong@baylibre.com \
/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).