I will look into bootcharts as soon as possible. I was expecting more info from the log of step #6.
You will recall that rate limiting gave the following kind of output: [ 17.062400] init: plymouth-upstart-bridge main process ended, respawning [ 42.218430] audit_printk_skb: 177 callbacks suppressed When /etc/sysctl.d/99-printk_ratelimiting.conf with kernel.printk_ratelimit=0 was implemented, I expected detail on those callbacks. Instead, I got: [ 17.530175] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 19.396738] init: plymouth-upstart-bridge main process ended, respawning [ 44.236269] type=1400 audit(1437703237.706:71): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2413 comm="apparmor_parser" What happened between 19 secs and 44 secs? Remember, this is a fast 4 core machine. I would appreciate your thoughts on that? Then we can look at bootcharts. Thanks. ** Changed in: apparmor (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458014 Title: audit_printk_skb slowing down boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1458014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs