poky: master:9de0ad47462c13ac4a2d73e12e92be6c1b4e0415 1. download beagleboard "core-image-sato-sdk" image from http://autobuilder.yoctoproject.org/pub/nightly/20130731-1/machines/beagleboard/ 2. boot up a beagleboard xm target 3. execute below commands to test cd /opt/ltp/testcases/open_posix_testsuite/ make generate-makefiles 4. the make has errors(Segmentation fault). Detail error info, please check below log. This is a regression issue. When i test it on 20130618-2 image, the test pass. =======test log======================== root@beagleboard:~# cd /opt/ltp/testcases/open_posix_testsuite/ s ot@beagleboard:/opt/ltp/testcases/open_posix_testsuite# make generate-makefile make[1]: Entering directory `/opt/ltp/testcases/open_posix_testsuite/conformance' make[2]: Entering directory `/opt/ltp/testcases/open_posix_testsuite/conformance/behavior' make[2]: Leaving directory `/opt/ltp/testcases/open_posix_testsuite/conformance/behavior' make[2]: Entering directory `/opt/ltp/testcases/open_posix_testsuite/conformance/definitions' make[2]: Leaving directory `/opt/ltp/testcases/open_posix_testsuite/conformance/definitions' make[2]: Entering directory `/opt/ltp/testcases/open_posix_testsuite/conformance/interfaces' make[2]: Leaving directory `/opt/ltp/testcases/open_posix_testsuite/conformance/interfaces' make[1]: Leaving directory `/opt/ltp/testcases/open_posix_testsuite/conformance' make[1]: Entering directory `/opt/ltp/testcases/open_posix_testsuite/functional' make[1]: Leaving directory `/opt/ltp/testcases/open_posix_testsuite/functional' make[1]: Entering directory `/opt/ltp/testcases/open_posix_testsuite/stress' make[1]: Leaving directory `/opt/ltp/testcases/open_posix_testsuite/stress' Generating buildonly Makefiles make: *** [generate-makefiles] Segmentation fault check /var/log/messages, it has below info: Jul 31 11:05:27 beagleboard user.alert kernel: Unable to handle kernel paging request at virtual address b7911a08 Jul 31 11:05:27 beagleboard user.alert kernel: pgd = dda24000 Jul 31 11:05:27 beagleboard user.alert kernel: [b7911a08] *pgd=00000000 Jul 31 11:05:27 beagleboard user.emerg kernel: Internal error: Oops: 5 [#1] ARM Jul 31 11:05:27 beagleboard user.warn kernel: Modules linked in: xt_connmark iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle iptable_filter ip_tables x_tables nfnetlink nls_iso8859 Jul 31 11:05:27 beagleboard user.warn kernel: CPU: 0 Not tainted (3.4.52-yocto-standard #1) Jul 31 11:05:27 beagleboard user.warn kernel: PC is at copy_process.part.56+0xaf0/0xe3c Jul 31 11:05:27 beagleboard user.warn kernel: LR is at recalc_sigpending+0x28/0x78 Jul 31 11:05:27 beagleboard user.warn kernel: pc : [<c00368e4>] lr : [<c0046d84>] psr: 200f0093 Jul 31 11:05:27 beagleboard user.warn kernel: sp : dd9f1ef0 ip : dd9f0030 fp : dd9f1f44 Jul 31 11:05:27 beagleboard user.warn kernel: r10: 00000000 r9 : de46cbd0 r8 : dda00000 Jul 31 11:05:27 beagleboard user.warn kernel: r7 : dda00240 r6 : c08dcbe4 r5 : c091dbc0 r4 : 01200011 Jul 31 11:05:27 beagleboard user.warn kernel: r3 : b79119ec r2 : dda00214 r1 : dd9f1eec r0 : dd9f1eec Jul 31 11:05:27 beagleboard user.warn kernel: Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user Jul 31 11:05:27 beagleboard user.warn kernel: Control: 10c5387d Table: 9da24019 DAC: 00000015 Jul 31 11:05:27 beagleboard user.emerg kernel: Process generate-makefi (pid: 601, stack limit = 0xdd9f02f0) Jul 31 11:05:27 beagleboard user.emerg kernel: Stack: (0xdd9f1ef0 to 0xdd9f2000) Jul 31 11:05:27 beagleboard user.emerg kernel: 1ee0: dd9f1fb0 c0046d84 dda00278 00000000 Jul 31 11:05:27 beagleboard user.emerg kernel: 1f00: dda00200 dd9f0030 dd9f1fb0 00000000 dd9f1f3c fffffff4 c0047d18 00000000 Jul 31 11:05:27 beagleboard user.emerg kernel: 1f20: beb4f498 01200011 dd9f1fb0 00000000 dd9f0000 00000000 dd9f1f8c dd9f1f48 Jul 31 11:05:27 beagleboard user.emerg kernel: 1f40: c0036da8 c0035e00 b6f4b3f8 dd9f1eec 00000000 dd9f0000 00000000 beb4f540 Jul 31 11:05:27 beagleboard user.emerg kernel: 1f60: 00000008 00000000 b6f4b3f8 00000000 45dc5440 00000078 c000e468 dd9f0000 Jul 31 11:05:27 beagleboard user.emerg kernel: 1f80: dd9f1fa4 dd9f1f90 c0012068 c0036c94 00000000 b6f4b3f8 00000000 dd9f1fa8 Jul 31 11:05:27 beagleboard user.emerg kernel: 1fa0: c000e200 c001203c b6f4b3f8 dd9f1fb0 01200011 00000000 00000000 00000000 Jul 31 11:05:27 beagleboard user.emerg kernel: 1fc0: b6f4b3f8 00000000 45dc5440 00000078 b6f4b850 00000259 000d6204 beb4f4b4 Jul 31 11:05:27 beagleboard user.emerg kernel: 1fe0: 00000000 beb4f498 b6f4b390 45d2dd00 600f0010 01200011 00000000 00000000 Jul 31 11:05:27 beagleboard user.warn kernel: [<c00368e4>] (copy_process.part.56+0xaf0/0xe3c) from [<c0036da8>] (do_fork+0x120/0x340) Jul 31 11:05:27 beagleboard user.warn kernel: [<c0036da8>] (do_fork+0x120/0x340) from [<c0012068>] (sys_clone+0x38/0x40) Jul 31 11:05:27 beagleboard user.warn kernel: [<c0012068>] (sys_clone+0x38/0x40) from [<c000e200>] (ret_fast_syscall+0x0/0x30) Jul 31 11:05:27 beagleboard user.emerg kernel: Code: e51bc040 e59b0008 e5913004 e0813203 (e593301c) Jul 31 11:05:27 beagleboard user.warn kernel: ---[ end trace d933642216210269 ]--- Jul 31 11:05:50 beagleboard daemon.info avahi-daemon[459]: Withdrawing workstation service for tun6to4. Jul 31 11:05:50 beagleboard daemon.info connmand[404]: tun6to4 {newlink} index 4 address 80:E0:A2:B6:08:00 mtu 1472 Jul 31 11:05:50 beagleboard daemon.info connmand[404]: tun6to4 {newlink} index 4 operstate 2 <DOWN> Jul 31 11:05:50 beagleboard daemon.info connmand[404]: tun6to4 {dellink} index 4 operstate 2 <DOWN> Jul 31 11:05:51 beagleboard auth.info sshd[559]: Accepted none for root from 128.224.162.247 port 56622 ssh2 Jul 31 11:05:51 beagleboard auth.info sshd[879]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory Jul 31 11:05:51 beagleboard auth.info sshd[879]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Yi, Do you have more than one beagle board or are you seeing this failure and the 4985 on the same hardware? Can you try a different beagleboard? This might be a hardware issue.
(In reply to comment #1) > Yi, Do you have more than one beagle board or are you seeing this failure > and the 4985 on the same hardware? Can you try a different beagleboard? > This might be a hardware issue. Hi Saul, We have 1 beagleboard xM and 2 beagleboard C4. We ran the test on these 2 boards and this issue happened on both of them. Yi
Hi Saul, I've done this test with below scenarios: 1. test 20130731-1 images, kernel is 3.4.52, poky is 9de0ad47462c13ac4a2d73e12e92be6c1b4e0415, test failed. 2. test 20130618-2 images, kernel is 3.4.36, poky is 590010a6525b0e1bc1de73e794764e23404591df, test pass. 3. Use scenario 1 image, downgrade kernel version with scenario 2(cp uImage, MLO files and /lib/modules/ files), which means use 3.4.36 kernel and 3.4.52 rootfs, test pass. 4. Use scenario 2 image, upgrade kernel version with scenario 1(cp uImage, MLO files and /lib/modules/ files), which means use 3.4.52 kernel and 3.4.36 rootfs, test failed. I tested all above on a same beagleboard xm target. So we guess this is not a hardware issue, it is the 3.4.52 kernel issue.
resolving this, since 3.10 is now the default. We have no cycles to investigate these on 3.4.