Bug 437907 - (unsupported glibc) mkinitrd fails on Intel when installing 2.6.24.3-34
(unsupported glibc) mkinitrd fails on Intel when installing 2.6.24.3-34
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
8
i386 Linux
low Severity high
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-17 22:49 EDT by Bob T.
Modified: 2008-03-18 13:12 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-18 10:51:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bob T. 2008-03-17 22:49:16 EDT
Description of problem: Installing the latest kernel update hangs because of a
failure during the mkinitrd step. This only seems to happen on Intel boxes (3 so
far); on the one AMD box I have, the install was not problematic.


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


How reproducible: Consistently on the three Intel boxes I have.


Steps to Reproduce:
1.  # rpm -i kernel-2.6.24.3-34.fc8.i686.rpm 

2.  
3.
  
Actual results: The kernel itself installs, but the mkinitrd step hangs after:

nash received SIGSEGV!  Backtrace (11):
/sbin/nash[0x805314a]
[0x110440]
/lib/libglib-2.0.so.0[0x79fba1]
/usr/lib/libbdevid.so.6.0.19(bdevid_module_unload_all+0x31)[0x4ade37]
/usr/lib/libbdevid.so.6.0.19(bdevid_destroy+0x2d)[0x4ad57c]
/usr/lib/libnash.so.6.0.19[0x597174]
/usr/lib/libnash.so.6.0.19(nash_vitals_destroy_probes+0x3f)[0x5977ec]
/usr/lib/libnash.so.6.0.19(_nashFreeContext+0x1c)[0x587fc6]
/sbin/nash[0x80536e4]
/lib/libc.so.6(__libc_start_main+0xe6)[0x30c606]
/sbin/nash[0x804ae61]

After ^C:

error: %post(kernel-2.6.24.3-34.fc8.i686) scriptlet failed, signal 2





Expected results:

vmlinuz, System Map, initrd and config all installed in /boot. initrd is not.

Additional info: The same package installs normally on AMD.
Comment 1 Bob T. 2008-03-17 22:52:34 EDT
The same error backtrace occurs with

# mkinitrd initrd-2.6.24.3-34.fc8.img  2.6.24.3-34.fc8
Comment 2 Warren Togami 2008-03-17 23:20:22 EDT
What version of mkinitrd?

rpm -q mkinitrd

I am running Fedora 8 x86_64 on an Intel 945 chipset (Core 2 Duo) and I have no
issues here with this exact kernel version.
Comment 3 Bob T. 2008-03-18 03:30:45 EDT
% rpm -q mkinitrd
mkinitrd-6.0.19-4.fc8

Intel(R) Pentium(R) M processor 1.70GHz
Intel(R) Core(TM)2 CPU 6600  @ 2.40GHz
Intel(R) Core(TM)2 Duo CPU E6550  @ 2.33GHz

On the last of these, rpm -i kernel-2.6.24.3-34.fc8.i686.rpm produces

/sbin/mkinitrd: line 186:  2668 Segmentation fault $ldso --verify $bin >
/dev/null 2>&1

but goes on and the installation terminates successfully.
Comment 4 Bob T. 2008-03-18 04:15:34 EDT
The box that "only" segfaults is running glibc-2.7-2. The other two are running
glibc-2.7.90-9 (I believe installed as a dependency when I yum-installed
something from rawhide, perhaps evince). Should I revert to glibc-2.7-2? If so,
how can it be done safely?
Comment 5 Warren Togami 2008-03-18 10:45:53 EDT
There is your problem.  You mixed in core libraries from Fedora 9 into your
Fedora 8 system?  That often breaks things and is unsupported.

rpm -Uvh <every package you replaced> --oldpackage *might* do it, but it isn't
guaranteed to do so.
Comment 6 Warren Togami 2008-03-18 10:51:07 EDT
CLOSED NOTABUG unsupported glibc.
Comment 7 Bob T. 2008-03-18 13:12:36 EDT
Me bad for sure.  But mkinitrd *does* say it segfaults with glibc-2.7-2.  

Note You need to log in before you can comment on or make changes to this bug.