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.

Description of problem: nss fails build on ppc564 fails due to many core dumps while running the test suite. This is not a problem with the test. Most nss security tools core dump on ppc64.


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


How reproducible:


Steps to Reproduce:
1. On a ppc64 system execute certutil -H


Actual results: Core dump detected


Expected results: certutil displays help info


Additional info: The problem is caused by one of the recent nss-softokn patches to need latest FIPS 140 requirement. It has been investigated by Bob Relyea who has patches that solve the problem. I'll let Bob explain the causes in greater detail.

Created attachment 948190 [details]
handle no init support on ppc4

Bob's patch slightly modified on account of latest sources.

Created attachment 948192 [details]
spec file changes in patch format

Comment on attachment 948190 [details]
handle no init support on ppc4

r+ rrelyea

Comment on attachment 948192 [details]
spec file changes in patch format

r-

Created attachment 948710 [details]
spec file changes V2 - in patch format

Created attachment 948745 [details]
spec file changes V3 - in patch format

Comment on attachment 948745 [details]
spec file changes V3 - in patch format

r+ rrelyea

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://rhn.redhat.com/errata/RHBA-2015-0364.html