Very slow login (30s!) and slow boot on Linux Mint 17.1

Please post suggestions for improvement of Cinnamon on:
https://github.com/linuxmint/Cinnamon
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
riFlo

Very slow login (30s!) and slow boot on Linux Mint 17.1

Post by riFlo »

Hi,
I have a Toshiba Notebook and installed LinuxMint 17 Cinnamon 64-Bit on it. Some time ago I upgraded to 17.1. Since Version 17 LinuxMint boots much slower than before and especially the login process is very slow. It takes at least 30s (sometimes 35s) to log into cinnamon, which is sometimes very annyoing because it seems to be a very long time for a today's notebook. During all this time the screen is black. The boot process is also slow. It takes 48 to 50s until the login screen appears. I can't remember such a slow login process while I used LinuxMint 16.
May it be some hardware problem or maybe a problem with the new cinnamon version? I tried some different kernel parameters without any success. Also I deactivated all applets, screenlets and unnecessary startup applications as well as wireless networking. The best result I got was 46s for boot process and 20s for login. But 20s for login still seems to be very much in my opinion. I use the free ATI graphics drivers because the proprietary ones caused much more trouble.

Here are the hardware specifications:

Code: Select all

System:    Host: Kernel: 3.13.0-37-generic x86_64 (64 bit) Desktop: Gnome Distro: Linux Mint 17.1 Rebecca
Machine:   System: TOSHIBA (portable) product: SATELLITE L875D-10R version: PSKFQE-04K033GR
           Mobo: AMD model: PLCSC8 Bios: Insyde version: 6.30 date: 12/06/2012
CPU:       Quad core AMD A8-4500M APU with Radeon HD Graphics (-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) 
           Clock Speeds: 1: 1400.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 1400.00 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Trinity [Radeon HD 7640G] 
           X.Org: 1.15.1 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1600x900@60.1hz 
           GLX Renderer: Gallium 0.4 on AMD ARUBA GLX Version: 3.0 Mesa 10.1.3
Audio:     Card-1: Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel
           Card-2: Advanced Micro Devices [AMD/ATI] Trinity HDMI Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture ver: k3.13.0-37-generic
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169 
           IF: eth0 state: down mac: 7c:05:07:21:ed:a3
           Card-2: Realtek RTL8723AE PCIe Wireless Network Adapter driver: rtl8723ae 
           IF: wlan0 state: up mac: 2c:d0:5a:bd:98:6b
Drives:    HDD Total Size: 1000.2GB (29.5% used) 1: id: /dev/sda model: TOSHIBA_MQ01ABD1 size: 1000.2GB 
Partition: ID: / size: 909G used: 275G (32%) fs: ext4 ID: swap-1 size: 8.02GB used: 0.00GB (0%) fs: swap 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 44.8C mobo: N/A gpu: 43.0 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 166 Uptime: 35 min Memory: 1265.9/7382.3MB Client: Shell inxi: 1.8.4 
I found some entries with a larger time offset in syslog:

Code: Select all

