Some additional info about these regressions:
On 19/11/22 9:43, kernelci.org bot wrote:
platform | arch | lab | compiler | defconfig | regressions -----------------------------+-------+---------------+----------+----------------------------+------------ mt8183-kukui-...uniper-sku16 | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/plan/id/63788de1ef2d2b8b992abd08
Results: 0 PASS, 1 FAIL, 0 SKIP Full config: defconfig+arm64-chromebook Compiler: gcc-10 (aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110) Plain log: https://storage.kernelci.org//chrome-platform/for-kernelci/v6.1-rc1-14-geba7... HTML log: https://storage.kernelci.org//chrome-platform/for-kernelci/v6.1-rc1-14-geba7... Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20221...
- baseline.login: https://kernelci.org/test/case/id/63788de1ef2d2b8b992abd09 failing since 79 days (last pass: tag-chrome-platform-for-v5.20-2-gddffaa3d76750, first fail: v6.0-rc1-18-gf36a064d1483)
The boot process seems to hang during driver probing and the system doesn't reach the login prompt. More detailed testing might point to the panfrost driver as the culprit since v6.0, as using the same kernel with the same configuration except disabling CONFIG_DRM_PANFROST makes it reach the loging prompt.
platform | arch | lab | compiler | defconfig | regressions -----------------------------+-------+---------------+----------+----------------------------+------------ rk3399-gru-kevin | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 4
Details: https://kernelci.org/test/plan/id/63788ef9e66068606e2abd59
Results: 85 PASS, 7 FAIL, 0 SKIP Full config: defconfig+arm64-chromebook Compiler: gcc-10 (aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110) Plain log: https://storage.kernelci.org//chrome-platform/for-kernelci/v6.1-rc1-14-geba7... HTML log: https://storage.kernelci.org//chrome-platform/for-kernelci/v6.1-rc1-14-geba7... Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20221...
- baseline.bootrr.rockchip-i2s1-probed: https://kernelci.org/test/case/id/63788ef9e66068606e2abd7b failing since 227 days (last pass: v5.17-rc1-10-g0ef49b25b7cc, first fail: v5.18-rc1-1-gbf84b10d9901d)
Both the cros-ec accelerator and gyroscope tests fail because the IIO ABI has changed slightly since 6.0. For instance, the `deviceX/location` sysfs attribute has disappeared. This will keep failing unless the test is updated to be compatible with the new ABI.
Cheers, Ricardo