Created attachment 122 [details] source file of nm01 Image location: http://autobuilder.pokylinux.org/nightly/20110305-4/machines/qemu/qemuppc/ Tree/Branch: Distro/Bernard Commit: commit c192fefd868be53c20dfd8bc44e3e815cf53a10a Author: Saul Wold <sgw@linux.intel.com> Date: Fri Mar 4 18:13:50 2011 -0800 lsbsetup: Fix LIC_FILE_CHKSUM Signed-off-by: Saul Wold <sgw@linux.intel.com> The test case could pass in v1.0 M2 on qemuppc. Meanwhile, on other platform, it could pass also. The error log is as below: #### tag=nm stime=1299398989 cmdline="export TCdat=$LTPROOT/testcases/bin; nm01 " contacts="" analysis=exit <<<test_output>>> In file included from /usr/include/stdio.h:75:0, from /opt/ltp/testcases/bin/nmfile1.c:1: /usr/include/libio.h:338:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. -------System test for nm command------ -)1 nm: '/tmp/nm12685/nmfile1': No such file -)2 nm: '/tmp/nm12685/nmfile1': No such file -)3 nm: '/tmp/nm12685/nmfile1': No such file nm -f sysv: FAIL <<<execution_status>>> initiation_status="ok" duration=40 termination_type=exited termination_id=1 corefile=no cutime=3197 cstime=566 ####
Have we run this on the h/w ppc target ? There aren't any kernel changes that would trigger this, so it is either configuration, memory or something in the flags that might be triggering this. If you use the M2 kernel with the M4 userspace, what is the result ?
(In reply to comment #1) > Have we run this on the h/w ppc target ? There aren't > any kernel changes that would trigger this, so it is either > configuration, memory or something in the flags that might > be triggering this. > If you use the M2 kernel with the M4 userspace, what is > the result ? The same case could pass on real ppc target -- mpc8315e-rdb with RC2 build. cc Yi Zhao to check if he could help to try M2 kernel with M4 userspace.
Thanks for the update. This smells like another qemuppc limitation jumping up.
I re-tested it on 3 different lsb-sdk build images: M2 kernel + M4 userspace (20101218 kernel + 20110305 RC2 rootfs) 20110305 RC2 build image (I tested it again) 1.0 final release image (20110325 build) And I found the case can *pass* on all of these images. <<<test_start>>> tag=nm stime=1301226684 cmdline="export TCdat=$LTPROOT/testcases/bin; nm01 " contacts="" analysis=exit <<<test_output>>> -------System test for nm command------ -)1 -)2 -)3 -)4 -)5 -)6 -)7 -)8 nm01: PASS <<<execution_status>>> initiation_status="ok" duration=35 termination_type=exited termination_id=0 corefile=no cutime=3023 cstime=392 <<<test_end>>> So I think this issue maybe relate to bug 780
mpc8315e-rdb: Image: 1.0.1 http://autobuilder.pokylinux.org/nightly/20110513-1/machines/mpc8315e-rdb/ppc/poky-image-sato-sdk-mpc8315e-rdb-20110514125020.rootfs.tar.gz Tree/Branch: poky/bernard Run ltp: nm Result: *pass* Qemuppc: Image: 1.0.1 http://autobuilder.pokylinux.org/nightly/20110513-1/machines/qemu/qemuppc/poky-image-sato-sdk-qemuppc-20110514074939.rootfs.ext3 Run ltp: nm Result: *Pass*
Looks like this can be closed. Do you agree ? I'm assuming that this continues to pass on 1.1 ..
Close this bug now and re-open it if needed.