Speeding up Booting - Boot Time 8min 29.588sec with userspace alone 8min 16.386sec

After going through the thread Speeding Up Linux I came to know that booting speed can be tweaked and my system is insanely slow.

Just after booting up (KDE loaded, after entering username and password), I got following output in konsole

akash@akash:~> systemd-analyze critical-chain 
Bootup is not yet finished. Please try again later.
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

Only after sometime the konsole gave the output it should.

akash@akash:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @8min 16.381s
└─multi-user.target @8min 16.381s
  └─dkms.service @20.128s +2min 13.215s
    └─basic.target @20.119s
      └─timers.target @20.118s
        └─systemd-tmpfiles-clean.timer @20.118s
          └─sysinit.target @20.118s
            └─apparmor.service @19.827s +290ms
              └─systemd-tmpfiles-setup.service @19.304s +522ms
                └─local-fs.target @19.291s
                  └─run-user-1000-gvfs.mount @1min 3.794s
                    └─local-fs-pre.target @6.435s
                      └─systemd-remount-fs.service @6.268s +165ms
                        └─systemd-fsck-root.service @5.197s +1.069s
                          └─systemd-readahead-replay.service @4.851s +222ms
akash@akash:~> systemd-analyze
Startup finished in 4.006s (firmware) + 2.911s (loader) + 2.772s (kernel) + 3.510s (initrd) + 8min 16.386s (userspace) = 8min 29.588s
akash@akash:~> systemd-analyze blame                                                                                                                                                            
    7min 56.247s purge-kernels.service                                                                                                                                                          
    2min 13.215s dkms.service                                                                                                                                                                   
         23.700s SuSEfirewall2_init.service                                                                                                                                                     
         20.284s ModemManager.service                                                                                                                                                           
         19.466s display-manager.service                                                                                                                                                        
         11.418s SuSEfirewall2.service                                                                                                                                                          
          8.961s systemd-udev-settle.service                                                                                                                                                    
          3.844s lvm2-activation-early.service                                                                                                                                                  
          3.458s run-media-akash-DATA.mount                                                                                                                                                     
          3.052s vboxdrv.service
          1.567s boot-efi.mount
          1.388s systemd-journald.service
          1.372s systemd-tmpfiles-setup-dev.service
          1.312s dev-mqueue.mount
          1.312s dev-mqueue.mount
          1.312s sys-kernel-debug.mount
          1.312s dev-hugepages.mount
          1.069s systemd-fsck-root.service
           899ms jexec.service
           897ms systemd-udev-trigger.service
           728ms systemd-modules-load.service
           728ms alsa-restore.service
           727ms console-kit-log-system-start.service
           724ms lvm2-activation.service
           721ms systemd-user-sessions.service
           717ms nscd.service
           716ms rc-local.service
           689ms postfix.service
           688ms avahi-daemon.service
           682ms wpa_supplicant.service
           522ms systemd-tmpfiles-setup.service
           341ms dm-event.service
           318ms NetworkManager.service
           290ms apparmor.service
           287ms rtkit-daemon.service
           259ms polkit.service
           222ms systemd-readahead-replay.service
           173ms systemd-readahead-collect.service
           165ms systemd-remount-fs.service
           153ms proc-sys-fs-binfmt_misc.mount
           146ms kmod-static-nodes.service
           121ms lvm2-lvmetad.service
           117ms cycle.service
           101ms udisks2.service
            75ms plymouth-read-write.service
            62ms user@1000.service
            55ms systemd-sysctl.service
            54ms dev-sda8.swap
            48ms systemd-udev-root-symlink.service
            44ms auditd.service
            25ms console-kit-daemon.service
            16ms systemd-vconsole-setup.service
            15ms plymouth-start.service
             7ms systemd-journal-flush.service
             7ms upower.service
             6ms systemd-rfkill@rfkill0.service
             6ms systemd-logind.service
             5ms systemd-rfkill@rfkill1.service
             4ms iscsi.service
             4ms systemd-update-utmp-runlevel.service
             4ms bluetooth.service
             3ms systemd-update-utmp.service
             3ms systemd-readahead-done.service
             2ms sys-fs-fuse-connections.mount
             2ms systemd-random-seed.service
             2ms systemd-udevd.service
             2ms systemd-backlight@backlight:intel_backlight.service
             1ms systemd-rfkill@rfkill2.service

Why is my system taking so much time. My hardware is not that old.

My system - Acer V3 571G Laptop, Core i5 - 3230M with 4GB DD3, Nvidia 710M GPU with bumblebee installed and 750 GB HDD

So what my laptop has HDD not SSD. 8min 29.588sec booting time is insane. >:(
Yesterday I happened to talk to sysrich on irc and I clearly envy his system which boots up in 5 secs straight. :expressionless:

On 2015-04-23 12:46, vish 99 wrote:

> 7min 56.247s purge-kernels.service
> 2min 13.215s dkms.service

Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Yes and how can I decrease it?

Just be patient :stuck_out_tongue:

Those two should only show up on the first boot after a kernel update. And kernel updates are infrequent (maybe once every three months), unless you are getting them from the kernel repo.

On 2015-04-23 15:46, vish 99 wrote:
> robin_listas;2706437 Wrote:
>> On 2015-04-23 12:46, vish 99 wrote:
>>> 7min 56.247s purge-kernels.service
>>> 2min 13.215s dkms.service
> Yes and how can I decrease it?

You probably can’t. However, that should only happen once, just after
you updated the kernel. You might have a look at the logs to find out
the sequence of events.

Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))


At second boot.

akash@akash:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @51.511s
└─multi-user.target @51.511s
  └─cron.service @51.511s
    └─postfix.service @51.169s +341ms
      └─network.target @51.151s
        └─NetworkManager.service @50.884s +266ms
          └─SuSEfirewall2_init.service @18.074s +32.808s
            └─basic.target @17.654s
              └─timers.target @17.653s
                └─systemd-tmpfiles-clean.timer @17.653s
                  └─sysinit.target @17.653s
                    └─apparmor.service @17.301s +351ms
                      └─systemd-tmpfiles-setup.service @16.543s +756ms
                        └─local-fs.target @16.530s
                          └─run-media-akash-DATA.mount @12.713s +2.454s
                            └─dev-disk-by\x2dlabel-DATA.device @12.712s
akash@akash:~> systemd-analyze
Startup finished in 2.503s (firmware) + 2.060s (loader) + 2.800s (kernel) + 3.785s (initrd) + 51.515s (userspace) = 1min 2.665s
akash@akash:~> systemd-analyze blame
         33.266s ModemManager.service
         32.905s display-manager.service
         32.808s SuSEfirewall2_init.service
         19.719s dkms.service                                                                                                                                                                   
          8.389s systemd-udev-settle.service                                                                                                                                                    
          7.812s systemd-logind.service                                                                                                                                                         
          2.454s run-media-akash-DATA.mount                                                                                                                                                     
          1.795s systemd-tmpfiles-setup-dev.service                                                                                                                                             
          1.550s lvm2-activation.service                                                                                                                                                        
          1.461s dev-mqueue.mount                                                                                                                                                               
          1.460s sys-kernel-debug.mount                                                                                                                                                         
          1.460s dev-hugepages.mount                                                                                                                                                            
          1.258s lvm2-activation-early.service                                                                                                                                                  
          1.225s systemd-fsck-root.service                                                                                                                                                      
          1.148s systemd-backlight@backlight:intel_backlight.service                                                                                                                            
           922ms systemd-journald.service                                                                                                                                                       
           756ms systemd-tmpfiles-setup.service                                                                                                                                                 
           482ms systemd-modules-load.service
           462ms systemd-udev-trigger.service
           443ms jexec.service
           421ms alsa-restore.service
           420ms console-kit-log-system-start.service
           420ms vboxdrv.service
           416ms systemd-user-sessions.service
           414ms nscd.service
           414ms rc-local.service
           400ms boot-efi.mount
           365ms avahi-daemon.service
           363ms systemd-rfkill@rfkill1.service
           361ms systemd-rfkill@rfkill2.service
           360ms systemd-rfkill@rfkill0.service
           359ms wpa_supplicant.service
           351ms apparmor.service
           341ms postfix.service
           290ms systemd-readahead-replay.service
           266ms NetworkManager.service
           262ms dm-event.service
           195ms udisks2.service
           175ms SuSEfirewall2.service
           151ms systemd-readahead-collect.service
           144ms systemd-sysctl.service
           124ms polkit.service
           124ms kmod-static-nodes.service
           111ms lvm2-lvmetad.service
           111ms user@1000.service
            94ms dev-sda8.swap
            84ms rtkit-daemon.service
            63ms plymouth-read-write.service
            48ms systemd-udev-root-symlink.service
            33ms auditd.service
            27ms console-kit-daemon.service
            25ms cycle.service
            17ms plymouth-start.service
            12ms systemd-vconsole-setup.service
             7ms systemd-journal-flush.service
             6ms iscsi.service
             6ms proc-sys-fs-binfmt_misc.mount
             5ms upower.service
             3ms systemd-remount-fs.service
             3ms systemd-update-utmp.service
             2ms systemd-readahead-done.service
             2ms systemd-update-utmp-runlevel.service
             2ms bluetooth.service
             2ms sys-fs-fuse-connections.mount
             1ms systemd-random-seed.service
             1ms systemd-udevd.service

But, still I’m not happy. :expressionless:

Can I do anything to boost booting speed other than fitting SSD?

Reduce the number of services you use. ModemManager.service seems to be slow are you on a modem? Maybe it is your IP that is slow to come up.

Is ModemManager.service required to connect using wifi also? I used LAN (wired) maybe last year. If not, how can I disable ModemManager.service.

I’m mounting NTFS partition (just stores DATA) also at boot. Is mounting it also causing delays.

akash@akash:~> df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda11       55G   50G  3.7G  94% /
devtmpfs        1.9G     0  1.9G   0% /dev
tmpfs           1.9G   80K  1.9G   1% /dev/shm
tmpfs           1.9G  2.2M  1.9G   1% /run
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/sda2       296M   52M  245M  18% /boot/efi
/dev/sda6       430G  359G   72G  84% /run/media/akash/DATA
akash@akash:~> cat /etc/fstab 
UUID=0c159219-6a81-422b-bbbb-7ed89e2a2071       swap                            swap       defaults                                     0 0
LABEL=opensuse                                  /                               ext4       acl,user_xattr                               1 1
LABEL=ESP                                       /boot/efi                       vfat       umask=0002,utf8=true                         0 0
LABEL=DATA                                      /run/media/akash/DATA           ntfs       defaults, utf8=true, nls=utf8, no fail       0 0

You do need it I guess if you use NetworkManager but I’d say the time is spent on the connection. ie you Internet Service provider is slow to connect

What if I disable networking from system tray before shutting down and enable it again after booting up. Will that increase my booting speed.

P.S. - I don’t connect to internet all the time. When I’m at university premises I connect to internet and when I at hostel I don’t.

Maybe never tried it myself It will show how long the connection takes in any case

Why is dkms.service showing up again. This time no new kernel is installed. And 19.719s is much time.

I’m mounting NTFS partition (just stores DATA) also at boot. Is mounting it also causing delays.

2.454s run-media-akash-DATA.mount

Got the answer. 2.454s is OK.

As a reference her is my blame with root on a SSD AMD FX 6 core processor wired Internet

dkms dose not run just with kernel updates many thing may use it if updated to link to the kernel

linux:/home/gogalthorp # systemd-analyze blame
         10.021s nmb.service
          3.077s systemd-udev-settle.service
           438ms vboxdrv.service
           381ms systemd-fsck@dev-disk-by\x2duuid-56d26ae8\x2d356c\x2d41b7\x2d8795\x2d8c85e618fbff.service
           251ms apparmor.service
           243ms postfix.service
           199ms SuSEfirewall2.service
           167ms vm.mount
           152ms vboxadd.service
           136ms lvm2-activation-early.service
           120ms systemd-fsck@dev-disk-by\x2duuid-3bd79acb\x2d9f73\x2d411b\x2dacae\x2dd5c1f8debf48.service
           118ms SuSEfirewall2_init.service
            75ms user@1000.service
            65ms display-manager.service
            51ms systemd-udev-trigger.service
            49ms ModemManager.service
            46ms home.mount
            41ms lvm2-lvmetad.service
            40ms systemd-journald.service
            40ms dm-event.service
            38ms smb.service
            36ms udisks2.service
            36ms systemd-tmpfiles-setup-dev.service
            32ms systemd-fsck-root.service
            26ms NetworkManager.service
            24ms dev-mqueue.mount
            24ms dev-hugepages.mount
            24ms alsa-restore.service
            22ms systemd-user-sessions.service
            21ms sys-kernel-debug.mount
            21ms lvm2-activation.service
            20ms nscd.service
            20ms avahi-daemon.service
            19ms wpa_supplicant.service
            19ms rc-local.service                                                                                                          
            17ms polkit.service
            16ms systemd-random-seed.service
            16ms plymouth-read-write.service
            15ms systemd-modules-load.service
            15ms plymouth-start.service

Then it should come all the time. Then, why it isn’t showing up with yours then. I’m confused. Pardon Me.

Nope it doesn’t.

Q1. Can I put a limit that ModemManager.service should look to connect for only certain period of time and after that it should quit searching for internet whether it connects to internet or not.

Q2. What is the shortest method to turn on / turn off the ModemManager.service? Will it take less than 13.859s? I know it’s insane question.

And dkms.service still shows up.

akash@akash:~> systemd-analyze blame
         13.859s ModemManager.service
         13.603s display-manager.service
         13.353s dkms.service
         13.287s SuSEfirewall2_init.service
          9.494s systemd-udev-settle.service
          2.165s lvm2-activation.service
          1.902s run-media-akash-DATA.mount
          1.877s lvm2-activation-early.service
          1.833s sys-kernel-debug.mount
          1.833s dev-hugepages.mount
          1.832s dev-mqueue.mount
          1.674s systemd-fsck-root.service
          1.598s systemd-tmpfiles-setup-dev.service
           953ms vboxdrv.service
           609ms systemd-udev-trigger.service
           604ms systemd-backlight@backlight:intel_backlight.service
           577ms systemd-modules-load.service
           565ms postfix.service
           562ms jexec.service
           533ms systemd-remount-fs.service
           529ms alsa-restore.service
           529ms console-kit-log-system-start.service
           518ms systemd-user-sessions.service
           513ms nscd.service
           511ms rc-local.service
           502ms systemd-journald.service
           456ms avahi-daemon.service
           455ms NetworkManager.service
           446ms wpa_supplicant.service
           382ms dm-event.service
           363ms systemd-tmpfiles-setup.service
           345ms boot-efi.mount
           336ms SuSEfirewall2.service
           289ms apparmor.service
           233ms upower.service
           230ms rtkit-daemon.service
           199ms systemd-sysctl.service
           171ms systemd-readahead-replay.service                                                                                                                                               
           165ms udisks2.service                                                                                                                                                                
           159ms user@1000.service                                                                                                                                                              
           146ms systemd-rfkill@rfkill1.service                                                                                                                                                 
           146ms systemd-rfkill@rfkill2.service                                                                                                                                                 
           145ms systemd-readahead-collect.service                                                                                                                                              
           141ms systemd-rfkill@rfkill0.service                                                                                                                                                 
           126ms cycle.service                                                                                                                                                                  
           125ms kmod-static-nodes.service                                                                                                                                                      
           111ms lvm2-lvmetad.service                                                                                                                                                           
           105ms console-kit-daemon.service                                                                                                                                                     
            87ms dev-sda8.swap                                                                                                                                                                  
            76ms bluetooth.service                                                                                                                                                              
            56ms auditd.service                                                                                                                                                                 
            49ms systemd-udev-root-symlink.service
            36ms plymouth-read-write.service

The blame is only an indicator, I would guess the culpret is dkms service and probably related to vbox service, something is probably being rebuilt and/or failing.

If you disable the vbox service temporarily, is there an improvement?


systemctl disable vboxdrv.service

and rebooted the system.

Nope. Instead it increases the booting time. Time for dkms.service increases to 22.993s from 13.353s. So, I’m re-enabling vboxdrv.service

akash@akash:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @42.310s
└─multi-user.target @42.310s
  └─SuSEfirewall2.service @30.292s +12.016s
    └─network.target @30.243s
      └─NetworkManager.service @28.276s +1.964s
        └─SuSEfirewall2_init.service @19.523s +8.746s
          └─basic.target @18.743s
            └─timers.target @18.742s
              └─systemd-tmpfiles-clean.timer @18.742s
                └─sysinit.target @18.742s
                  └─apparmor.service @17.897s +845ms
                    └─systemd-tmpfiles-setup.service @17.655s +240ms
                      └─local-fs.target @17.640s
                        └─run-media-akash-DATA.mount @12.963s +3.077s
                          └─dev-disk-by\x2dlabel-DATA.device @12.962s
akash@akash:~> systemd-analyze                  
Startup finished in 2.505s (firmware) + 2.233s (loader) + 2.780s (kernel) + 3.612s (initrd) + 42.316s (userspace) = 53.448s
akash@akash:~> systemd-analyze blame            
         22.993s dkms.service
         12.016s SuSEfirewall2.service
         10.401s display-manager.service
         10.151s ModemManager.service
          9.380s systemd-udev-settle.service
          8.746s SuSEfirewall2_init.service
          3.077s run-media-akash-DATA.mount
          2.049s systemd-tmpfiles-setup-dev.service
          1.964s NetworkManager.service
          1.844s lvm2-activation-early.service
          1.833s bluetooth.service
          1.597s systemd-fsck-root.service
          1.500s systemd-journald.service
          1.467s boot-efi.mount
          1.458s dev-mqueue.mount
          1.458s sys-kernel-debug.mount
          1.457s systemd-backlight@backlight:intel_backlight.service
          1.457s dev-hugepages.mount
          1.394s vboxdrv.service
          1.043s dev-sda8.swap
          1.008s lvm2-activation.service
           900ms postfix.service
           897ms rtkit-daemon.service
           845ms apparmor.service
           819ms jexec.service
           813ms systemd-random-seed.service
           782ms alsa-restore.service
           781ms console-kit-log-system-start.service
           771ms systemd-user-sessions.service
           765ms nscd.service
           765ms rc-local.service
           729ms avahi-daemon.service
           718ms wpa_supplicant.service
           627ms systemd-modules-load.service
           626ms polkit.service
           546ms systemd-udev-trigger.service                                                                                                                                                   
           498ms auditd.service                                                                                                                                                                 
           409ms systemd-rfkill@rfkill1.service                                                                                                                                                 
           404ms systemd-rfkill@rfkill0.service                                                                                                                                                 
           402ms systemd-rfkill@rfkill2.service                                                                                                                                                 
           377ms systemd-sysctl.service                                                                                                                                                         
           344ms dm-event.service                                                                                                                                                               
           344ms lvm2-lvmetad.service                                                                                                                                                           
           240ms systemd-tmpfiles-setup.service                                                                                                                                                 
           159ms systemd-readahead-replay.service                                                                                                                                               
           142ms systemd-readahead-collect.service                                                                                                                                              
           110ms kmod-static-nodes.service                                                                                                                                                      
            80ms plymouth-read-write.service                                                                                                                                                    
            53ms udisks2.service                                                                                                                                                                
            48ms systemd-udev-root-symlink.service
            42ms user@1000.service
            30ms cycle.service
            29ms console-kit-daemon.service
            19ms plymouth-start.service
            15ms systemd-vconsole-setup.service
            13ms systemd-logind.service
            12ms proc-sys-fs-binfmt_misc.mount
             8ms upower.service
             7ms iscsi.service
             7ms systemd-journal-flush.service
             5ms systemd-remount-fs.service
             5ms systemd-update-utmp.service
             5ms systemd-update-utmp-runlevel.service
             3ms systemd-readahead-done.service
             2ms systemd-udevd.service
             2ms sys-fs-fuse-connections.mount

Modem manager is required to manage 2G/3G/4G modems.


systemctl enable vboxdrv.service

and rebooted again

