x86_64 - can't run i386 binaries any longer

[Jeff Sheltren]

I am currently unable to run i386 packages on FC4 x86_64.  I believe this is
a new occurrence after doing an update to the latest devel packages this
morning (I'll be glad to give the full list, but it was 150+ packages).

Now when I try to run i386 binaries, they segfault.  Even trying to run
'ldd' on an i386 binary segfaults...

For example (firefox.i386):
[jeff at hell tmp]$ rpm -qi firefox
Name        : firefox                      Relocations: (not relocatable)
Version     : 1.0.3                             Vendor: Red Hat, Inc.
Release     : 2                             Build Date: Fri 15 Apr 2005
11:22:03 PM PDT
Install Date: Wed 27 Apr 2005 01:42:54 PM PDT      Build Host:
decompose.build.redhat.com
Group       : Applications/Internet         Source RPM:
firefox-1.0.3-2.src.rpm
Size        : 31210908                         License: MPL/LGPL
Signature   : DSA/SHA1, Mon 25 Apr 2005 12:36:56 PM PDT, Key ID
da84cbd430c9ecf8
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://www.mozilla.org/projects/firefox/
Summary     : Mozilla Firefox Web browser.
Description :
Mozilla Firefox is an open-source web browser, designed for standards
compliance, performance and portability.
[jeff at hell tmp]$ firefox
Segmentation fault

strace of firefox ends with:
execve("/usr/lib/firefox-1.0.3/mozilla-xremote-client",
["/usr/lib/firefox-1.0.3/mozilla-x"..., "-a", "firefox",
"xfeDoCommand(openBrowser)"], [/* 31 vars */]) = 0
[ Process PID=3604 runs in 32 bit mode. ]
brk(0)                                  = 0x804c000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

ldd gives:
[jeff at hell firefox-1.0.3]$ pwd
/usr/lib/firefox-1.0.3
[jeff at hell firefox-1.0.3]$ ldd firefox-bin
/usr/bin/ldd: line 116:  3639 Segmentation fault
LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW=
LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$@"

I get similar results with other i386 binaries.  I am positive that I could
run them before on this machine (running FC4); the problem is I'm not
exactly sure when this stopped working, so it makes it hard to figure out
the cause.  The problem persists on both kernel-smp-2.6.11-1.1261_FC4 and
kernel-smp-2.6.11-1.1268_FC4

Any ideas?  Let me know if you need more info.

Thanks,
Jeff