Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1676357
Summary: | dracut-install[7836]: segfault at 0 ip 0000562144297444 sp 00007ffdb5ad3588 error 4 in dracut-install | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||||
Component: | dracut | Assignee: | dracut-maint-list | ||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 29 | CC: | antonette.caldwell, awilliam, dracut-maint-list, jonathan, nige, philip.wyett, redhat-bugzilla, russ+bugzilla-redhat, satellitgo, th.neuber, tom, zbyszek | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | dracut-049-26.git20181204.fc29 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2019-03-29 02:59:03 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Chris Murphy
2019-02-12 03:55:15 UTC
Created attachment 1533887 [details]
journal
I saw what's probably the same crash today. I noticed I have kernel-core-5.0.0-0.rc6.git0.1.fc30.x86_64 installed but my system booted to an older kernel, and looking in /boot/loader/entries , there was no entry for the rc6 kernel. So I did 'dnf reinstall kernel-core-5.0.0-0.rc6.git0.1.fc30.x86_64' to see what would happen, and saw a scriptlet fail: Running scriptlet: kernel-core-5.0.0-0.rc6.git0.1.fc30.x86_64 2/2 /usr/lib/dracut/dracut-init.sh: line 969: 12931 Segmentation fault (core dumped) $DRACUT_INSTALL ${initdir:+-D "$initdir"} ${loginstall:+-L "$loginstall"} ${hostonly:+-H} ${omit_drivers:+-N "$omit_drivers"} ${srcmods:+--kerneldir "$srcmods"} ${_optional:+-o} ${_silent:+--silent} -m "$@" dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.WlwtEn/initramfs -H --kerneldir /lib/modules/5.0.0-0.rc6.git0.1.fc30.x86_64/ -o -m =drivers/net/phy =drivers/net/team =drivers/net/ethernet ecb arc4 bridge stp llc ipv6 bonding 8021q ipvlan macvlan af_packet virtio_net xennet Looking at abrt I saw a core dump for dracut-install. I couldn't automatically report it with abrt-gui or abrt-cli because there seem to be issues with the FAF server right now (I have reported these to the maintainer by email), but I could generate the backtrace with gdb, and it's all in dracut-install, like Chris's partial trace. I will attach the full gdb-generated backtrace. This seems pretty significant, if it's preventing newly-installed kernels from booting. Created attachment 1534939 [details]
full backtrace from the crash
If I run 'dracut -f' I get the same failure for the currently-booted kernel, though it seems the same dracut-install must have worked at the time that kernel was installed. So I think this is not a case of it only failing with kernel rc6, but instead some other change has caused dracut to fail in this way on all kernels when previously it didn't... Fix tested, works, thanks. I am sending a Rawhide package build with it backported (dracut-049-26.git20181204). *** Bug 1677415 has been marked as a duplicate of this bug. *** *** Bug 1677455 has been marked as a duplicate of this bug. *** *** Bug 1677450 has been marked as a duplicate of this bug. *** Looks like I am seeing this (or at least a crash in dracut-install) in F29 with the newly arrived 5.0.3 kernel... Trace seems to be the same: PID: 5356 (dracut-install) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Mon 2019-03-25 17:55:36 GMT (30s ago) Command Line: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.Nn3322/initramfs -H --kerneldir /lib/modules/5.0.3-200.fc29.x86_64/ -o -m =drivers/net/phy =drive> Executable: /usr/lib/dracut/dracut-install Control Group: /user.slice/user-1000.slice/user/gnome-terminal-server.service Unit: user User Unit: gnome-terminal-server.service Slice: user-1000.slice Owner UID: 1000 (tom) Boot ID: dc9bc9bf94724a84bd437cf5a43508b0 Machine ID: 915a7d3d1c624d789e906030a1dafb2f Hostname: bericote.compton.nu Storage: /var/lib/systemd/coredump/core.dracut-install.0.dc9bc9bf94724a84bd437cf5a43508b0.5356.1553536536000000.lz4 (inaccessible) Message: Process 5356 (dracut-install) of user 0 dumped core. Stack trace of thread 5356: #0 0x000055d2edaf9444 string_hash_func (dracut-install) #1 0x000055d2edaf987a hashmap_get (dracut-install) #2 0x000055d2edaf5829 check_hashmap (dracut-install) #3 0x000055d2edaf77cf install_dependent_modules (dracut-install) #4 0x000055d2edaf7e6b install_module (dracut-install) #5 0x000055d2edaf8874 install_modules (dracut-install) #6 0x000055d2edaf479d main (dracut-install) #7 0x00007fb5c2eb6413 __libc_start_main (libc.so.6) #8 0x000055d2edaf4a7e _start (dracut-install) For some reason it only seemed to happen on two of the machines I just updated, and not on the other two. I can confirm that rebuilding the current F30 package (with the extra patch) for F29 fixes this. *** Bug 1692189 has been marked as a duplicate of this bug. *** Bug 1692189 is a dup, but I did process with `coredumpctl gdb` and attached the output. It definitely happens on F29 and F30, and seems to be kernel 5.0 specific, it's not happening with 4.20 kernels; also is reproducible by running dracut standalone. I'll send the fix to F29 too, then. And probably F28 as well as presumably kernel 5 is going to wind up there eventually. dracut-049-26.git20181204.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-38c666fc03 In fact having looked at it, I think the dracut in f28 shouldn't be affected by this, for the record. I'm also seeing this in F29 on install of kernel-core-5.0.3-200.fc29.x86_64. Trace the same as in comment 11. After installing the packages from bodhi, I could "dnf reinstall kernel-core-5.0.3-200.fc29.x86_64" with no error. Thanks! dracut-049-26.git20181204.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-38c666fc03 confirming dracut-049-26.git20181204.fc29 is a working fix although an alternant method was used. Booted to previous unaffected kernel (kernel-4.20.16-200.fc29) uninstalled kernel-5.0.3-200.fc29 updated to dracut-049-26.git20181204.fc29 installed kernel-5.0.4-200.fc29 from koji Result : No error messages upon installation. dracut-049-26.git20181204.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |