Description of problem: When starting up an Fedora Xen PV guest, the system freezes during bootup. Version-Release number of selected component (if applicable): systemd-208-19.fc20.x86_64 systemd-libs-208-19.fc20.x86_64 How reproducible: 8/10 attempts Steps to Reproduce: 1. try to boot a fedora xen pv guest Actual results: last few lines of the bootup with systemd debug enabled: (typed of the screen) [...] systemd-journald.socket changes dead -> running system.slice changed dead -> active paths.target changed dead -> active slices.target changed dead -> active fedora-loadmodules.service changed dead -> exited remote-fs.target changed dead -> active systemd-ask-password-wall.path changed dead -> waiting local-fs-pre.target changed dead -> active systemd-fsck-root.service changed dead -> exited proc-xen.mount changed dead -> mounted - -.mount changed dead -> mounted tmp.mount changed dead -> mounted fedora-readonly.service changed dead -> start dev-hvc0.device changed dead -> plugged Job dev-hvc0.device/start finished, result=done Assertion 'epoll_ctl(j->manager->epoll_fd, EPOLL_CTL_DEL, j->timer_watch.fd, NULL) >= 0' failed at ../src/core/job.c:112, function job_free(). Aborting. Caught <ABRT>, dumped core as pid 515. Freezing execution. Expected results: Bootup without issues. Additional info: This bug has been observed in a third party product (Qubes OS [1]) that makes use of fedora 20 guest VMs and uses a non-fedora kernel based on linux 3.12.23 [2]. [1] http://qubes-os.org/trac [2] http://git.qubes-os.org/?p=joanna/linux-kernel.git
This bug is also reproducible with a vanilla Linux kernel 3.15.3 (kernel.org).
I was able to track the trigger of this bug down. A qubes service did execute 'systemctl daemon-reexec' during startup, this triggers the bug. Is this supposed to be causing problems?
(In reply to Joonas from comment #2) > A qubes service did execute 'systemctl daemon-reexec' during startup, this > triggers the bug. Is this supposed to be causing problems? It shouldn't crash. If you can reproduce this reliably (or if you still have the core file), you could check what the values of j->manager->epoll_fd, j->timer_watch.fd are. This code has been rewritten post systemd-208, so unfortunately a possible fix would only be applicable to that version.
Created attachment 919356 [details] core file I hope this is the correct file (it was located in /).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.