Re: next/master boot: 265 boots: 17 failed, 243 passed with 4 offline, 1 conflict (next-20190717)

Re: next/master boot: 265 boots: 17 failed, 243 passed with 4 offline, 1 conflict (next-20190717)

[Mark Brown, Rob Herring, Tomeu Vizoso]

[-- 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

Re: next/master boot: 265 boots: 17 failed, 243 passed with 4 offline, 1 conflict (next-20190717)

[Mark Brown]

[-- 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

Re: next/master boot: 265 boots: 17 failed, 243 passed with 4 offline, 1 conflict (next-20190717)

[Rob Clark]

On Wed, Jul 17, 2019 at 5:10 AM Mark Brown <broonie@kernel.org> wrote:
>
> 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/


jfyi, Jordan tracked this down to needing:
https://patchwork.freedesktop.org/patch/314397/

BR,
-R

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel