FS#44016 - [systemd] journald regression in v219 makes boot hang
Attached to Project:
Arch Linux
Opened by Christian Hesse (eworm) - Monday, 02 March 2015, 14:46 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 30 July 2015, 05:50 GMT
Opened by Christian Hesse (eworm) - Monday, 02 March 2015, 14:46 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 30 July 2015, 05:50 GMT
|
Details
Description:
A journald regression in v219 makes the boot hang. This has been reported for Debian [0] and Ubuntu [1] and a discussion has been started on systemd mailing list [2]. I've seen this with Arch package system 219-2 as well. Looks like the be fix for now is to revert commit add4bf64 ("journald: allow restarting journald without losing stream connections") [3]. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970 [1] https://bugs.launchpad.net/bugs/1423811 [2] http://comments.gmane.org/gmane.comp.sysutils.systemd.devel/28525 [3] http://cgit.freedesktop.org/systemd/systemd/commit/?id=13790add4bf64 Additional info: systemd 219-2 libsystemd 219-2 Steps to reproduce: Update to system 219-2, then reboot again and again until boot hangs. |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 30 July 2015, 05:50 GMT
Reason for closing: Fixed
Additional comments about closing: systemd-220-1
Thursday, 30 July 2015, 05:50 GMT
Reason for closing: Fixed
Additional comments about closing: systemd-220-1
Just downgraded to systemd-219-2 and could boot fine again.
edit: disregard this seems to be something unrelated
http://lists.freedesktop.org/archives/systemd-devel/2015-April/031348.html
http://cgit.freedesktop.org/systemd/systemd/commit/?id=64144440
I did not verify myself, though.
http://cgit.freedesktop.org/systemd/systemd/commit/?id=d4a144fa
Just compiling...
The more testers we have the better test results we have.
Hopefully it'll be backported soon?
Feel free to grab systemd.diff from above and build a fixed package.
Going to the point..: yesterday, after some hours of coding - by luck I save every microsecond - the X went down the hill towards the cliff. I tried to start the X by typing "startx" all the time, even after some reboots, but nothing: colord.service at fault (I guess..?) because of systemd (another guess).
After looking, I noticed a warning at boot time. "colord.service" couldn't start. And a little searching (googling) pinpointed that, time to time, systemd has this strange behaviour of not starting things (ie. bug).
So here I am to report that some update in these last days (even, maybe, prior to this month that just tarted) broke things. But I can't confirm what the problem is - I think don't have the knowledge.
There are some logs attached (I don't know if they suffice) but I just wanted to say that I am using the testing repository to test if with systemd 220.3 things works (the problematic one is 219). And till know, they do work. I hope 220 is a real fix and that this update comes as soon as possible.
Files:
:: journalctl -p 0..3 -xn > 1.txt
:: systemctl status colord.service > 2.txt
:: journalctl -xe > 3.txt
EDIT - 2015-06-16: system crashed, again. This new version doesn't work OK. I lasted 11 days. I got the same files and made a diff but relevant info hasn't changed. So, 220 IS NOT a fix.
2.txt (0.9 KiB)
3.txt (120.8 KiB)