On 10/08/2016 09:11 AM, Kevin Hilman wrote:
Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> writes:
On Fri, Oct 07, 2016 at 03:26:04PM -0700, kernelci.org bot wrote:
stable-rc boot: 479 boots: 4 failed, 183 passed with 292 offline (v4.8-11-ge141008f62ab)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.8-11-ge141008f62ab/
Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.8-11-ge141008f62ab/
Tree: stable-rc
Branch: local/linux-4.8.y
Git Describe: v4.8-11-ge141008f62ab
Git Commit: e141008f62abab72c15b093d97a88f37c8cd7096
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 86 unique boards, 23 SoC families, 33 builds out of 206
Boot Failures Detected: https://kernelci.org/boot/?v4.8-11-ge141008f62ab&fail
arm:
mxs_defconfig:
imx23-olinuxino: 1 failed lab
This one looks like lab-specific intermittent failures, not related to
the this kernel.
multi_v7_defconfig+CONFIG_SMP=n:
imx6q-sabrelite: 1 failed lab
The CONFIG_SMP=n boots for this board have been failing for awhile, so
this isn't related to stable-rc
multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
vexpress-v2p-ca15-tc1: 1 failed lab
vexpress-v2p-ca15_a7: 1 failed lab
These builds are known broken an QEMU need to be blacklisted until we
find out what's going on.
Is this with qemu or on a real board ?
If with qemu, what is your qemu version ?
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html