On Tue, Aug 25, 2015 at 09:15:10AM -0700, Tyler Baker wrote:
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=512450361ea46ed5a8c5d81f507fef094181ab91 Tested: 56 unique boards, 15 SoC families, 22 builds out of 132 *Boot Failures Detected: http://kernelci.org/boot/?next-20150825&fail http://kernelci.org/boot/?next-20150825&fail* arm: multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y: am335x-boneblack http://kernelci.org/boot/am335x-boneblack/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab at91-sama5d3_xplained http://kernelci.org/boot/at91-sama5d3_xplained/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab exynos4412-odroidx2 http://kernelci.org/boot/exynos4412-odroidx2/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab exynos5250-arndale http://kernelci.org/boot/exynos5250-arndale/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab exynos5250-snow http://kernelci.org/boot/exynos5250-snow/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab exynos5420-arndale-octa http://kernelci.org/boot/exynos5420-arndale-octa/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab exynos5422-odroidxu3 http://kernelci.org/boot/exynos5422-odroidxu3/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 2 failed labs exynos5800-peach-pi http://kernelci.org/boot/exynos5800-peach-pi/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab hip04-d01 http://kernelci.org/boot/hip04-d01/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab imx6q-cm-fx6 http://kernelci.org/boot/imx6q-cm-fx6/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab imx6q-sabrelite http://kernelci.org/boot/imx6q-sabrelite/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab imx6q-wandboard http://kernelci.org/boot/imx6q-wandboard/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab omap3-beagle-xm http://kernelci.org/boot/omap3-beagle-xm/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab omap4-panda http://kernelci.org/boot/omap4-panda/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab omap4-panda-es http://kernelci.org/boot/omap4-panda-es/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab qcom-apq8064-ifc6410 http://kernelci.org/boot/qcom-apq8064-ifc6410/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab qcom-apq8084-ifc6540 http://kernelci.org/boot/qcom-apq8084-ifc6540/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab sun7i-a20-bananapi http://kernelci.org/boot/sun7i-a20-bananapi/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab sun7i-a20-cubietruck http://kernelci.org/boot/sun7i-a20-cubietruck/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab sun9i-a80-cubieboard4 http://kernelci.org/boot/sun9i-a80-cubieboard4/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab sun9i-a80-optimus http://kernelci.org/boot/sun9i-a80-optimus/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab tegra124-jetson-tk1 http://kernelci.org/boot/tegra124-jetson-tk1/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 2 failed labs vexpress-v2p-ca15-tc1 http://kernelci.org/boot/vexpress-v2p-ca15-tc1/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab vexpress-v2p-ca15_a7 http://kernelci.org/boot/vexpress-v2p-ca15_a7/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab vexpress-v2p-ca9 http://kernelci.org/boot/vexpress-v2p-ca9/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab zynq-parallella http://kernelci.org/boot/zynq-parallella/job/next/kernel/next-20150825/defconfig/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/: 1 failed lab
I bisected these CONFIG_THUMB2_KERNEL boot failures:
Thanks for the report - I'm guessing these are all the same failure. Not yet sure what's causing it, and I don't think the updates that I've pushed out so far will address this yet.
Looking at the oops dumps you have, it's really quite annoying that they do not contain a proper backtrace. I also have to ask why your logs seem to screw up on the PC/LR values in the oops dumps - they seem to be completely missing.
From what I can tell from the oops dumps you have, the failure is in
padzero calling clear_user, which then calls __clear_user_std. That path already changes the domain register to make userspace accessible; we can see that in the register values in the oops dump, where r4 is 0x15 and r3 is 0x55. This follows the assembly I have here, where r3 will be written to the DACR, followed by an ISB, then a call to __clear_user_std before restoring it to the state saved in r4.
I wonder whether we need something stronger there, maybe a DSB to prevent the accesses trying to occur before the DACR update. I'll need to read the ARM or talk to Will about that.
In any case, let me know how tonights fair, and whether things improve.
I must admit that I don't normally look at kernelci stuff very often because I'm normally using a non-javascript enabled browser (elinks) and moving to the desktop just to look at kernelci stuff tends to be annoying. In fact, tonight is probably the first time I've looked at any kernelci results.