Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

very slow boot

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
dove
Posts: 14
Joined: 2010-03-31 20:54

very slow boot

#1 Post by dove »

My laptop (i3,4g ram) with stretch mate 64b has suddenly started very slow boot. Output for

Code: Select all

systemd-analyze blame
is

Code: Select all

 3.043s iio-sensor-proxy.service
          1.469s apt-daily-upgrade.service
           748ms exim4.service
           657ms upower.service
           559ms dev-sdb1.device
           459ms ModemManager.service
           366ms loadcpufreq.service
           327ms accounts-daemon.service
           288ms NetworkManager.service
           216ms systemd-logind.service
           201ms lm-sensors.service
           200ms speech-dispatcher.service
           197ms keyboard-setup.service
           189ms avahi-daemon.service
           187ms rtkit-daemon.service
           172ms pppd-dns.service
           150ms systemd-timesyncd.service
           148ms systemd-fsck@dev-disk-by\x2duuid-5571228c\x2d3974\x2d4741\x2dad78\x2d76
           143ms udisks2.service
           134ms systemd-journald.service
           115ms systemd-fsck@dev-disk-by\x2duuid-e35eb82f\x2d5318\x2d4380\x2d8e42\x2dd0
           108ms systemd-rfkill.service
           104ms networking.service
           100ms systemd-udevd.service
            99ms rsyslog.service
            97ms polkit.service
            96ms systemd-udev-trigger.service
            90ms lightdm.service
            63ms user@1000.service
            54ms user@111.service
            47ms wpa_supplicant.service
            45ms systemd-tmpfiles-setup-dev.service
            42ms systemd-backlight@backlight:intel_backlight.service
            34ms boot.mount
            31ms dev-mqueue.mount
            29ms systemd-tmpfiles-setup.service
            24ms systemd-remount-fs.service
How can I fix?

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: very slow boot

#2 Post by debiman »

^ that output doesn't look so bad.
do you have any reason to believe that the services at the top are responsible?
3 extra seconds isn't much.
what's "very slow" by your standards?
most common cause are networking problems (but i think they should show up in systemd-analyze).

Wheelerof4te
Posts: 1454
Joined: 2015-08-30 20:14

Re: very slow boot

#3 Post by Wheelerof4te »

If that is slow, then what's this?

Code: Select all

systemd-analyze
Startup finished in 3.549s (firmware) + 1.761s (loader) + 3.863s (kernel) + 20.730s (userspace) = 29.904s
graphical.target reached after 20.723s in userspace

Code: Select all

systemd-analyze blame
          7.106s NetworkManager-wait-online.service
          4.197s udisks2.service
          4.169s dev-sda2.device
          4.079s NetworkManager.service
          3.978s ModemManager.service
          3.731s accounts-daemon.service
          2.797s networking.service
          2.779s rsyslog.service
          2.709s wpa_supplicant.service
          2.698s bluetooth.service
          2.694s lm-sensors.service
          2.688s switcheroo-control.service
          2.688s systemd-logind.service
          2.682s pppd-dns.service
          2.596s avahi-daemon.service
          1.572s packagekit.service
          1.328s systemd-fsck@dev-disk-by\x2duuid-2C02\x2dA00C.service
          1.202s apparmor.service
           975ms keyboard-setup.service
           941ms polkit.service
           885ms systemd-backlight@backlight:intel_backlight.service
           645ms dev-disk-by\x2duuid-8070911e\x2d4

dove
Posts: 14
Joined: 2010-03-31 20:54

Re: very slow boot

#4 Post by dove »

After I sign in I have a pointer but no desktop for about 60s or more

User avatar
sunrat
Administrator
Administrator
Posts: 6457
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 472 times

Re: very slow boot

#5 Post by sunrat »

Run

Code: Select all

journalctl -b -p3
to see if any related errors show up.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

dove
Posts: 14
Joined: 2010-03-31 20:54

Re: very slow boot

#6 Post by dove »

output is

Code: Select all

-- Logs begin at Fri 2018-05-04 16:22:27 PDT, end at Fri 2018-05-04 16:24:44 PDT. --
May 04 16:22:27 dove kernel: usb 1-1.4: string descriptor 0 read error: -22
May 04 16:22:28 dove kernel: usb 1-1.4: firmware: failed to load ar3k/AthrBT_0x11020000.dfu (-2)
May 04 16:22:28 dove kernel: Bluetooth: Loading patch file failed
May 04 16:22:28 dove avahi-daemon[426]: chroot.c: open() failed: No such file or directory
May 04 16:23:10 dove pulseaudio[1138]: [pulseaudio] pid.c: Daemon already running.

User avatar
sunrat
Administrator
Administrator
Posts: 6457
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 472 times

Re: very slow boot

#7 Post by sunrat »

Do you still get slow boot with your USB device unplugged? I occasionally get a stall like that when my USB wifi dongle isn't recognised instantly.
That firmware is in the package firmware-atheros from the non-free repo. Do you have it installed?
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

dove
Posts: 14
Joined: 2010-03-31 20:54

Re: very slow boot

#8 Post by dove »

Yes I have it installed

dove
Posts: 14
Joined: 2010-03-31 20:54

Re: very slow boot

#9 Post by dove »

I have a usb mouse

User avatar
sunrat
Administrator
Administrator
Posts: 6457
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 472 times

Re: very slow boot

#10 Post by sunrat »

Bluetooth mouse? If you have the firmware installed it shouldn't be failing to load. It's probably either that or the avahi service. Disable avahi if you don't use it. But I suspect the USB as I've seen a similar issue as I said.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

Post Reply