Booting time got slower with newer kernel versions

Bug #1359754 reported by Sworddragon on 2014-08-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Medium
Unassigned

Bug Description

I'm using Ubuntu 14.10 dev with linux-image-generic 3.16.0.9.10 and as already mentioned in the other ticket (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325819) I'm noticing a performance loss in booting time of a few seconds with newer versions of the kernel. But interestingly one linked kernel in the other ticket (http://kernel.ubuntu.com/~jsalisbury/lp1325819/ -> 3.13.0-031300rc3-generic) doesn't have this problem. In the attachments are 2 dmesg logs of the different kernels. As they show the 3.13.0-031300rc3-generic was ~2 seconds faster with loading the nvidia module (last lines in dmesg) than the current kernel. I'm wondering why there is this difference between those kernels in booting time.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.16.0-9-generic.
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
BootDmesg: (Nothing has been logged yet.)
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,18497662,00100101'
   Controls : 36
   Simple ctrls : 18
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19'
   Mixer name : 'Nvidia GPU 42 HDMI/DP'
   Components : 'HDA:10de0042,14583555,00100100'
   Controls : 21
   Simple ctrls : 3
CurrentDesktop: LXDE
DistroRelease: Ubuntu 14.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-9-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-9-generic N/A
 linux-backports-modules-3.16.0-9-generic N/A
 linux-firmware 1.132
RfKill: Error: [Errno 2] No such file or directory
Tags: utopic
Uname: Linux 3.16.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.asset.tag: BC5FF4739C55
dmi.board.name: 960GM/U3S3 FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Sworddragon (sworddragon) wrote :
Sworddragon (sworddragon) wrote :

apport information

tags: added: apport-collected utopic
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-bisect
Sworddragon (sworddragon) wrote :

I have made now some tests and have figured out that on the slow booting kernels the console output is slow too. For example on "time dmesg" the slow kernels needs 3.5 seconds of real time while the fast kernels needs only 1 second of real time. Could it be that the slow console output causes the boot delay (I'm using GRUB_CMDLINE_LINUX_DEFAULT="elevator=cfq" so I'm getting more output than usual on booting)?

On testing the kernels I'm seeing a fast console output on linux-image-3.13.1-031301-generic (3.13.1-031301.201401291035) but not on linux-image-3.13.2-031302-generic (3.13.2-031302.201402061638). Also on the first one I'm seeing specific dmesg entries much earlier but the total booting time isn't that fast too. That makes me unsure if this issue has really something to do with the booting problem. Possibly this problem should be bisected first to test if after a fix the booting delay still exists on recent kernels?

Joseph Salisbury (jsalisbury) wrote :

Before starting a bisect, would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/

tags: added: kernel-bug-exists-upstream
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Sworddragon (sworddragon) wrote :
tags: added: kernel-bug-reported-upstream
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.