changing the version since this is a 5.2 issue.
Changed back to 5.1, just committed a patch to rhel5 and tested in x86_64. The patch seems to make the problem go away :)
Verified with RHEL5.2-Server-20080217.nightly.
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 the 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-2008-0397.html