Slower boot since GRUB update

Asked by peterzay

Since the recent update to GRUB, my boots of 14.04 are slower.

Is this a bug or a feature?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Can you define slower... Is it taking minutes to boot?

Revision history for this message
peterzay (peterzay) said :
#2

It is taking about 50 secs to get the password screen.

The machine is Dell Inspiron 660 desktop Core i5, 4 physical processors of 3GHz each.

I never timed the previous boots. They seem slower now.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

If you run:

dmesg | less

Use SPACE to scroll down page by page and look for large gaps in the numbers on the left. This is seconds since the kernel came online. This will help isolate the issue.

Revision history for this message
peterzay (peterzay) said :
#4

Here is the final screen of dmesg | less

[ 16.315349] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 16.495787] r8169 0000:04:00.0 eth0: link down
[ 16.495803] r8169 0000:04:00.0 eth0: link down
[ 16.495836] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 16.496109] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.061465] r8169 0000:04:00.0 eth0: link up
[ 18.061473] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 21.918107] init: plymouth-upstart-bridge main process ended, respawning
[ 21.921780] init: plymouth-upstart-bridge main process (1558) terminated with status 1
[ 21.921790] init: plymouth-upstart-bridge main process ended, respawning
[ 30.720726] hda-codec: out of range cmd 0:4:707:ffffffff
[ 41.414185] audit_printk_skb: 177 callbacks suppressed
[ 41.414187] type=1400 audit(1431817764.860:71): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2008 comm="apparmor_parser"
[ 41.414192] type=1400 audit(1431817764.860:72): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2008 comm="apparmor_parser"
[ 41.414532] type=1400 audit(1431817764.860:73): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2008 comm="apparmor_parser"
[ 50.155098] hda-codec: out of range cmd 0:5:707:ffffffbf
(END)

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

That's 45 seconds. Seems to be an apparmor issue

Revision history for this message
peterzay (peterzay) said :
#6

Are you sure? Here is another dump from today. Note the very large amount of time to get to audit_printk_skb in both cases.

[ 13.243280] vboxdrv: Successfully loaded version 4.3.10_Ubuntu (interface 0x001a0007).
[ 13.257947] vboxpci: IOMMU not found (not registered)
[ 13.862999] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 13.865996] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.195776] r8169 0000:04:00.0 eth0: link down
[ 14.195796] r8169 0000:04:00.0 eth0: link down
[ 14.195827] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 14.196138] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 15.769090] r8169 0000:04:00.0 eth0: link up
[ 15.769097] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 16.223084] init: plymouth-upstart-bridge main process ended, respawning
[ 42.424836] audit_printk_skb: 195 callbacks suppressed
[ 42.424839] type=1400 audit(1431891089.974:77): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2632 comm="apparmor_parser"
[ 42.424844] type=1400 audit(1431891089.974:78): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2632 comm="apparmor_parser"
[ 42.425185] type=1400 audit(1431891089.974:79): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2632 comm="apparmor_parser"
(END)

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.