touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #57036
[Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails
This is an automated reproducer in the form of an autopkgtest. You can
call it like this:
adt-run --built-tree ./systemd-bootsmoke --- qemu /srv/vm/adt-
pid1.img
This reboots the VM up to 20 times, and check for stuck jobs or non-
running polkit on each iteration. You can also test with modified
binaries by copying them into the testbed's /tmp/systemd-replace, like
this:
adt-run --built-tree ./systemd-bootsmoke --copy /tmp/systemd-
journald:/tmp/systemd-replace/systemd-journald --- ....
With e. g. systemd-journald from 218 the test passes. Note that there is
sometimes some testbed timeout and other testbed setup failures, due to
various race conditions.
I added a few robustifications to autopkgtest 3.9.7 (just uploaded to
Debian sid, will sync into vivid this evening). You can of course also
just checkout latest autopkgtest git and call /checkout/dir/run-from-
checkout instead of "adt-run".
In principle this works with a standard adt-buildvm-ubuntu-cloud minimal
image (the test installs lightdm, network-manager, etc.), but I still
find it rather hard to reproduce there. I instead built a custom "adt-
pid1.img" which is a standard vivid desktop install with the following
modifications:
- Prepare the VM for autopkgtest (enable serial console and provide
the root shell on ttyS1 mostly) by running /usr/share/autopkgtest/adt-
setup-vm in it as root once (you *need* autopkgtest 3.9.7 for this, or
grab it from git).
- Install systemd-sysv
With such an image I usually get the hang after 2 or 3 reboots already,
so that the 20 iterations that the test does should be quite sufficient.
I'll add this test to the systemd package soon, but for now this is
standalone for easier hacking.
** Attachment added: "boot smoke autopkgtest"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/+attachment/4324637/+files/systemd-bootsmoke.tar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1 regression: boot hangs, logind fails
Status in systemd package in Ubuntu:
In Progress
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@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@rfkill1.service stop waiting
1631 failsafe-x.service stop waiting
1638 systemd-backlight@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@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@rfkill0.service stop waiting
1613 plymouth-quit.service start waiting
1639 system-ifup.slice stop waiting
1642 ifup@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/ubuntu/+source/systemd/+bug/1423811/+subscriptions
References