next boot: 292 boots: 11 failed, 281 passed (next-20150520)
Full Boot Summary: http://kernelci.org/boot/all/job/next/kernel/next-20150520/ Full Build Summary: http://kernelci.org/build/next/kernel/next-20150520/
Tree: next Branch: local/master Git Describe: next-20150520 Git Commit: 0ebc274769c2defec75283dce930e887ead25abd Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 72 unique boards, 21 SoC families, 26 builds out of 133
Boot Failures Detected: http://kernelci.org/boot/?next-20150520&fail
arm:
multi_v7_defconfig: at91-sama5d3_xplained: 2 failed labs at91-sama5d4ek: 1 failed lab sama5d35ek: 1 failed lab
imx_v6_v7_defconfig: imx6q-sabrelite: 1 failed lab
multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: at91-sama5d3_xplained: 2 failed labs at91-sama5d4ek: 1 failed lab sama5d35ek: 1 failed lab
exynos_defconfig: exynos5800-peach-pi_rootfs:mmc: 1 failed lab
shmobile_defconfig: emev2-kzm9d: 1 failed lab
--- For more info write to info@kernelci.org
Le 20/05/2015 15:53, kernelci.org bot a écrit :
*next boot: 292 boots: 11 failed, 281 passed (next-20150520)* Full Boot Summary: http://kernelci.org/boot/all/job/next/kernel/next-20150520/ Full Build Summary: http://kernelci.org/build/next/kernel/next-20150520/ Tree: next Branch: local/master Git Describe: next-20150520 Git Commit: 0ebc274769c2defec75283dce930e887ead25abd Git URL: 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=0ebc274769c2defec75283dce930e887ead25abd Tested: 72 unique boards, 21 SoC families, 26 builds out of 133
*Boot Failures Detected: http://kernelci.org/boot/?next-20150520&fail* arm: multi_v7_defconfig: at91-sama5d3_xplained http://kernelci.org/boot/at91-sama5d3_xplained/job/next/kernel/next-20150520/defconfig/multi_v7_defconfig/: 2 failed labs at91-sama5d4ek http://kernelci.org/boot/at91-sama5d4ek/job/next/kernel/next-20150520/defconfig/multi_v7_defconfig/: 1 failed lab sama5d35ek http://kernelci.org/boot/sama5d35ek/job/next/kernel/next-20150520/defconfig/multi_v7_defconfig/:
[..]
Hi,
For the multi* defconfig on AT91, we need to move from ttyS0 to ttyAT0 which is the name of the Atmel's serial line.
So, as we didn't move to "stdout-path" property in DT, the cmdline and the rootfs inittab certainly have to be changed. I don't know if it's possible on your side.
Bye,
Hi Nicolas,
On 20 May 2015 at 07:35, Nicolas Ferre nicolas.ferre@atmel.com wrote:
Le 20/05/2015 15:53, kernelci.org bot a écrit :
*next boot: 292 boots: 11 failed, 281 passed (next-20150520)* Full Boot Summary: http://kernelci.org/boot/all/job/next/kernel/next-20150520/ Full Build Summary: http://kernelci.org/build/next/kernel/next-20150520/ Tree: next Branch: local/master Git Describe: next-20150520 Git Commit: 0ebc274769c2defec75283dce930e887ead25abd Git URL: 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=0ebc274769c2defec75283dce930e887ead25abd Tested: 72 unique boards, 21 SoC families, 26 builds out of 133
*Boot Failures Detected: http://kernelci.org/boot/?next-20150520&fail* arm: multi_v7_defconfig: at91-sama5d3_xplained http://kernelci.org/boot/at91-sama5d3_xplained/job/next/kernel/next-20150520/defconfig/multi_v7_defconfig/: 2 failed labs at91-sama5d4ek http://kernelci.org/boot/at91-sama5d4ek/job/next/kernel/next-20150520/defconfig/multi_v7_defconfig/: 1 failed lab sama5d35ek http://kernelci.org/boot/sama5d35ek/job/next/kernel/next-20150520/defconfig/multi_v7_defconfig/:
[..]
Hi,
For the multi* defconfig on AT91, we need to move from ttyS0 to ttyAT0 which is the name of the Atmel's serial line.
Will this also change for sama5_defconfig? Seems that it uses ttyS0 still.
So, as we didn't move to "stdout-path" property in DT, the cmdline and the rootfs inittab certainly have to be changed. I don't know if it's possible on your side.
Bye,
Nicolas Ferre _______________________________________________ Kernel-build-reports mailing list Kernel-build-reports@lists.linaro.org https://lists.linaro.org/mailman/listinfo/kernel-build-reports
Cheers,
Tyler
Hi,
On 20/05/2015 at 07:59:27 -0700, Tyler Baker wrote :
Will this also change for sama5_defconfig? Seems that it uses ttyS0 still.
I'm not sure that is the plan because it means updating a lot of documentation on their side.
However, I'm all in favor of killing CONFIG_SERIAL_ATMEL_TTYAT and switch everyone to ttyATx .
Note that digicolor will have the same issue and will not work in any configuration that also include the 8250 driver.
It will also be the same for bcm63x and pnx8xxx but you probably don't care as those are mips platforms.
Hi,
On 20 May 2015 at 09:14, Alexandre Belloni alexandre.belloni@free-electrons.com wrote:
Hi,
On 20/05/2015 at 07:59:27 -0700, Tyler Baker wrote :
Will this also change for sama5_defconfig? Seems that it uses ttyS0 still.
I'm not sure that is the plan because it means updating a lot of documentation on their side.
For now, adding both console parameters to the kernel cmdline is an OK workaround as Kevin mentioned. I've re-pushed my boot results to reflect this change.
However, I'm all in favor of killing CONFIG_SERIAL_ATMEL_TTYAT and switch everyone to ttyATx .
I agree, it would be nice to have all the boards using the same tty, at least from an automation perspective.
Note that digicolor will have the same issue and will not work in any configuration that also include the 8250 driver.
It will also be the same for bcm63x and pnx8xxx but you probably don't care as those are mips platforms.
If we had the hardware, we would boot it :)
Cheers,
Tyler
On Wed, May 20, 2015 at 7:35 AM, Nicolas Ferre nicolas.ferre@atmel.com wrote:
For the multi* defconfig on AT91, we need to move from ttyS0 to ttyAT0 which is the name of the Atmel's serial line.
So, as we didn't move to "stdout-path" property in DT, the cmdline and the rootfs inittab certainly have to be changed. I don't know if it's possible on your side.
We need to run old and new kernels on these boards, so on my side I've just added both console= arguments on the command line, and that works.
I re-ran all the at91 platforms from my lab and things look back to normal: http://kernelci.org/boot/all/job/next/kernel/next-20150520/
Kevin
kernel-build-reports@lists.linaro.org