[Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails
Bug Watch Updater
1423811 at bugs.launchpad.net
Fri Oct 27 07:02:12 UTC 2017
Launchpad has imported 18 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1201964.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2015-03-14T03:14:36+00:00 Adam wrote:
Created attachment 1001544
failure log
Since around March 6th, my Fedora 22 desktop system has frequently
failed to boot properly.
Unfortunately the last time I booted the system before that was February
23rd, so there's quite a big list of possible changes in there.
I have tried downgrading from systemd-219-8.fc22 to systemd-219-5.fc22
and from kernel-4.0.0-0.rc3.git1.2 to 3.20.0-0.rc0.git10.1.fc22; neither
seems to change anything, the bug still happens.
When the boot fails, various services don't attempt to start for some
time, and when they try and start, many fail. The system never manages
to start any consoles or gdm.
>From the debug console (tty9), running 'systemctl' appears to do nothing
for a long time, then shows an error like "Failed to register match for
disconnected message".
I will attach logs of both failed and successful boots with
systemd.log_level = debug.
The boot fails on average ~3 in 4 times.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/13
------------------------------------------------------------------------
On 2015-03-14T03:15:00+00:00 Adam wrote:
Created attachment 1001545
success log
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/14
------------------------------------------------------------------------
On 2015-03-15T03:13:58+00:00 Zbigniew wrote:
In the upcoming systemd update there's a fix for socket path handling.
I'm not sure if this could be the same issue, but it'd be good if you
could test if it helps.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/15
------------------------------------------------------------------------
On 2015-03-15T04:00:46+00:00 Fedora wrote:
systemd-219-9.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/systemd-219-9.fc22
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/16
------------------------------------------------------------------------
On 2015-03-15T08:35:54+00:00 Adam wrote:
Nope, sorry, doesn't help :/ saw the bug on 2 of 3 test boots with
219-9.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/17
------------------------------------------------------------------------
On 2015-03-16T01:41:00+00:00 Fedora wrote:
Package systemd-219-9.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-219-9.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3949/systemd-219-9.fc22
then log in and leave karma (feedback).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/18
------------------------------------------------------------------------
On 2015-03-18T12:52:31+00:00 Lukáš wrote:
This is definitely a bug in 219. I have the same issue with my rhel build.
Unfortunately on my machine it occurs quite rarely so its hard to debug.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/19
------------------------------------------------------------------------
On 2015-03-20T18:00:02+00:00 Marek wrote:
I see similar problem, my case is described in bug 1204023.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/20
------------------------------------------------------------------------
On 2015-03-25T19:33:02+00:00 Adam wrote:
Lukas: it occurs frequently for me, I'm happy to do any debugging anyone
requests, but I'd really like to see this fixed. It's kind of
unfortunate that my system neither starts up nor shuts down properly
most of the time! (I suffer from one or other of the bugs in the
disaster zone that is
https://bugzilla.redhat.com/show_bug.cgi?id=1088619 ).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/21
------------------------------------------------------------------------
On 2015-03-26T17:07:36+00:00 Michal wrote:
Just guessing... This could be the same problem:
http://lists.freedesktop.org/archives/systemd-devel/2015-February/028640.html
Martin Pitt is reverting commit 13790add4bf648fed816361794d8277a75253410 in Ubuntu as a workaround.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/22
------------------------------------------------------------------------
On 2015-03-26T18:03:17+00:00 Adam wrote:
I just tested with systemd-219-11.fc22 and 8 boots in a row didn't hit
the bug once. It may be a bit early to declare 'mission accomplished',
but it looks good.
zbyszek, any chance you could submit an update for 219-11?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/23
------------------------------------------------------------------------
On 2015-03-27T08:05:17+00:00 Martin wrote:
I just applied all v219-stable patches on top of our package, and re-
applied 13790a again (i. e. dropped the revert). I now get the boot
failures again, so I'm afraid the patches in v219-stable aren't
sufficient.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/26
------------------------------------------------------------------------
On 2015-03-27T16:02:22+00:00 Adam wrote:
Hum, interesting. So either I got really lucky yesterday, or we're
actually seeing two different bugs, or (I suppose) latest stable changes
things enough to hide whatever's triggering the bug when I boot my
system, but not to fix your reproducer...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/27
------------------------------------------------------------------------
On 2015-04-29T09:52:34+00:00 Martin wrote:
Good news! It seems this got finally fixed (involuntarily) in upstream
git master, and the patch cleanly backports to 219. See
http://lists.freedesktop.org/archives/systemd-
devel/2015-April/031348.html
for the details.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/30
------------------------------------------------------------------------
On 2015-05-01T00:02:11+00:00 Adam wrote:
+1 resurrection of kittens
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/31
------------------------------------------------------------------------
On 2015-06-26T16:27:04+00:00 Ferry wrote:
Guys,
Is this already fixed in F22?
I came here via a search on 'fedora 22 avahi-daemon fails'.
avahi-daemon fails to start on one of my servers, but not on others
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/32
------------------------------------------------------------------------
On 2015-06-26T16:30:23+00:00 Ferry wrote:
(In reply to Ferry Huberts from comment #15)
> Guys,
> Is this already fixed in F22?
>
> I came here via a search on 'fedora 22 avahi-daemon fails'.
> avahi-daemon fails to start on one of my servers, but not on others
Nevermind, this was an install failure for the avahi package: the avahi
user was not created.
I've seen this with the tcpdump packages as well.
I think there might be some rpm/dnf issue there.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/33
------------------------------------------------------------------------
On 2016-07-19T19:05:38+00:00 Fedora wrote:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/36
** Changed in: systemd (Fedora)
Status: Unknown => Won't Fix
** Changed in: systemd (Fedora)
Importance: Unknown => High
** Bug watch added: Red Hat Bugzilla #1088619
https://bugzilla.redhat.com/show_bug.cgi?id=1088619
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1 regression: boot hangs, logind fails
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd package in Debian:
Fix Released
Status in systemd package in Fedora:
Won't Fix
Bug description:
Since yesterday, systemd does not boot properly any more. It takes
very long, ends up in an X failsafe session, and eventually you just
get a getty on VT1.
Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the
boot again.
This happens both with the standard "quiet splash $vt_handoff" as well
as without these tree options, i. e. text mode boot.
$ sudo systemctl list-jobs
JOB UNIT TYPE STATE
1634 sound.target stop waiting
1176 NetworkManager.service start running
1598 cgproxy.service start waiting
1632 failsafe-graphical.target stop waiting
1563 alsa-restore.service start waiting
1594 plymouth-quit-wait.service start waiting
1588 getty-static.service start waiting
1562 alsa-state.service start waiting
121 systemd-update-utmp-runlevel.service start waiting
1640 ifup at wlan0.service stop waiting
1544 systemd-ask-password-plymouth.path start waiting
1507 friendly-recovery.service start waiting
1607 anacron.service start waiting
1489 systemd-binfmt.service start waiting
1637 system-systemd\x2drfkill.slice stop waiting
1636 systemd-rfkill at rfkill1.service stop waiting
1631 failsafe-x.service stop waiting
1638 systemd-backlight at backlight:intel_backlight.service stop waiting
1610 pppd-dns.service start waiting
1483 systemd-machine-id-commit.service start waiting
1635 system-systemd\x2dbacklight.slice stop waiting
1557 systemd-hwdb-update.service start waiting
1630 systemd-backlight at backlight:acpi_video0.service stop waiting
1500 sys-kernel-config.mount start waiting
92 multi-user.target start waiting
1509 debian-fixup.service start waiting
1641 systemd-rfkill at rfkill0.service stop waiting
1613 plymouth-quit.service start waiting
1639 system-ifup.slice stop waiting
1642 ifup at lxcbr0.service stop waiting
1633 acpid.service stop waiting
1643 systemd-logind.service restart waiting
1543 plymouth-start.service start waiting
1499 plymouth-read-write.service start waiting
Attaching debug journal.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-1ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 20 07:39:03 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-20 (91 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
MachineType: LENOVO 2324CTO
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet splash vt.handoff=7 init=/sbin/upstart
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324CTO
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1423811/+subscriptions
More information about the foundations-bugs
mailing list