← Back to team overview

kernel-packages team mailing list archive

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


The problem is not there in Ubuntu 12.04.2 (kernel 3.5.0-54)
and it is there in Ubuntu 12.04.3 (kernel 3.8.0-44).

My test case is to boot with ip=dhcp break=top. When the problem doesn't
exist, I get an initramfs prompt in 2 seconds, when it exists I get it
in 12 seconds, and that shows up in dmesg as well.

Comparing those configs from https://wiki.ubuntu.com/Kernel/Configs/QuantalToRaring, I got:
3.5: # CONFIG_IP_PNP is not set

Is it possible to revert those?
Can we find out why they were enabled?
If they're only needed on some arches (e.g. ARM), maybe they could only be enabled there?

@rhansen, writing an alias e.g. initramfs_ip=* won't help, e.g. IPAPPEND 3 in pxelinux puts ip=* in the cmdline, I don't think it'll ever be patched to put initramfs_ip=* there...
I think we should either get the configuration change reverted,
or fix ipconfig.c so that it aborts if no NICs/modules are detected.

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: