← Back to team overview

kernel-packages team mailing list archive

[Bug 1259861] Re: 5-10 second delay in kernel boot


@penlalvch: I was asked in #ubuntu-kernel to file this bug report so
that they can assign someone to work on it.

If you keep adding "it needs this and that" tags, then this bug report
appears to be incomplete, and no developer will start working on it
until I satisfy/remove the tags.

But as I keep saying,
1) needs-apport-collect => why? it happens anywhere, so I could run apport-collect in a KVM VM, but why would anyone want that? It's just useless information.
2) needs-upstream-testing => as I said, the problem doesn't happen in any Debian or Vanilla kernels.
OK if you really need a specific version there, here it is:
$ uname -a
Linux alkis 3.13.0-9.29-031400rc3-generic #201402181344 SMP Tue Feb 18 19:02:54 UTC 2014 i686 i686 i686 GNU/Linux
...but again that version number is useless because it doesn't happen in _any_ vanilla kernels.

** Tags removed: needs-apport-collect needs-upstream-testing
** Tags added: tested-upstream-its-ok-there-its-an-ubuntu-specific-bug

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

  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening.
  Excerpt from dmesg:
  [    3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to: