On Sun, 2014-10-05 at 11:36PM +0000, Kevin's boot bot wrote:
Status report database: http://status.armcloud.us/boot/all/job/stable/kernel/v3.10.56/
Tree/Branch: stable Git describe: v3.10.56 Failed boot tests ================= omap3-n900,legacy: FAIL: arm-omap2plus_defconfig http://armcloud.us/kernel-ci/stable/v3.10.56/arm-omap2plus_defconfig/boot-om... zynq-zc702: FAIL: arm-multi_v7_defconfig http://armcloud.us/kernel-ci/stable/v3.10.56/arm-multi_v7_defconfig/boot-zyn...
Zynq should no longer fail - at least not this silently - since Greg added the patch enabling Zynq's UART driver. The name of the console device changed from ttyPS1 in this old to ttyPS0 in more recent kernels which causes a little trouble with my ramdisk and the getty process not being available, but I get all the messages from the kernel. I also downloaded the zImage and DT from the CI system, they work fine for me until the userspace handoff.
Sören
On Mon, Oct 6, 2014 at 9:22 AM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Sun, 2014-10-05 at 11:36PM +0000, Kevin's boot bot wrote:
Status report database: http://status.armcloud.us/boot/all/job/stable/kernel/v3.10.56/
Tree/Branch: stable Git describe: v3.10.56 Failed boot tests ================= omap3-n900,legacy: FAIL: arm-omap2plus_defconfig http://armcloud.us/kernel-ci/stable/v3.10.56/arm-omap2plus_defconfig/boot-om... zynq-zc702: FAIL: arm-multi_v7_defconfig http://armcloud.us/kernel-ci/stable/v3.10.56/arm-multi_v7_defconfig/boot-zyn...
Zynq should no longer fail - at least not this silently - since Greg added the patch enabling Zynq's UART driver. The name of the console device changed from ttyPS1 in this old to ttyPS0 in more recent kernels which causes a little trouble with my ramdisk and the getty process not being available, but I get all the messages from the kernel. I also downloaded the zImage and DT from the CI system, they work fine for me until the userspace handoff.
Ah, I was booting with a fixed command line (overriding what was in the DTB) using console=ttyPS0, which explains why there was no output. I've removed my command-line for this board and will just use the DTB default now. That seems to work on the stable v3.10.y and on current mainline.
Thanks for the tip,
Kevin
On Tue, 2014-10-07 at 02:58PM -0700, Kevin Hilman wrote:
On Mon, Oct 6, 2014 at 9:22 AM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Sun, 2014-10-05 at 11:36PM +0000, Kevin's boot bot wrote:
Status report database: http://status.armcloud.us/boot/all/job/stable/kernel/v3.10.56/
Tree/Branch: stable Git describe: v3.10.56 Failed boot tests ================= omap3-n900,legacy: FAIL: arm-omap2plus_defconfig http://armcloud.us/kernel-ci/stable/v3.10.56/arm-omap2plus_defconfig/boot-om... zynq-zc702: FAIL: arm-multi_v7_defconfig http://armcloud.us/kernel-ci/stable/v3.10.56/arm-multi_v7_defconfig/boot-zyn...
Zynq should no longer fail - at least not this silently - since Greg added the patch enabling Zynq's UART driver. The name of the console device changed from ttyPS1 in this old to ttyPS0 in more recent kernels which causes a little trouble with my ramdisk and the getty process not being available, but I get all the messages from the kernel. I also downloaded the zImage and DT from the CI system, they work fine for me until the userspace handoff.
Ah, I was booting with a fixed command line (overriding what was in the DTB) using console=ttyPS0, which explains why there was no output. I've removed my command-line for this board and will just use the DTB default now. That seems to work on the stable v3.10.y and on current mainline.
Thanks for the tip,
Awesome. Thanks for checking.
Sören
linaro-kernel@lists.linaro.org
-
Kevin Hilman -
Sören Brinkmann