next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129)
next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20181129/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20181129/
Tree: next Branch: master Git Describe: next-20181129 Git Commit: 25e778835fceb547555519fc325d0e011de61202 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 56 unique boards, 20 SoC families, 21 builds out of 220
Boot Regressions Detected:
arm:
multi_v7_defconfig: tegra124-jetson-tk1: lab-baylibre-seattle: failing since 30 days (last pass: next-20181011 - first fail: next-20181029)
tegra_defconfig: tegra124-jetson-tk1: lab-baylibre-seattle: failing since 47 days (last pass: next-20181011 - first fail: next-20181012)
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y: meson-gxbb-p200: lab-baylibre: new failure (last pass: next-20181127)
Boot Failures Detected:
arm64:
defconfig mt7622-rfb1: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y mt7622-rfb1: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig: stih410-b2120: 1 offline lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y: meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab
defconfig: meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y: meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab
Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
tegra_defconfig: tegra124-jetson-tk1: lab-mhart: PASS lab-baylibre-seattle: FAIL
multi_v7_defconfig: tegra124-jetson-tk1: lab-mhart: PASS lab-baylibre-seattle: FAIL
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y: meson-gxbb-p200: lab-baylibre: FAIL lab-baylibre-seattle: PASS
--- For more info write to info@kernelci.org
On Thu, Nov 29, 2018 at 03:23:59AM -0800, kernelci.org bot wrote:
Today's -next crashes on Jetson TK1 when the Nouveau module is loaded if it can't find firmware:
[ 7.617291] nouveau 57000000.gpu: Linked as a consumer to regulator.33 [ 7.624037] nouveau 57000000.gpu: NVIDIA GK20A (0ea000a1) [ 7.629880] nouveau 57000000.gpu: imem: using IOMMU [ 7.635013] nouveau 57000000.gpu: Direct firmware load for nvidia/gk20a/fecs_inst.bin failed with error -2 [ 7.644726] nouveau 57000000.gpu: Direct firmware load for nouveau/nvea_fuc409c failed with error -2 [ 7.653960] nouveau 57000000.gpu: Direct firmware load for nouveau/fuc409c failed with error -2 [ 7.662916] nouveau 57000000.gpu: gr: failed to load fuc409c [ 7.669694] Unable to handle kernel NULL pointer dereference at virtual address 0000006c
This has been there for ~30 days but obscured by other issues. Full log and other info can be found at:
On Thu, Nov 29, 2018 at 11:44:13AM +0000, Mark Brown wrote:
On Thu, Nov 29, 2018 at 03:23:59AM -0800, kernelci.org bot wrote:
Today's -next crashes on Jetson TK1 when the Nouveau module is loaded if it can't find firmware:
[ 7.617291] nouveau 57000000.gpu: Linked as a consumer to regulator.33 [ 7.624037] nouveau 57000000.gpu: NVIDIA GK20A (0ea000a1) [ 7.629880] nouveau 57000000.gpu: imem: using IOMMU [ 7.635013] nouveau 57000000.gpu: Direct firmware load for nvidia/gk20a/fecs_inst.bin failed with error -2 [ 7.644726] nouveau 57000000.gpu: Direct firmware load for nouveau/nvea_fuc409c failed with error -2 [ 7.653960] nouveau 57000000.gpu: Direct firmware load for nouveau/fuc409c failed with error -2 [ 7.662916] nouveau 57000000.gpu: gr: failed to load fuc409c [ 7.669694] Unable to handle kernel NULL pointer dereference at virtual address 0000006c
This has been there for ~30 days but obscured by other issues. Full log and other info can be found at:
https://kernelci.org/boot/id/5bffa74b59b5148342fddd64/
This looks like the same issue that I was seeing a couple of weeks ago. There's a fix for this here:
http://patchwork.ozlabs.org/patch/993812/
Not sure if Ben's picked that up yet, though.
Thierry
On Thu, Nov 29, 2018 at 12:54:13PM +0100, Thierry Reding wrote:
This looks like the same issue that I was seeing a couple of weeks ago. There's a fix for this here:
Not sure if Ben's picked that up yet, though.
It's certainly not visible in -next and the issue is showing so guessing not.
kernel-build-reports@lists.linaro.org
-
kernelci.org bot -
Mark Brown -
Thierry Reding