Bug 440091
| Summary: | init segfaults at boot on system upgraded from F8 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Will Woods <wwoods> |
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | cookiecaper, dcantrell, katzj, lsof, notting, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-04-17 06:29:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 235706 | ||
|
Description
Will Woods
2008-04-01 18:16:01 UTC
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[1]: segfault at d ip 004a266b sp bfa52b60 error 4 in > libc-2.7.90.so[48c000+16d000] > > 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[1]: segfault at d ip 004a266b sp bfacb960 error 4 in libc-2.7.90.so[48c000+16d000] 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 libc' problem. 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 off-hand :-/ 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. *** kernel-2.6.25-0.195.rc8.git1.fc9.i686 wfm 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 |