Feb 10 08:11:40 dnsmasq[1331]: vorgelagerte Server von DBus gesetzt
Feb 10 08:11:40 dnsmasq[1331]: Benutze Namensserver 192.168.2.1#53
Feb 10 08:11:40 dbus[863]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 10 08:11:44 NetworkManager[1191]: <info> WiFi hardware radio set enabled
Feb 10 08:11:47 anacron[1711]: Anacron 2.3 started on 2015-02-10
Feb 10 08:11:47 cron[1667]: (CRON) INFO (pidfile fd = 3)
Feb 10 08:11:47 cron[1720]: (CRON) STARTUP (fork ok)
Feb 10 08:11:47 cron[1720]: (CRON) INFO (Running @reboot jobs)
Feb 10 08:11:47 anacron[1711]: Will run job `cron.daily' in 5 min.
Feb 10 08:11:47 anacron[1711]: Jobs will be executed sequentially

Feb 10 08:11:50 ag[1977]: mdm-superinit Starting...
Feb 10 08:11:50 ag[1978]: mdm-superinit Finished
Feb 10 08:11:55 dbus[863]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Feb 10 08:11:55 dbus[863]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Feb 10 08:11:57 NetworkManager[1191]: <info> (wlan0): IP6 addrconf timed out or failed.
A syslog of another day is similar to the other one:

Code: Select all

Feb 16 15:38:03 ag[1962]: mdm-superinit Starting...
Feb 16 15:38:03 ag[1963]: mdm-superinit Finished
Feb 16 15:38:04 NetworkManager[1274]: <info> WiFi hardware radio set enabled
Feb 16 15:38:06 ntpdate[1524]: adjust time server 91.189.89.199 offset -0.125767 sec
Feb 16 15:38:09 dbus[898]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Feb 16 15:38:09 dbus[898]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Feb 16 15:38:12 dbus[898]: [system] Activating service name='org.freedesktop.RealtimeKit1' (using servicehelper)
Feb 16 15:38:12 dbus[898]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'

Feb 16 15:38:14 colord: Profile added: icc-6cb0c9f86e5db25162939936b8b6560a
Feb 16 15:38:14 colord: Profile added: icc-dfaebce3eea636804200e4cde6b934ba
Feb 16 15:38:17 NetworkManager[1274]: <info> (wlan0): IP6 addrconf timed out or failed.
Feb 16 15:38:17 NetworkManager[1274]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Feb 16 15:38:17 NetworkManager[1274]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Feb 16 15:38:17 NetworkManager[1274]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete...
I also found the following strange bluetooth messages:

Code: Select all

Feb 10 08:11:31 kernel: [   30.264973] init: bluetooth main process (900) terminated with status 1
Feb 10 08:11:31 kernel: [   30.264992] init: bluetooth main process ended, respawning
Feb 10 08:11:31 kernel: [   30.330808] init: cups main process (886) killed by HUP signal
Feb 10 08:11:31 kernel: [   30.330834] init: cups main process ended, respawning
Feb 10 08:11:31 kernel: [   30.353611] init: bluetooth main process (930) terminated with status 1
Feb 10 08:11:31 kernel: [   30.353633] init: bluetooth main process ended, respawning
Feb 10 08:11:31 kernel: [   30.389436] init: bluetooth main process (955) terminated with status 1
Feb 10 08:11:31 kernel: [   30.389454] init: bluetooth main process ended, respawning
Feb 10 08:11:31 kernel: [   30.423905] init: bluetooth main process (979) terminated with status 1
Feb 10 08:11:31 kernel: [   30.423926] init: bluetooth main process ended, respawning
Feb 10 08:11:31 kernel: [   30.462118] init: bluetooth main process (1014) terminated with status 1
Feb 10 08:11:31 kernel: [   30.462140] init: bluetooth main process ended, respawning
Feb 10 08:11:31 kernel: [   30.496616] init: bluetooth main process (1040) terminated with status 1
Feb 10 08:11:31 kernel: [   30.496638] init: bluetooth main process ended, respawning
Feb 10 08:11:31 bluez: Stopping rfcomm
Feb 10 08:11:31 bluetoothd[1069]: Bluetooth daemon 4.101
Which also appear in the dmesg output:

Code: Select all

[   30.264973] init: bluetooth main process (900) terminated with status 1
[   30.264992] init: bluetooth main process ended, respawning
[   30.330808] init: cups main process (886) killed by HUP signal
[   30.330834] init: cups main process ended, respawning
[   30.353611] init: bluetooth main process (930) terminated with status 1
[   30.353633] init: bluetooth main process ended, respawning
[   30.389436] init: bluetooth main process (955) terminated with status 1
[   30.389454] init: bluetooth main process ended, respawning
[   30.423905] init: bluetooth main process (979) terminated with status 1
[   30.423926] init: bluetooth main process ended, respawning
[   30.462118] init: bluetooth main process (1014) terminated with status 1
[   30.462140] init: bluetooth main process ended, respawning
[   30.496616] init: bluetooth main process (1040) terminated with status 1
[   30.496638] init: bluetooth main process ended, respawning
[   30.535257] init: bluetooth main process (1069) terminated with status 1
[   30.535279] init: bluetooth main process ended, respawning
I hope someone has an idea how to improve the login time and maybe also the boot time. I would be grateful for every suggestion.

Regards
riFlo
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
hpmc13
Level 3
Level 3
Posts: 166
Joined: Tue Jun 04, 2013 4:26 pm

Re: Very slow login (30s!) and slow boot on Linux Mint 17.1

Post by hpmc13 »

Wish I could help you, but I'm having the same problem with very similar times but on completely different hardware. I've sort of given up on a solution and learned to live with it.

What always strikes me is that I can load LM 17 in VirtualBox in about 20 seconds. I've always blamed the Nvidia drivers, but can't prove it.
Running LM 20 Cinnamon
riFlo

Re: Very slow login (30s!) and slow boot on Linux Mint 17.1

Post by riFlo »

Hi,
I thank you hpmc13 for your confirmation of this problem.
today i tried the points 2 and 3 of these instructions: http://community.linuxmint.com/tutorial/view/114
Disabling the hdd-check in /etc/fstab doesn't improve the boot time. So I changed it back to '1'. Changing 'quiet splash' in /etc/default/grub to 'profile' doesn't improve boot time as well. But now there were some 'failed' messages when bluetooth tries to start. Similar to the ones in the syslog-entries I showed in my first post. I also created a fresh new user with default desktop. But the login time is the same for it.
When I logout from a running cinnamon session and log into a new one, the login process is fast (about 7 seconds). But when I login after booting it takes the usual 30s or more.

Has somebody tested the tool e4rat (Improving Startup Times by Physical Block Reallocation) in combination with linux mint? : http://e4rat.sourceforge.net/
I also attached a typical bootchart.

http://s23.postimg.org/ezg2a0ct5/bootchart_20150210.png

Regards
riFlo
dudecorpch

Re: Very slow login (30s!) and slow boot on Linux Mint 17.1

Post by dudecorpch »

Same here on an IPC2, first session logins were blazing fast but after configuring my desktop a bit more I started to experience the same thing (>30s!). Sadly I don't have the skills to debug it :/
User avatar
Flemur
Level 20
Level 20
Posts: 10097
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Very slow login (30s!) and slow boot on Linux Mint 17.1

Post by Flemur »

Same here (I think); Mint 17 was booting in about 15-20 seconds from grub prompt to desktop, now (Mint 17.1) it takes about 30 sec. (Edit: 23 seconds, so not that terrible).

Most of that time difference is here (in dmesg):

Code: Select all

[    2.731229] random: nonblocking pool is initialized
[    8.216848] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    9.639940] systemd-udevd[406]: starting version 204
[    9.998121] lp: driver loaded but no devices found
Debian boots in 13-14 seconds.
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
hpmc13
Level 3
Level 3
Posts: 166
Joined: Tue Jun 04, 2013 4:26 pm

Re: Very slow login (30s!) and slow boot on Linux Mint 17.1

Post by hpmc13 »

hpmc13 wrote:I've always blamed the Nvidia drivers, but can't prove it.
It's not the NVidia drivers. I had occasion recently to remove the drivers and the login takes just as long as before. I'm pretty sure that I encrypted /home when I installed, and I'm wondering if that has anything to do with it.
Running LM 20 Cinnamon
Locked

Return to “Cinnamon”