kernel-packages team mailing list archive

[salvia <marco38@xxxxxxxxxxxxx>]

/var/log/dmesg's last date of modification was 04/26/2015, which I
simply don't understand, but inside the file:

[    6.118458] init: plymouth-upstart-bridge respawning too fast, stopped
[   31.833709] Adding 4189180k swap on /dev/sda5.  Priority:-1 extents:1 across:4189180k FS

where are the missing 26 seconds, where the ordering cycle would appear?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1592933

Title:
  there are several errors on booting my laptop (xubuntu 16.04 64 bits),
  ordering cycle broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Best I could think of is recording a video, so you see what I endure
  every time I power on the laptop:

  https://vid.me/9eRl

  it's comments are self explanatory:

  Booting on M7X-SUN

  00:39: those are several inode errors, those appear because I had to
  reboot the laptop several times (because the first or second time on
  powering the laptop I just got a blank screen).

  00:48: that huge list of things being loaded is nowehere in
  /var/log/syslog, dmesg or kern.log to be seen. Where do I find that
  information that tells me what is going in in plain text format? Green
  is OK, red is FAILED

  Right after the several inode errors some information about the
  ordering cycle appears: They read as follows (see #8 for more
  information):

  /dev/sda1: clean, 116918/19275776 files, 66284199/77094912 blocks
  [10.368134] systemd[1]: paths.target: job paths.target/start deleted to break ordering cycle starting with basic.target/start
  [10.368234] systemd[1]: systemd-ask-password-plymouth.path: Job systemd ask-password-plymouth.path/deleted to break ordering cycle starting with basic.target/start
  [10.368324] systemd[1]: plymouth-start.service: Job plymouth-start.service/start deleted to break ordering cycle starting with plymouth-quit-wait.service/start

  01:21: from this moment on, blank screen with just a cursor. It stays
  like that usually for 30 to 40 seconds with no mention of tty1 (see
  next)

  01:38: thats tty1 asking me an username and if I enter it, a password,
  I usually don't write anything and let the laptop go on to login
  screen.

  02:01: blank screen (this is new, usually the login screen should
  appear now)

  03:00: not recorded, but log in screen appeared.

  I dont know if this is related to my other bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589109 , because
  on shutting down I also don't see what is going on...

  somebody suggested to execute 'systemd-analyze plot > boot.svg' which
  does not show that huge list I mention on 00:48, but I append it here,
  as it may be useful for you...

  How Do I solve all those problems and get my fully 4 GiB of ram to work instead of the 2 just right now? Between 2 and 3 minutes just to boot a laptop is too much time.
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2012-04-12 (1525 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.7.0-040700rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video
  _MarkForUpload: True

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