Description of problem: Sometimes especially when using dnf to install/remove/upgrade packages, I get this message (on tty only): [123.456789]systemd-journald[456]: Recieved request to flush runtime journal from PID 1 where 123.456789 is the relative time since boot (as in dmesg) and 456 is the pid of systemd-journald. After that the system freezes forever. Version-Release number of selected component (if applicable): systemd-208-9.fc20 (and possibly previous versions) How reproducible: difficult. Seems to happen especially when using dnf to install/remove/upgrade packages. It does not seem to happen when tty is active. I.e. when I'm switching to tty1/Gnome while installing this does never happen. On one machine I've seen this bug for ~2 month on F20 beta and F20 with "updates" and "updates-testing" repositories enabled. On another machine ("updates" and "updates-testing" since F20 beta enabled) I've seen this the first time today. Additional info: journald does not print anything about this error to journal. Someone else seems to have the same problem: https://lists.fedoraproject.org/pipermail/test/2013-December/119352.html http://forums.opensuse.org/showthread.php/493151-Boot-failing-on-quot-systemd-journald-XXX-Received-request-to-flush-runtime-journal-from-PID-1-quot as in his case, space is not short on my systems on /var (>10GB available) Tips on http://freedesktop.org/wiki/Software/systemd/Debugging/ don't help me since my case is not "intended".
I am seeing a similar issue on a Thinkpad T420. It's a fresh F20 install with all current updates applied. I also have the T420 firmware updated to the latest and only integrated graphics enabled in the BIOS config. It seems that the system doesn't completely die but the tty does. I.e., if I'm doing a yum update and see the "Received request . . ." message, the tty freezes and I can't switch to another but the yum update continues on to completion as there's disk activity for some time and, when I reboot, the update finished cleanly.
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.