Messages in this thread | | | From | Kevin Hilman <> | Subject | Re: [PATCH 4.10 00/21] 4.10.1-stable review | Date | Mon, 27 Feb 2017 12:24:36 -0800 |
| |
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Fri, Feb 24, 2017 at 10:09:22AM -0800, kernelci.org bot wrote: >> stable-rc boot: 191 boots: 2 failed, 181 passed with 8 offline (v4.10-22-g0b3f6c4ba776) >> >> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.10-22-g0b3f6c4ba776/ >> Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.10-22-g0b3f6c4ba776/ >> >> Tree: stable-rc >> Branch: local/linux-4.10.y >> Git Describe: v4.10-22-g0b3f6c4ba776 >> Git Commit: 0b3f6c4ba776c7c49564681a3b0be953cce243e3 >> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 47 unique boards, 16 SoC families, 24 builds out of 206 >> >> Boot Failures Detected: >> >> arm64: >> >> defconfig+CONFIG_RANDOMIZE_BASE=y >> apm-mustang: 1 failed lab >> juno: 1 failed lab > > Is this failure new?
It's new, but not unique to stable, also been happening in mainline for awhile:
https://kernelci.org/boot/id/58b381fd59b51450d65e8e4f/
Not sure if anyone is looking into it though, as I'm just getting back from some time off.
Kevin
| |