Automated DT boot report for various ARM defconfigs.
Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo').
Tree/Branch: linus/master Git describe: v3.12-rc2-245-g30ceb4e Commit: 30ceb4ec33 Merge tag 'usb-3.12-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
Failed boot tests (console logs at the end) =========================================== tegra30-beaver: FAIL: arm-tegra_defconfig
Full Report ===========
arm-tegra_defconfig ------------------- tegra30-beaver FAIL: 0 min 46.3 sec
arm-omap2plus_defconfig ----------------------- am335x-boneblack PASS: 0 min 29.6 sec omap3-beagle-xm PASS: 0 min 51.5 sec am335x-bone PASS: 0 min 26.3 sec omap3-tobi,3530overo PASS: 0 min 42.5 sec omap4-panda PASS: 1 min 6.5 sec omap4-panda-es PASS: 1 min 11.5 sec omap3-tobi,3730storm PASS: 0 min 41.1 sec omap3-beagle PASS: 0 min 56.1 sec
arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.3 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec imx6q-wandboard PASS: 0 min 15.0 sec
arm-multi_v7_defconfig ---------------------- tegra30-beaver PASS: 0 min 15.1 sec am335x-boneblack PASS: 0 min 34.6 sec omap3-beagle-xm PASS: 0 min 51.4 sec armada-370-mirabox PASS: 0 min 19.5 sec omap4-panda PASS: 0 min 59.8 sec omap4-panda-es PASS: 1 min 6.5 sec sun4i-a10-cubieboard PASS: 0 min 11.5 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.4 sec omap3-tobi,3530overo PASS: 0 min 40.9 sec am335x-bone PASS: 0 min 33.4 sec imx6q-wandboard PASS: 0 min 15.7 sec omap3-tobi,3730storm PASS: 0 min 40.1 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.6 sec omap3-beagle PASS: 0 min 51.1 sec
arm-exynos_defconfig -------------------- exynos5250-arndale PASS: 0 min 29.9 sec
arm-mvebu_defconfig ------------------- armada-370-mirabox PASS: 0 min 19.3 sec
arm-sama5_defconfig ------------------- sama5d35ek PASS: 0 min 18.2 sec
Console logs for failures =========================
arm-tegra_defconfig -------------------
tegra30-beaver: FAIL: last 24 lines of boot log: ------------------------------------------------
[ 3.644614] tegra-ehci 7d008000.usb: irq 129, io mem 0x7d008000 [ 3.663633] tegra-ehci 7d008000.usb: USB 2.0 started, EHCI 1.00 [ 3.670147] hub 1-0:1.0: USB hub found [ 3.673928] hub 1-0:1.0: 1 port detected [ 3.678675] tegra_rtc 7000e000.rtc: setting system clock to 1970-01-01 00:00:12 UTC (12) [ 3.687009] ALSA device list: [ 3.689967] #0: NVIDIA Tegra Beaver [ 3.693969] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00245-g30ceb4e / # [ 3.993683] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485573] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r. # PYBOOT: Time: 46.30 seconds. # PYBOOT: Result: FAIL
On 09/29/2013 06:15 PM, Kevin Hilman build bot wrote:
Automated DT boot report for various ARM defconfigs.
Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo').
arm-tegra_defconfig
...
[ 3.693969] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00245-g30ceb4e / # [ 3.993683] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485573] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r.
This seems to be failing because dmesg output is confusing the code that's searching for the command output. Perhaps dmesg could be turned off immediately after login and/or the commands retried if they time out? That said, I do see the command prompt being printed right after uname executes, so I'm not sure why the scripts are getting confused.
On Mon, Sep 30, 2013 at 8:31 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 09/29/2013 06:15 PM, Kevin Hilman build bot wrote:
Automated DT boot report for various ARM defconfigs.
Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo').
arm-tegra_defconfig
...
[ 3.693969] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00245-g30ceb4e / # [ 3.993683] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485573] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r.
This seems to be failing because dmesg output is confusing the code that's searching for the command output. Perhaps dmesg could be turned off immediately after login and/or the commands retried if they time out? That said, I do see the command prompt being printed right after uname executes, so I'm not sure why the scripts are getting confused.
My machine seems immune from it mostly because userspace takes longer to start so the asix probing happens before login prompt. ;)
But yes, a little odd that expect doesn't see the prompt there already.
-Olof
On Mon, Sep 30, 2013 at 8:31 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 09/29/2013 06:15 PM, Kevin Hilman build bot wrote:
Automated DT boot report for various ARM defconfigs.
Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo').
arm-tegra_defconfig
...
[ 3.693969] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00245-g30ceb4e / # [ 3.993683] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485573] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r.
This seems to be failing because dmesg output is confusing the code that's searching for the command output. Perhaps dmesg could be turned off immediately after login and/or the commands retried if they time out? That said, I do see the command prompt being printed right after uname executes, so I'm not sure why the scripts are getting confused.
Yeah, the prompt is definitely showing up.
I'm not sure why it's getting confused either, and seems to only happen on the jenkins triggered jobs, and not when I do launch the script manually. I'm still looking into it.
Kevin
On Mon, Sep 30, 2013 at 10:12 AM, Kevin Hilman khilman@linaro.org wrote:
On Mon, Sep 30, 2013 at 8:31 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 09/29/2013 06:15 PM, Kevin Hilman build bot wrote:
Automated DT boot report for various ARM defconfigs.
Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo').
arm-tegra_defconfig
...
[ 3.693969] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00245-g30ceb4e / # [ 3.993683] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485573] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r.
This seems to be failing because dmesg output is confusing the code that's searching for the command output. Perhaps dmesg could be turned off immediately after login and/or the commands retried if they time out? That said, I do see the command prompt being printed right after uname executes, so I'm not sure why the scripts are getting confused.
Yeah, the prompt is definitely showing up.
I'm not sure why it's getting confused either, and seems to only happen on the jenkins triggered jobs, and not when I do launch the script manually. I'm still looking into it.
Ah, it's because when it looks for the prompt, it expects a '#' at the end of line, and with more messages on the console, that isn't happening. Your suggestion of turning of console output should fix that. I'll add a 'dmesg -n1' as the first thing to do at the shell (and I wont wait for a prompt on that one, so it shouldn't fail.)
Kevin
On 09/30/2013 11:22 AM, Kevin Hilman wrote:
On Mon, Sep 30, 2013 at 10:12 AM, Kevin Hilman khilman@linaro.org wrote:
On Mon, Sep 30, 2013 at 8:31 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 09/29/2013 06:15 PM, Kevin Hilman build bot wrote:
Automated DT boot report for various ARM defconfigs.
Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo').
arm-tegra_defconfig
...
[ 3.693969] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00245-g30ceb4e / # [ 3.993683] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485573] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r.
This seems to be failing because dmesg output is confusing the code that's searching for the command output. Perhaps dmesg could be turned off immediately after login and/or the commands retried if they time out? That said, I do see the command prompt being printed right after uname executes, so I'm not sure why the scripts are getting confused.
Yeah, the prompt is definitely showing up.
I'm not sure why it's getting confused either, and seems to only happen on the jenkins triggered jobs, and not when I do launch the script manually. I'm still looking into it.
Ah, it's because when it looks for the prompt, it expects a '#' at the end of line, and with more messages on the console, that isn't happening. Your suggestion of turning of console output should fix that. I'll add a 'dmesg -n1' as the first thing to do at the shell (and I wont wait for a prompt on that one, so it shouldn't fail.)
The one risk with turning off dmesg is whether console messages are useful when diagnosing failures. I assume that oopses always show up no matter what though so perhaps it's not a big deal. Still, some other messages might be useful?
On Mon, Sep 30, 2013 at 11:09 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 09/30/2013 11:22 AM, Kevin Hilman wrote:
On Mon, Sep 30, 2013 at 10:12 AM, Kevin Hilman khilman@linaro.org wrote:
On Mon, Sep 30, 2013 at 8:31 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 09/29/2013 06:15 PM, Kevin Hilman build bot wrote:
Automated DT boot report for various ARM defconfigs.
Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo').
arm-tegra_defconfig
...
[ 3.693969] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00245-g30ceb4e / # [ 3.993683] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485573] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r.
This seems to be failing because dmesg output is confusing the code that's searching for the command output. Perhaps dmesg could be turned off immediately after login and/or the commands retried if they time out? That said, I do see the command prompt being printed right after uname executes, so I'm not sure why the scripts are getting confused.
Yeah, the prompt is definitely showing up.
I'm not sure why it's getting confused either, and seems to only happen on the jenkins triggered jobs, and not when I do launch the script manually. I'm still looking into it.
Ah, it's because when it looks for the prompt, it expects a '#' at the end of line, and with more messages on the console, that isn't happening. Your suggestion of turning of console output should fix that. I'll add a 'dmesg -n1' as the first thing to do at the shell (and I wont wait for a prompt on that one, so it shouldn't fail.)
The one risk with turning off dmesg is whether console messages are useful when diagnosing failures. I assume that oopses always show up no matter what though so perhaps it's not a big deal. Still, some other messages might be useful?
Perhaps. maybe just retrying the command is going to be more robust and provide more useful debug output.
Kevin
linaro-kernel@lists.linaro.org
-
Kevin Hilman -
Kevin Hilman build bot
-
Olof Johansson -
Stephen Warren