Bug 18467 - systemd does not the finish boot process. plymouth-quit-wait.service does not finish waiting.
Summary: systemd does not the finish boot process. plymouth-quit-wait.service does no...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-16 11:10 CEST by PC LX
Modified: 2016-08-03 20:27 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
full output of systemctl (25.27 KB, text/plain)
2016-05-16 11:15 CEST, PC LX
Details

Description PC LX 2016-05-16 11:10:47 CEST
Description of problem:

systemd does not finish the boot process. It seems plymouth-quit-wait.service is still waiting many minutes after boot started. If I manually stop plymouth-quit-wait.service, systemd finishes booting.


# systemd-analyze
Bootup is not yet finished. Please try again later.
# systemctl status
station4
    State: starting
     Jobs: 8 queued
   Failed: 0 units
    Since: Seg 2016-05-16 09:26:49 WEST; 25min ago
...

# systemctl | grep wait
proc-sys-fs-binfmt_misc.automount        loaded active     waiting         Arbitrary Executable File Formats File System Automount Point
systemd-ask-password-plymouth.path       loaded active     waiting         Forward Password Requests to Plymouth Directory Watch
systemd-ask-password-wall.path           loaded active     waiting         Forward Password Requests to Wall Directory Watch
fedora-wait-storage.service              loaded active     exited          Wait for storage scan
plymouth-quit-wait.service               loaded activating start     start Hold until boot process finishes up
systemd-tmpfiles-clean.timer             loaded active     waiting         Daily Cleanup of Temporary Directories
# systemctl stop plymouth-quit-wait.service
# systemctl status
station4
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Seg 2016-05-16 09:26:49 WEST; 39min ago
...
# systemd-analyze 
Startup finished in 16.285s (kernel) + 37min 23.196s (userspace) = 37min 39.482s
# systemd-analyze blame
   36min 47.784s plymouth-quit-wait.service
          9.348s dev-mapper-Mageia5\x2dbtrfs.device
          8.991s NetworkManager-wait-online.service
          7.860s systemd-udev-settle.service
          6.930s network-up.service
          5.912s shorewall.service
          5.136s mandriva-everytime.service
          4.297s systemd-journal-flush.service
          4.012s NetworkManager.service
...



Version-Release number of selected component (if applicable):

# rpm -q systemd
systemd-229-3.mga6
# uname -a
Linux marte 4.6.0-desktop-0.rc6.1.mga6 #1 SMP Tue May 3 23:27:25 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux



How reproducible:

Always.



Steps to Reproduce:
1. Boot Mageia (6) cauldron system.
2. Wait long enough for system to boot.
3. Run "systemd-analyze" or "systemctl status" to see boot status.
PC LX 2016-05-16 11:13:17 CEST

Summary: systemd does not the finish boot process. => systemd does not the finish boot process. plymouth-quit-wait.service does not finish waiting.

Comment 1 PC LX 2016-05-16 11:15:00 CEST
Created attachment 7799 [details]
full output of systemctl
Rémi Verschelde 2016-05-17 11:38:21 CEST

CC: (none) => pkg-bugs
Assignee: bugsquad => mageia

Comment 2 PC LX 2016-06-18 11:32:57 CEST
Noticed something that may be of use to track down this bug.

Today, when I booted the Mageia Cauldron for another round of updates and testing, due to not having the nvidia binary driver available for the most recent kernel, Xorg started using the nouveau driver and "systemctl status" showed "State: running / Jobs: 0 queued / Failed: 0 units" without me having to stop the plymouth-quit-wait.service manually.

After I installed dkms-nvidia340, reconfigured the system to use it and rebooted, the system again showed this bug.

This is a test system (not production) so I can do testing to help debug this issue.


# rpm -qa | grep -E 'dkms|nvidia|4\.6\.2' | sort
cpupower-4.6.2-1.mga6
dkms-2.0.19-37.mga6
dkms-minimal-2.0.19-37.mga6
dkms-nvidia340-340.96-37.mga6.nonfree
kernel-desktop-4.6.2-1.mga6-1-1.mga6
kernel-desktop-devel-4.6.2-1.mga6-1-1.mga6
kernel-desktop-devel-latest-4.6.2-1.mga6
kernel-desktop-latest-4.6.2-1.mga6
kernel-userspace-headers-4.6.2-1.mga6
vboxadditions-kernel-4.6.2-desktop-1.mga6-5.0.22-1.mga6
x11-driver-video-nvidia340-340.96-37.mga6.nonfree

# uname -a
Linux marte 4.6.2-desktop-1.mga6 #1 SMP Fri Jun 10 08:32:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# cat /proc/cmdline 
BOOT_IMAGE=/root_cauldron/boot/vmlinuz-desktop root=/dev/mapper/Mageia5-btrfs ro rootflags=subvol=root_cauldron nokmsboot splash
Comment 3 PC LX 2016-07-12 13:14:05 CEST
This bug is still valid, with all packages up-to-date.

This bug occurs when using the nvidia driver but does NOT occur when using the nouveau driver.

# rpm -qa | grep -E 'dkms|nvidia|4\.7\.0' | sort
cpupower-4.7.0-0.rc7.1.mga6
dkms-2.0.19-37.mga6
dkms-minimal-2.0.19-37.mga6
dkms-nvidia340-340.96-37.mga6.nonfree
javapackages-tools-4.7.0-1.mga6
kernel-desktop-4.7.0-0.rc7.1.mga6-1-1.mga6
kernel-desktop-devel-4.7.0-0.rc7.1.mga6-1-1.mga6
kernel-desktop-devel-latest-4.7.0-0.rc7.1.mga6
kernel-desktop-latest-4.7.0-0.rc7.1.mga6
kernel-userspace-headers-4.7.0-0.rc7.1.mga6
python3-javapackages-4.7.0-1.mga6
vboxadditions-kernel-4.7.0-desktop-0.rc7.1.mga6-5.0.24-6.mga6
x11-driver-video-nvidia340-340.96-37.mga6.nonfree
Comment 4 David Walser 2016-07-22 15:38:12 CEST
Video driver problem, not a systemd problem.

CC: (none) => anssi.hannula
Assignee: mageia => tmb

Comment 5 PC LX 2016-08-03 20:27:56 CEST
Just updated the system and am rechecking the bugs. Well, where ever the problem was, it seems this bug is resolved. I'm marking this bug a resolved/fixed.

$ systemd-analyze
Startup finished in 19.027s (kernel) + 49.843s (userspace) = 1min 8.870s
$ systemctl status | head -n 5
station4
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Qua 2016-08-03 19:07:24 WEST; 10min ago
$ uname -a
Linux marte 4.7.0-desktop-2.mga6 #1 SMP Sat Jul 30 21:54:30 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -qa | grep -Ei 'systemd|nvidia|dkms' | sort
dkms-2.0.19-37.mga6
dkms-minimal-2.0.19-37.mga6
dkms-nvidia340-340.96-38.mga6.nonfree
dkms-virtualbox-5.1.2-1.mga6
lib64systemd0-230-3.mga6
libsystemd0-230-3.mga6
systemd-230-3.mga6
systemd-devel-230-3.mga6
systemd-units-230-3.mga6
x11-driver-video-nvidia340-340.96-38.mga6.nonfree

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.