Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When running in a 32-bit Xen domU environment, glibc does not load the nosegneg libraries when "hwcap 1 nosegneg" is in /etc/ld.so.conf.d/nosegneg.conf
Version-Release number of selected component (if applicable): 2.12-1.2.el6
How reproducible: 100%
Steps to Reproduce (on Xen domU):
1. # echo hwcap 1 nosegneg > /etc/ld.so.conf.d/nosegneg.conf
2. # ldconfig
3. # ldd /bin/true
Actual results:
linux-gate.so.1 => (0xb7798000)
libc.so.6 => /lib/libc.so.6 (0xb76bb000)
/lib/ld-linux.so.2 (0xb7799000)
Expected results:
linux-gate.so.1 => (0xb7798000)
libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0xb7624000)
/lib/ld-linux.so.2 (0xb7799000)
Additional info:
This bug was introduced in http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=7bfa311ff51999f9e92620268e493959a2f7bfb4
Rolling back this change corrects the behavior.
Comment 2RHEL Program Management
2010-07-18 05:37:51 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0584.html
Description of problem: When running in a 32-bit Xen domU environment, glibc does not load the nosegneg libraries when "hwcap 1 nosegneg" is in /etc/ld.so.conf.d/nosegneg.conf Version-Release number of selected component (if applicable): 2.12-1.2.el6 How reproducible: 100% Steps to Reproduce (on Xen domU): 1. # echo hwcap 1 nosegneg > /etc/ld.so.conf.d/nosegneg.conf 2. # ldconfig 3. # ldd /bin/true Actual results: linux-gate.so.1 => (0xb7798000) libc.so.6 => /lib/libc.so.6 (0xb76bb000) /lib/ld-linux.so.2 (0xb7799000) Expected results: linux-gate.so.1 => (0xb7798000) libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0xb7624000) /lib/ld-linux.so.2 (0xb7799000) Additional info: This bug was introduced in http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=7bfa311ff51999f9e92620268e493959a2f7bfb4 Rolling back this change corrects the behavior.