[Bug 1705345] Re: Installing new kernel hangs on plymouth --ping

Wed Jan 10 13:02:17 UTC 2018

I am seeing the same thing.  plymouthd doesn't hang around after every
boot, but it does so a reasonably large percentage of the time.
Additionally, when plymouthd continues to run after boot, machine
shutdown hangs for a long time before completing (presumably some kind
of systemd timeout).

Running strace against plymouthd when it's stuck causes it to exit
normally.

root at asp:~# ps axu |grep plymouth
root       320  0.0  0.2 164820 44100 ?        S    12:23   0:00 @sbin/plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid
root      1166  0.0  0.0  12936  1016 ?        Ss   12:23   0:00 /bin/plymouth --wait
root      1311  0.0  0.0  12936  1020 ?        S    12:23   0:00 /bin/plymouth quit
root      5398  0.0  0.0  12936  1024 pts/2    SN+  12:26   0:00 plymouth --ping
root      6023  0.0  0.0  12936  1020 ?        S    12:28   0:00 plymouth --ping
root      7537  0.0  0.0  14356  1060 pts/3    S+   12:58   0:00 grep --color=auto plymouth
root at asp:~# strace -p 320
strace: Process 320 attached
ioctl(10, PIO_CMAP, 0x559a2b77f178)     = 0
epoll_ctl(3, EPOLL_CTL_MOD, 10, {EPOLLERR|EPOLLHUP, {u32=730276688, u64=94120643601232}}) = 0
epoll_ctl(3, EPOLL_CTL_DEL, 10, NULL)   = 0
rt_sigaction(SIGWINCH, {sa_handler=SIG_DFL, sa_mask=[WINCH], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f0996fec140}, {sa_handler=0x7f09975b2820, sa_mask=[WINCH], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f0996fec140}, 8) = 0
ioctl(10, TIOCSLCKTRMIOS, {B0 -opost -isig -icanon -echo ...}) = 0
ioctl(10, TCGETS, {B38400 opost -isig -icanon -echo ...}) = 0
ioctl(10, TCGETS, {B38400 opost -isig -icanon -echo ...}) = 0
ioctl(10, SNDCTL_TMR_START or TCSETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(10, TCGETS, {B38400 opost isig icanon echo ...}) = 0
close(10)                               = 0
close(7)                                = 0
unlink("/run/plymouth/pid")             = 0
sendto(8, "\6", 1, MSG_NOSIGNAL, NULL, 0) = 1
epoll_ctl(3, EPOLL_CTL_DEL, 4, NULL)    = 0
epoll_ctl(3, EPOLL_CTL_DEL, 6, NULL)    = 0
epoll_ctl(3, EPOLL_CTL_DEL, 7, NULL)    = -1 EBADF (Bad file descriptor)
epoll_ctl(3, EPOLL_CTL_DEL, 11, NULL)   = 0
epoll_ctl(3, EPOLL_CTL_DEL, 12, NULL)   = 0
epoll_ctl(3, EPOLL_CTL_DEL, 8, NULL)    = 0
close(11)                               = 0
close(12)                               = 0
close(8)                                = 0
close(2)                                = 0
exit_group(0)                           = ?
+++ exited with 0 +++
root at asp:~# ps axu |grep plymouth
root      5405  0.0  0.0  14356  1080 pts/3    S+   12:59   0:00 grep --color=auto plymouth

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1705345

Title:
  Installing new kernel hangs on plymouth --ping

Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  I tried to upgrade linux kernel, from 4.10.0-26 to 4.10.0-28, but the
  installation hung on the following output lines:

  sudo apt-get install unrar linux-generic linux-headers-generic linux-image-generic linux-signed-generic linux-signed-image-generic
  Configurazione di linux-image-4.10.0-28-generic (4.10.0-28.32)...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic

  Then I looked at the running processes, and noticed this one was
  blocking post-installation:

  plymouth --ping

  I could not but manually kill plymouth, then the script resumed just
  to freeze again a few line later and so on, but is that safe for the
  installation?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: plymouth 0.9.2-3ubuntu15
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 19 22:32:14 2017
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
  InstallationDate: Installed on 2017-05-22 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision M4800
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0T3YTY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1705345/+subscriptions