From: Mark Brown <broonie@kernel.org>
To: Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: kernel-build-reports@lists.linaro.org,
linux-next@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730)
Date: Tue, 30 Jul 2019 14:00:47 +0100 [thread overview]
Message-ID: <20190730130047.GC4264@sirena.org.uk> (raw)
In-Reply-To: <5d403574.1c69fb81.14163.65d3@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Tue, Jul 30, 2019 at 05:17:56AM -0700, kernelci.org bot wrote:
The previously reported issues with booting -next on
meson-gxm-khadas-vim2 are still present today, though seemingly only
manifesting with CONFIG_RANDOMIZE_BASE and not defconfig (there are
failures with big endian too but they don't look device specific):
> arm64:
> defconfig+CONFIG_RANDOMIZE_BASE=y:
> gcc-8:
> meson-gxm-khadas-vim2: 1 failed lab
It looks like it gets to userspace and then hangs (end of the log
below). More details at:
https://kernelci.org/boot/id/5d40069859b5148b3931b2bf/
The last message in the log indicates it was initializing the Panfrost
driver:
08:53:47.332143 <6>[ 15.172833] panfrost d00c0000.gpu: clock rate = 666666666
08:55:40.299880 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:14, retry in 00:02:07
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: kernel-build-reports@lists.linaro.org,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-next@vger.kernel.org,
Daniel Vetter <daniel@ffwll.ch>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730)
Date: Tue, 30 Jul 2019 14:00:47 +0100 [thread overview]
Message-ID: <20190730130047.GC4264@sirena.org.uk> (raw)
In-Reply-To: <5d403574.1c69fb81.14163.65d3@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
On Tue, Jul 30, 2019 at 05:17:56AM -0700, kernelci.org bot wrote:
The previously reported issues with booting -next on
meson-gxm-khadas-vim2 are still present today, though seemingly only
manifesting with CONFIG_RANDOMIZE_BASE and not defconfig (there are
failures with big endian too but they don't look device specific):
> arm64:
> defconfig+CONFIG_RANDOMIZE_BASE=y:
> gcc-8:
> meson-gxm-khadas-vim2: 1 failed lab
It looks like it gets to userspace and then hangs (end of the log
below). More details at:
https://kernelci.org/boot/id/5d40069859b5148b3931b2bf/
The last message in the log indicates it was initializing the Panfrost
driver:
08:53:47.332143 <6>[ 15.172833] panfrost d00c0000.gpu: clock rate = 666666666
08:55:40.299880 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:14, retry in 00:02:07
[-- 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
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: kernel-build-reports@lists.linaro.org,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730)
Date: Tue, 30 Jul 2019 14:00:47 +0100 [thread overview]
Message-ID: <20190730130047.GC4264@sirena.org.uk> (raw)
In-Reply-To: <5d403574.1c69fb81.14163.65d3@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
On Tue, Jul 30, 2019 at 05:17:56AM -0700, kernelci.org bot wrote:
The previously reported issues with booting -next on
meson-gxm-khadas-vim2 are still present today, though seemingly only
manifesting with CONFIG_RANDOMIZE_BASE and not defconfig (there are
failures with big endian too but they don't look device specific):
> arm64:
> defconfig+CONFIG_RANDOMIZE_BASE=y:
> gcc-8:
> meson-gxm-khadas-vim2: 1 failed lab
It looks like it gets to userspace and then hangs (end of the log
below). More details at:
https://kernelci.org/boot/id/5d40069859b5148b3931b2bf/
The last message in the log indicates it was initializing the Panfrost
driver:
08:53:47.332143 <6>[ 15.172833] panfrost d00c0000.gpu: clock rate = 666666666
08:55:40.299880 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:14, retry in 00:02:07
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-30 13:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d403574.1c69fb81.14163.65d3@mx.google.com>
2019-07-30 12:34 ` next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730) Mark Brown
2019-07-30 12:34 ` Mark Brown
2019-08-02 13:03 ` Neil Armstrong
2019-08-02 13:03 ` Neil Armstrong
2019-07-30 13:00 ` Mark Brown [this message]
2019-07-30 13:00 ` Mark Brown
2019-07-30 13:00 ` Mark Brown
2019-07-30 13:28 ` 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
2019-07-30 12:17 kernelci.org bot
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=20190730130047.GC4264@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.