← Back to team overview

kernel-packages team mailing list archive

[Bug 1592933] Missing required logs.


This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1592933

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  there are several errors on booting my laptop (xubuntu 16.04 64 bits)

Status in linux package in Ubuntu:

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


  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

  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

  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

  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.

To manage notifications about this bug go to: