Comment 30 for bug 1235231

On a regular trusty laptop with an SSD i did 6 boots (3 reboots and 3 cold boots), and compared the boot.logs.
My expectation is to have no less than 6 instances of each unique boot messages, that is not the case:
      1 * Starting Bridge socket events into upstart
      1 * Starting modem connection manager
      1 * Starting Restore Sound Card State
      1 * Starting System V initialisation compatibility
      2 * Starting bluetooth daemon
      2 * Starting configure network device
      2 * Starting system logging daemon
      3 * Starting save kernel messages
      3 * Stopping save kernel messages
      4 * Starting Bridge file events into upstart
      4 * Starting save udev log and update rules
      4 * Starting SystemD login management service
      4 * Stopping save udev log and update rules
      5 * Starting ACPI daemon
      5 * Starting enable remaining boot-time encrypted block devices
      5 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated
      5 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated
      5 * Stopping cold plug devices
      5 * Stopping log initial device creation

bootlogs attached.

I'm not sure if this is the same or different problem.