This bug has been created based on an anonymous crash report requested by the package maintainer. Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/a1f56ca4a7f72d360ed2945aec8456b1de1718fe/
For explanation, see https://bugzilla.redhat.com/show_bug.cgi?id=1300212. I find it very unlikely, though, that the system is so starved that it doesn't respond for 3 minutes at all... I suspect a subtle bug that *makes* journald stop responding. It's near impossible to debug, though, without a system where this would happen with at least a 50% probability.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.