219-1ubuntu1 regression: boot hangs, logind fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Undecided
|
Martin Pitt | ||
systemd (Debian) |
Fix Released
|
Unknown
|
|||
systemd (Fedora) |
Won't Fix
|
High
|
|||
systemd (Ubuntu) |
Fix Released
|
Critical
|
Martin Pitt |
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:/
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.
1598 cgproxy.service start waiting
1632 failsafe-
1563 alsa-restore.
1594 plymouth-
1588 getty-static.
1562 alsa-state.service start waiting
121 systemd-
1640 <email address hidden> stop waiting
1544 systemd-
1507 friendly-
1607 anacron.service start waiting
1489 systemd-
1637 system-
1636 <email address hidden> stop waiting
1631 failsafe-x.service stop waiting
1638 systemd-
1610 pppd-dns.service start waiting
1483 systemd-
1635 system-
1557 systemd-
1630 systemd-
1500 sys-kernel-
92 multi-user.target start waiting
1509 debian-
1641 <email address hidden> stop waiting
1613 plymouth-
1639 system-ifup.slice stop waiting
1642 <email address hidden> stop waiting
1633 acpid.service stop waiting
1643 systemd-
1543 plymouth-
1499 plymouth-
Attaching debug journal.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-1ubuntu1
ProcVersionSign
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=
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.
dmi.board.name: 2324CTO
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2324CTO
dmi.product.
dmi.sys.vendor: LENOVO
description: | updated |
description: | updated |
Changed in systemd (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in systemd (Debian): | |
status: | Unknown → Confirmed |
Changed in systemd (Debian): | |
status: | Confirmed → Fix Released |
Changed in systemd: | |
assignee: | nobody → Martin Pitt (pitti) |
Changed in systemd (Fedora): | |
importance: | Unknown → High |
status: | Unknown → Won't Fix |
Notekeeping:
- installing self-built .debs: boot ok
- reinstalling ubuntu debs: boot fail
- Removing persistant journal (sudo rm -r /var/log/journal) with the ubuntu binaries: boot ok
- rebooting a few times with re-enabling persistant journal: boot ok
- QEMU with enabling persistant journal and booting a few times: bootok
- Didier has no persistant journal and got the issue once, so this only appears to change timing, not a fundamental thing
So now I need to figure out how to make boot fail again.