Red Hat Bugzilla – Bug 440091
init segfaults at boot on system upgraded from F8
Last modified: 2008-04-17 02:29:00 EDT
I upgraded my system from F8 to rawhide using preupgrade.
At boot I get the following message from init:
init: segfault at d ip 004a266b sp bfa52b60 error 4 in
Bootup hangs at this point.
What happens if you boot with enforcing=0/selinux=0?
If you boot with init=/bin/bash and do:
rpm -V upstart event-compat-sysv
what do you see?
(In reply to comment #0)
> I upgraded my system from F8 to rawhide using preupgrade.
> At boot I get the following message from init:
> init: segfault at d ip 004a266b sp bfa52b60 error 4 in
> Bootup hangs at this point.
All combinations of those boot args give slightly different SPs but that's it.
e.g. selinux=0 init=/bin/bash:
init: segfault at d ip 004a266b sp bfacb960 error 4 in
Trying to get a working rescue CD so I can poke this machine a bit further.
Well, that eliminates upstart as the culprit.
Is that init or is it /init from the initrd (in which case, nash)?
Poked at the box. It's the return of the 'mkinitrd chooses mismatching ld.so and
Blargh. This is because ld-2.7.90.so sorts before ld-2.7.so in shell sort. But
we don't want to change the sort to be reversed as that would break things for
ld-2.7 -> ld-2.8. Not really sure if there's any better heuristic to use
Can't we just readlink ld-linux.so.2?
The name isn't consistent across arches... it's ld-linux-x86_64.so.2 on x86_64,
ld-linux-ia64.so.2 on itanium, ld.so.1 on ppc and ld64.so.1 on ppc64. I didn't
feel motivated enough to find an s390 or a sparc at that point. And keeping a
hardcoded list in mkinitrd per-arch feels like loss
You don't need a list, you can just ldd something...
(In reply to comment #9)
> You don't need a list, you can just ldd something...
Like say, the libc you're about to install.
*** Bug 440514 has been marked as a duplicate of this bug. ***
*** Bug 440583 has been marked as a duplicate of this bug. ***
Yes, anything that recreates the initrd (e.g. installing a new kernel)
post-upgrade will work fine.
But the problem happens when you run mkinitrd *during* the upgrade.
Can you test this with 6.0.42 ? (to be built very soon...)
Just did an upgrade from F8 and things are fine now