akash@akash:~> systemd-analyze
Startup finished in 2.052s (firmware) + 2.990s (loader) + 2.801s (kernel) + 3.190s (initrd) + 36.649s (userspace) = 47.684s
akash@akash:~> systemd-analyze critical-chain  
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @36.644s
└─multi-user.target @36.644s
  └─cron.service @36.644s
    └─postfix.service @35.774s +868ms
      └─network.target @35.755s
        └─NetworkManager.service @35.516s +238ms
          └─SuSEfirewall2_init.service @18.823s +16.691s
            └─basic.target @18.058s
              └─timers.target @18.058s
                └─systemd-tmpfiles-clean.timer @18.058s
                  └─sysinit.target @18.058s
                    └─apparmor.service @17.772s +285ms
                      └─systemd-tmpfiles-setup.service @17.424s +347ms
                        └─local-fs.target @17.413s
                          └─run-media-akash-DATA.mount @11.772s +2.523s
                            └─dev-disk-by\x2dlabel-DATA.device @11.771s
akash@akash:~> systemd-analyze blame
         17.166s ModemManager.service
         16.691s SuSEfirewall2_init.service
         16.392s display-manager.service
         15.988s dkms.service
          7.414s systemd-udev-settle.service
          2.533s lvm2-activation.service
          2.523s run-media-akash-DATA.mount
          1.524s vboxdrv.service
          1.516s lvm2-activation-early.service
          1.154s systemd-udev-trigger.service
          1.101s dev-mqueue.mount
          1.101s sys-kernel-debug.mount
          1.101s dev-hugepages.mount
           937ms systemd-tmpfiles-setup-dev.service
           898ms systemd-fsck-root.service
           868ms postfix.service
           808ms jexec.service
           767ms alsa-restore.service
           766ms systemd-journald.service
           766ms console-kit-log-system-start.service
           765ms systemd-user-sessions.service
           764ms nscd.service
           762ms rc-local.service
           758ms systemd-modules-load.service
           707ms avahi-daemon.service
           702ms wpa_supplicant.service
           523ms boot-efi.mount
           413ms dm-event.service
           347ms systemd-tmpfiles-setup.service
           294ms systemd-remount-fs.service
           285ms apparmor.service
           240ms SuSEfirewall2.service
           238ms NetworkManager.service
           234ms systemd-udevd.service
           215ms cycle.service
           168ms systemd-readahead-replay.service
           154ms polkit.service
           153ms systemd-readahead-collect.service
           141ms rtkit-daemon.service
           124ms kmod-static-nodes.service
           111ms lvm2-lvmetad.service
           104ms console-kit-daemon.service
            74ms systemd-random-seed.service
            66ms dev-sda8.swap
            56ms auditd.service
            55ms user@1000.service
            48ms systemd-udev-root-symlink.service
            42ms udisks2.service
            40ms plymouth-read-write.service
            15ms systemd-vconsole-setup.service
            15ms systemd-logind.service
            14ms plymouth-start.service
            11ms proc-sys-fs-binfmt_misc.mount
             6ms upower.service
             5ms systemd-rfkill@rfkill1.service
             5ms systemd-journal-flush.service
             4ms systemd-update-utmp-runlevel.service
             4ms systemd-rfkill@rfkill0.service
             3ms iscsi.service
             3ms systemd-sysctl.service
             3ms bluetooth.service
             3ms systemd-rfkill@rfkill2.service
             2ms systemd-update-utmp.service
             2ms sys-fs-fuse-connections.mount
             1ms systemd-backlight@backlight:intel_backlight.service
             1ms systemd-readahead-done.service

If you disable networking when you do not need it, and turn off the firewall before shutting down, then turn your firewall back on after booting, it will make a significant difference to your boot time.

You might also look into the long display-manager.service time. But, keep in mind, neither it nor ModemManager.service are in the critical chain.

You can lessen the initrd load time from almost 4 seconds to a couple seconds less by disabling or removing Plymouth and running:


But, your biggest boot-time improvement is going to come from booting with the firewall disabled.

You could investigate further to see why your firewall takes so long to load, and I think that may be affected by the ModemManager.service with a similar time.

ModemManager.service on my Acer Laptop (core 2 duo 2Ghz, 2-Gig memory) is 396ms compared to your 32 seconds + 266ms time.

Firewall on mine is 7.383 seconds compared to almost 33 seconds on yours.