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.
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 upstart- bridge main process ended, respawning 7.706:71) : apparmor="STATUS" operation= "profile_ replace" profile= "unconfined" name="/ usr/lib/ cups/backend/ cups-pdf" pid=2413 comm="apparmor_ parser"
[ 19.396738] init: plymouth-
[ 44.236269] type=1400 audit(143770323
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.