RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1424707 - Test suite reports failed "Run pr19784a" test case
Summary: Test suite reports failed "Run pr19784a" test case
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: binutils
Version: 7.4
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nick Clifton
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On:
Blocks: 1425528
TreeView+ depends on / blocked
 
Reported: 2017-02-18 14:19 UTC by Miloš Prchlík
Modified: 2017-08-01 20:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-08-01 20:24:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1864 0 normal SHIPPED_LIVE binutils bug fix update 2017-08-01 18:24:14 UTC

Description Miloš Prchlík 2017-02-18 14:19:47 UTC 
Description of problem:

s390x-redhat-linux-gcc  -B/root/rpmbuild/BUILD/binutils-2.27/ld/tmpdir/ld/ -I/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -march=z196 -mtune=zEC12   -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
 --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -march=z196 -mtune=zEC12  -c /root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc/dummy.c -o tmpdir/dummy.o
Executing on host: sh -c {s390x-redhat-linux-gcc  -B/root/rpmbuild/BUILD/binutils-2.27/ld/tmpdir/ld/ -I/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc -O2 -g -pipe -Wall -Wp,-D_FORT
IFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -march=z196 -mtune=zEC12   -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexception
s -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -march=z196 -mtune=zEC12  -c /root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc/dummy.c -o tmpdir/dumm
y.o 2>&1}  /dev/null ld.tmp (timeout = 300)
spawn [open ...]
/root/rpmbuild/BUILD/binutils-2.27/ld/ld-new  -m elf64_s390  -o tmpdir/pr19784a -dynamic-linker /lib/ld64.so.1 /usr/lib/gcc/s390x-redhat-linux/4.8.5/../../../../lib64/crt1.o /usr/lib/gcc/s39
0x-redhat-linux/4.8.5/../../../../lib64/crti.o /usr/lib/gcc/s390x-redhat-linux/4.8.5/crtbegin.o -L/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc tmpdir/pr19784a.o tmpdir/libpr19784
a.so tmpdir/dummy.o -ldl -ldl  -L/usr/lib/gcc/s390x-redhat-linux/4.8.5/../../../../lib64 --start-group /usr/lib/gcc/s390x-redhat-linux/4.8.5/libgcc.a /usr/lib/gcc/s390x-redhat-linux/4.8.5/li
bgcc_eh.a -lc --end-group /usr/lib/gcc/s390x-redhat-linux/4.8.5/crtend.o /usr/lib/gcc/s390x-redhat-linux/4.8.5/../../../../lib64/crtn.o
Executing on host: sh -c {/root/rpmbuild/BUILD/binutils-2.27/ld/ld-new  -m elf64_s390  -o tmpdir/pr19784a -dynamic-linker /lib/ld64.so.1 /usr/lib/gcc/s390x-redhat-linux/4.8.5/../../../../lib
64/crt1.o /usr/lib/gcc/s390x-redhat-linux/4.8.5/../../../../lib64/crti.o /usr/lib/gcc/s390x-redhat-linux/4.8.5/crtbegin.o -L/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc tmpdir/pr
19784a.o tmpdir/libpr19784a.so tmpdir/dummy.o -ldl -ldl  -L/usr/lib/gcc/s390x-redhat-linux/4.8.5/../../../../lib64 --start-group /usr/lib/gcc/s390x-redhat-linux/4.8.5/libgcc.a /usr/lib/gcc/s
390x-redhat-linux/4.8.5/libgcc_eh.a -lc --end-group /usr/lib/gcc/s390x-redhat-linux/4.8.5/crtend.o /usr/lib/gcc/s390x-redhat-linux/4.8.5/../../../../lib64/crtn.o 2>&1}  /dev/null ld.tmp (tim
eout = 300)
spawn [open ...]
Running: tmpdir/pr19784a > tmpdir/pr19784a.out
child killed: illegal instruction
FAIL: Run pr19784a



Version-Release number of selected component (if applicable):

binutils-2.27-2.base.el7.s390x (scratch build provided by Nick)
gcc-4.8.5-11.el7.s390x


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Nick Clifton 2017-02-21 17:14:29 UTC 
The test for this particular PR is actually bogus - or rather x86_64 specific - and it was moved by its creator (H.J Lu) into the x86_64 specific linker tests some time after the 2.27 release.

I have checked in a patch to remove this test from general testing.  As it turns out there is no need to add it to the x86_64 specific tests as there already is a similar test in there.
Comment 3 Miloš Prchlík 2017-03-07 13:59:27 UTC 
Verified with binutils-2.27-6.base.el7.
Comment 4 errata-xmlrpc 2017-08-01 20:24:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1864
Note You need to log in before you can comment on or make changes to this bug.