From: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>, Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic@lists.infradead.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 265 boots: 17 failed, 243 passed with 4 offline, 1 conflict (next-20190717)
Date: Wed, 17 Jul 2019 12:54:01 +0100 [thread overview]
Message-ID: <20190717115401.GC4459@sirena.org.uk> (raw)
In-Reply-To: <5d2f063c.1c69fb81.69fe8.9d45@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 3112 bytes --]
On Wed, Jul 17, 2019 at 04:27:56AM -0700, kernelci.org bot wrote:
Today's -next fails to boot on meson-gxm-khadas-vim2 in a variety
of configurations:
> defconfig:
> gcc-8:
> meson-gxm-khadas-vim2:
> lab-baylibre: new failure (last pass: next-20190705)
> defconfig+CONFIG_CPU_BIG_ENDIAN=y:
> gcc-8:
> meson-gxm-khadas-vim2:
> lab-baylibre: new failure (last pass: next-20190705)
> defconfig+CONFIG_RANDOMIZE_BASE=y:
> gcc-8:
> meson-gxm-khadas-vim2:
> lab-baylibre: new failure (last pass: next-20190705)
It looks like it gets to userspace and then hangs (end of the log
below). More details at:
https://kernelci.org/boot/id/5d2ed6ad59b514a0e649e937/
Compared to working boots in mainline it looks like the main difference
is the addition of the panfrost driver but that could be a complete red
herring.
08:00:51.567064 [ 14.844034] Run /init as init process
08:00:51.590902 Starting syslogd: OK
08:00:51.645937 Starting klogd: OK
08:00:51.650193 Populating /dev using udev: [ 14.894327] udevd[214]: starting version 3.2.7
08:00:51.651409 [ 14.894906] random: udevd: uninitialized urandom read (16 bytes read)
08:00:51.652703 [ 14.899720] random: udevd: uninitialized urandom read (16 bytes read)
08:00:51.653946 [ 14.905958] random: udevd: uninitialized urandom read (16 bytes read)
08:00:51.655192 [ 14.913972] udevd[214]: specified group 'kvm' unknown
08:00:51.656495 [ 14.920901] udevd[215]: starting eudev-3.2.7
08:00:51.790817 [BL31]: tee size: 0
08:00:51.820838 [ 15.089001] meson-gx-mmc d0070000.mmc: allocated mmc-pwrseq
08:00:51.860744 [ 15.106647] meson8b-dwmac c9410000.ethernet: PTP uses main clock
08:00:51.865096 [ 15.107020] meson8b-dwmac c9410000.ethernet: no reset control found
08:00:51.866318 [ 15.114743] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
08:00:51.867556 [ 15.120434] meson8b-dwmac c9410000.ethernet: DWMAC1000
08:00:51.868872 [ 15.123055] panfrost d00c0000.gpu: clock rate = 666666666
08:00:51.870123 [ 15.125580] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
08:00:51.871365 [ 15.126609] meson-drm d0100000.vpu: Queued 2 outputs on vpu
08:00:51.903478 [ 15.131066] panfrost d00c0000.gpu: mali-t820 id 0x820 major 0x1 minor 0x0 status 0x0
08:00:51.907981 [ 15.138262] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
08:00:51.909205 [ 15.138269] meson8b-dwmac c9410000.ethernet: COE Type 2
08:00:51.910449 [ 15.143806] panfrost d00c0000.gpu: features: 00000000,101e76ff, issues: 00000000,24040400
08:00:51.911698 [ 15.145058] Bluetooth: Core ver 2.22
08:00:51.913009 [ 15.145170] NET: Registered protocol family 31
08:00:51.914253 [ 15.145175] Bluetooth: HCI device and connection manager initialized
08:00:51.919829 [ 15.145197] Bluetooth: HCI socket layer initialized
08:02:48.216650 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:20, retry in 00:02:10
08:02:48.321432 #
[-- 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-17 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d2f063c.1c69fb81.69fe8.9d45@mx.google.com>
2019-07-17 11:54 ` Mark Brown, Rob Herring, Tomeu Vizoso [this message]
2019-07-17 12:10 ` next/master boot: 265 boots: 17 failed, 243 passed with 4 offline, 1 conflict (next-20190717) Mark Brown
2019-07-17 22:00 ` Rob Clark
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=20190717115401.GC4459@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=tomeu.vizoso@collabora.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).