From: Mark Brown <broonie@kernel.org>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.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 13:10:02 +0100 [thread overview]
Message-ID: <20190717121002.GD4459@sirena.org.uk> (raw)
In-Reply-To: <5d2f063c.1c69fb81.69fe8.9d45@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1470 bytes --]
On Wed, Jul 17, 2019 at 04:27:56AM -0700, kernelci.org bot wrote:
Today's -next fails to boot on a couple of apq8064 boards:
> arm:
> qcom_defconfig:
> gcc-8:
> qcom-apq8064-cm-qs600: 1 failed lab
> qcom-apq8064-ifc6410: 1 failed lab
In both cases it looks like the error handling when we fail to get the
firmware for the GPU is broken, we get a crash in the initialization
code shortly after failing to load some firmware:
[ 4.608279] msm 5100000.mdp: Direct firmware load for qcom/a300_pm4.fw failed with error -2
[ 4.614916] msm 5100000.mdp: [drm:adreno_request_fw] *ERROR* failed to load a300_pm4.fw
[ 4.623229] 8<--- cut here ---
[ 4.631111] Unable to handle kernel NULL pointer dereference at virtual address 00000088
...
[ 4.665947] Workqueue: events deferred_probe_work_func
[ 4.670532] PC is at msm_open+0x64/0x90
[ 4.675656] LR is at _raw_write_unlock+0x20/0x4c
...
[ 4.949553] [] (msm_open) from [] (drm_file_alloc+0x134/0x21c)
[ 4.957703] [] (drm_file_alloc) from [] (drm_client_init+0xa8/0x124)
[ 4.965162] [] (drm_client_init) from [] (drm_fb_helper_init.part.0+0x30/0x3c)
[ 4.973411] [] (drm_fb_helper_init.part.0) from [] (msm_fbdev_init+0x50/0xb4)
[ 4.982173] [] (msm_fbdev_init) from [] (msm_drm_bind+0x560/0x638)
Full details (including full boot logs) at:
https://kernelci.org/boot/id/5d2ede2359b514a54b49e91b/
https://kernelci.org/boot/id/5d2ede2759b514a54749e91d/
[-- 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 prev parent reply other threads:[~2019-07-17 12:10 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 ` next/master boot: 265 boots: 17 failed, 243 passed with 4 offline, 1 conflict (next-20190717) Mark Brown, Rob Herring, Tomeu Vizoso
2019-07-17 12:10 ` Mark Brown [this message]
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=20190717121002.GD4459@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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).