[Solved] Slow Boot Time - Is K4.15.0-20 the cause?

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
Andre dsouza
Level 1
Level 1
Posts: 5
Joined: Thu Jul 11, 2019 8:40 am

[Solved] Slow Boot Time - Is K4.15.0-20 the cause?

Post by Andre dsouza » Thu Jul 11, 2019 8:46 am

I have a Dell Vostro 1510 and I have the same problem mentioned in thread Incredibly Slow Boot Time with New Mint 19 Installation (Solved).
I checked my kernel version and it is 4.15.0.20
Will updating my kernel to a newer one make my system boot up faster
My computer has a 64bit intel core 2duo and 2gb ram
The os runs silky smooth when booted up and is pretty fast
P.s. my computer also shows some errors when I shut it down :(
Last edited by karlchen on Sat Jul 13, 2019 10:35 am, edited 3 times in total.
Reason: Marked the thread as [Solved], because Andre confirmed the problem has been resolved in the post below: https://forums.linuxmint.com/viewtopic.php?f=46&t=297628#p1658101

User avatar
karlchen
Level 20
Level 20
Posts: 10859
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by karlchen » Thu Jul 11, 2019 11:33 am

Hello, Andre dsouza.

It is unlikely that you experience the same problem which was reported and solved in that old thread from 2018.
The cause in the old thread was precisely kernel 4.15.0-24, which was faulty and which had been withdrawn from the repos by Ubuntu.
This is not the same a kernel K4.15.0-20, which has never been reported as faulty and which has not been withdrawn.
Yet, it is definitely an outdated kernel. By now your system should be on K4.15.0-54.
Suggests that you do not apply available software updates in a timely fashion.

Please, open a terminal window. Execute the following commandlines. Post the complete text output which each commandline will display:

Code: Select all

inxi -Fxz

Code: Select all

systemd-analyze

Code: Select all

systemd-analyze blame
Please, also explain more precisely which error messages you read during shutdown.

Best regards,
Karl
Image
Linux Mint 18.1 64-bit Cinnamon Desktop, Total Commander 9.22a 64-bit
Ubuntu 18.04.2 32-bit Mate Desktop, Total Commander 9.22a 32-bit
Windows? - 1 window in every room

Andre dsouza
Level 1
Level 1
Posts: 5
Joined: Thu Jul 11, 2019 8:40 am

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by Andre dsouza » Fri Jul 12, 2019 12:11 pm

hi, karlchen

thanks for replying back so fast......, so anyways here are the results when i had run the following commands in the terminal
  • this one is for inxi -Fxz

    Code: Select all

    System:
      Host: andre-Vostro1510 Kernel: 4.15.0-20-generic x86_64 bits: 64 
      compiler: gcc v: 7.3.0 Desktop: Cinnamon 4.0.8 
      Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic 
    Machine:
      Type: Portable System: Dell product: Vostro1510 v: Null serial: <filter> 
      Mobo: Dell model: 0R780K serial: <filter> BIOS: Dell v: A15 
      date: 03/18/2009 
    Battery:
      ID-1: BAT1 charge: 27.1 Wh condition: 46.1/48.8 Wh (94%) model: Dell 
      status: Charging 
    CPU:
      Topology: Dual Core model: Intel Core2 Duo T5670 bits: 64 type: MCP 
      arch: Core Merom rev: D L2 cache: 2048 KiB 
      flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7182 
      Speed: 798 MHz min/max: 800/1801 MHz Core speeds (MHz): 1: 798 2: 798 
    Graphics:
      Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Dell 
      driver: i915 v: kernel bus ID: 00:02.0 
      Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
      resolution: 1280x800~60Hz 
      OpenGL: renderer: Mesa DRI Intel 965GM v: 2.1 Mesa 18.0.5 
      direct render: Yes 
    Audio:
      Device-1: Intel 82801H HD Audio vendor: Dell driver: snd_hda_intel 
      v: kernel bus ID: 00:1b.0 
      Sound Server: ALSA v: k4.15.0-20-generic 
    Network:
      Device-1: Broadcom Limited BCM4321 802.11a/b/g/n 
      vendor: Dell Wireless 1500 Draft 802.11n WLAN Mini-card driver: wl 
      v: kernel port: 1c20 bus ID: 06:00.0 
      IF: wlp6s0 state: up mac: <filter> 
      Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
      vendor: Dell driver: r8169 v: 2.3LK-NAPI port: 5000 bus ID: 07:00.0 
      IF: enp7s0 state: down mac: <filter> 
    Drives:
      Local Storage: total: 465.76 GiB used: 9.38 GiB (2.0%) 
      ID-1: /dev/sda vendor: Western Digital model: WD5000BPVT-55HXZT3 
      size: 465.76 GiB 
    Partition:
      ID-1: / size: 457.45 GiB used: 9.38 GiB (2.0%) fs: ext4 dev: /dev/sda1 
    Sensors:
      System Temperatures: cpu: 51.0 C mobo: N/A 
      Fan Speeds (RPM): cpu: 0 
    Info:
      Processes: 173 Uptime: 8m Memory: 1.94 GiB used: 646.3 MiB (32.6%) 
      Init: systemd runlevel: 5 Compilers: gcc: 7.3.0 Shell: bash v: 4.4.19 
      inxi: 3.0.27
  • this one is for systemd-analyze

    Code: Select all

    Startup finished in 2min 8.776s (kernel) + 34.608s (userspace) = 2min 43.385s
    graphical.target reached after 34.594s in userspace
  • and this one is for systemd-analyze blame

    Code: Select all

    31.038s colord.service
             23.255s dev-sda1.device
             15.290s snapd.service
             13.901s systemd-journal-flush.service
              9.750s udisks2.service
              9.575s apparmor.service
              9.164s networkd-dispatcher.service
              8.986s NetworkManager.service
              8.634s ModemManager.service
              8.582s accounts-daemon.service
              7.901s ubuntu-system-adjustments.service
              7.374s thermald.service
              7.110s systemd-udevd.service
              6.647s grub-common.service
              6.465s apport.service
              6.462s avahi-daemon.service
              6.076s wpa_supplicant.service
              5.782s dns-clean.service
              5.672s lm-sensors.service
              5.471s plymouth-read-write.service
              5.154s snap-gnome\x2d3\x2d28\x2d1804-67.mount
              5.143s console-setup.service
              5.068s snap-chromium-784.mount
              4.967s snap-core-7270.mount
              4.888s snap-gtk\x2dcommon\x2dthemes-1313.mount
              4.766s snap-spotify-35.mount
              4.760s snap-core18-1055.mount
              4.585s snap-snap\x2dstore-171.mount
              3.402s dev-loop6.device
              2.998s dev-loop5.device
              2.961s dev-loop2.device
              2.799s keyboard-setup.service
              2.655s dev-loop1.device
              2.582s dev-loop4.device
              2.498s dev-loop3.device
              2.457s systemd-modules-load.service
              2.186s dev-loop0.device
              2.014s lvm2-monitor.service
              1.802s upower.service
              1.510s lightdm.service
              1.508s plymouth-quit-wait.service
              1.485s polkit.service
              1.207s speech-dispatcher.service
              1.192s kerneloops.service
              1.179s rsyslog.service
              1.145s pppd-dns.service
              1.144s gpu-manager.service
               928ms systemd-tmpfiles-setup-dev.service
               845ms setvtrgb.service
               776ms systemd-logind.service
               717ms networking.service
               688ms systemd-journald.service
               617ms kmod-static-nodes.service
               611ms swapfile.swap
               556ms systemd-random-seed.service
               492ms plymouth-start.service
               426ms hddtemp.service
               424ms packagekit.service
               405ms systemd-tmpfiles-clean.service
               388ms alsa-restore.service
               383ms systemd-tmpfiles-setup.service
               347ms dev-hugepages.mount
               330ms systemd-rfkill.service
               324ms systemd-udev-trigger.service
               322ms blk-availability.service
               309ms user@1000.service
               298ms systemd-sysctl.service
               292ms rtkit-daemon.service
               281ms dev-mqueue.mount
               278ms sys-kernel-debug.mount
               255ms systemd-remount-fs.service
               232ms systemd-resolved.service
               200ms systemd-timesyncd.service
               145ms systemd-update-utmp.service
                89ms systemd-backlight@backlight:acpi_video0.service
                62ms snapd.seeded.service
                40ms ufw.service
                15ms ureadahead-stop.service
                11ms systemd-update-utmp-runlevel.service
                 9ms systemd-user-sessions.service
                 9ms sys-fs-fuse-connections.mount
                 6ms sys-kernel-config.mount
                 5ms snapd.socket
                 3ms openvpn.service
I also got 1 of the 3 errors, I couldn't get the others because the system shuts down too quickly
Here is one of the errors

Code: Select all

[ 450.204320] [DRM:drm_atomic_helper_wait_for_flip_down [drm_(something I couldn't read)_helper]] *error* [CRTC:41:pipe B] flip_done timed out
This is all I know, please do find a solution to this problem
Regards,
Andre D'souza

User avatar
karlchen
Level 20
Level 20
Posts: 10859
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by karlchen » Fri Jul 12, 2019 3:53 pm

Hello, Andre.

Thank you for executing the 3 commandlines and posting their output.
Pooh. The timespan needed to load the kernel is extremely long. Never read such a timespan for kernel loading.
It should be around 9 to 10 seconds on a spinning harddisk (as opposed to an SSD).
But in fact, kernel loading takes about 2 minutes and 9 seconds.

Code: Select all

systemd-analyze

Startup finished in 2min 8.776s (kernel) + 34.608s (userspace) = 2min 43.385s
graphical.target reached after 34.594s in userspace
In order to investigate this time further, it will be necessary to inspect the system logs with the help of the command journalctl.

Doing so and posting the result is a bit tricky, because journalctl is extremely verbose. The output will be too long to insert it into a post directly.

Please, find the steps below how to
+ execute journalctl
+ catch the output in a text file
+ compress the text file using gzip
+ attach the gzipped text file to your next reply, please.

How to provide your journalctl output to us for inspection:
  • Open a terminal window.
  • Execute the following commandline, please:

    Code: Select all

    journalctl --no-pager -b 0 > journalctl_andre.txt
    This command will write the whole current system log to the file journalctl_andre.txt. The file will be located in your $HOME directory (very likely /home/andre).
  • Now gzip the file journalctl_andre.txt by executing the commandline:

    Code: Select all

    gzip journalctl_andre.txt
    The resulting .gz file will be named journalctl_andre.txt.gz.
  • Attach this file to your next reply, please.
If we are lucky the systemlog will put us on the right track. Hopefully.

Regards,
Karl
Image
Linux Mint 18.1 64-bit Cinnamon Desktop, Total Commander 9.22a 64-bit
Ubuntu 18.04.2 32-bit Mate Desktop, Total Commander 9.22a 32-bit
Windows? - 1 window in every room

Andre dsouza
Level 1
Level 1
Posts: 5
Joined: Thu Jul 11, 2019 8:40 am

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by Andre dsouza » Sat Jul 13, 2019 2:34 am

Hi karlchen
I ran the following commands in the terminal...
Here are the results
Hope you find a solution to this problem
journalctl_andre.txt.gz
(33.28 KiB) Downloaded 6 times
Regards,
Andre

User avatar
Larry78723
Level 5
Level 5
Posts: 727
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by Larry78723 » Sat Jul 13, 2019 6:52 am

Andre and Karl,

The following block of code repeats numerous time in Andre's journalctl:

Code: Select all

Jul 13 11:45:32 andre-Vostro1510 kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe A] flip_done timed out
Jul 13 11:45:32 andre-Vostro1510 kernel: ------------[ cut here ]------------
Jul 13 11:45:32 andre-Vostro1510 kernel: vblank wait timed out on crtc 0
Jul 13 11:45:32 andre-Vostro1510 kernel: WARNING: CPU: 0 PID: 187 at /build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x181/0x190 [drm]
Jul 13 11:45:32 andre-Vostro1510 kernel: Modules linked in: i915 psmouse i2c_i801 ahci libahci firewire_ohci i2c_algo_bit sdhci_pci pata_acpi sdhci firewire_core drm_kms_helper crc_itu_t syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops mii drm wmi video
Jul 13 11:45:32 andre-Vostro1510 kernel: CPU: 0 PID: 187 Comm: kworker/u4:5 Not tainted 4.15.0-20-generic #21-Ubuntu
Jul 13 11:45:32 andre-Vostro1510 kernel: Hardware name: Dell Inc. Vostro1510/0R780K, BIOS A15 03/18/2009
Jul 13 11:45:32 andre-Vostro1510 kernel: Workqueue: events_unbound async_run_entry_fn
Jul 13 11:45:32 andre-Vostro1510 kernel: RIP: 0010:drm_wait_one_vblank+0x181/0x190 [drm]
Jul 13 11:45:32 andre-Vostro1510 kernel: RSP: 0018:ffffbbbd4060ba00 EFLAGS: 00010286
Jul 13 11:45:32 andre-Vostro1510 kernel: RAX: 0000000000000000 RBX: ffff9663b3cd0000 RCX: ffffffff90c628a8
Jul 13 11:45:32 andre-Vostro1510 kernel: RDX: 0000000000000001 RSI: 0000000000000082 RDI: 0000000000000247
Jul 13 11:45:32 andre-Vostro1510 kernel: RBP: ffffbbbd4060ba58 R08: 0000000000000001 R09: 00000000000002e4
Jul 13 11:45:32 andre-Vostro1510 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Jul 13 11:45:32 andre-Vostro1510 kernel: R13: 0000000000000000 R14: 0000000001000001 R15: ffff9663b394f008
Jul 13 11:45:32 andre-Vostro1510 kernel: FS:  0000000000000000(0000) GS:ffff9663ff400000(0000) knlGS:0000000000000000
Jul 13 11:45:32 andre-Vostro1510 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 13 11:45:32 andre-Vostro1510 kernel: CR2: 00007ffd890de0d0 CR3: 000000001de0a000 CR4: 00000000000006f0
Jul 13 11:45:32 andre-Vostro1510 kernel: Call Trace:
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? wait_woken+0x80/0x80
Jul 13 11:45:32 andre-Vostro1510 kernel:  intel_get_load_detect_pipe+0x5b7/0x620 [i915]
Jul 13 11:45:32 andre-Vostro1510 kernel:  intel_tv_detect+0x147/0x510 [i915]
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? drm_get_edid+0xe8/0x3d0 [drm]
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? drm_get_edid+0xe8/0x3d0 [drm]
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? __ww_mutex_lock_slowpath+0x16/0x20
Jul 13 11:45:32 andre-Vostro1510 kernel:  drm_helper_probe_detect+0x50/0x90 [drm_kms_helper]
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? drm_helper_probe_detect+0x50/0x90 [drm_kms_helper]
Jul 13 11:45:32 andre-Vostro1510 kernel:  drm_helper_probe_single_connector_modes+0xe2/0x710 [drm_kms_helper]
Jul 13 11:45:32 andre-Vostro1510 kernel:  drm_setup_crtcs+0x13f/0xa30 [drm_kms_helper]
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? resched_curr+0x5d/0xc0
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? check_preempt_wakeup+0x130/0x240
Jul 13 11:45:32 andre-Vostro1510 kernel:  __drm_fb_helper_initial_config_and_unlock+0x41/0x400 [drm_kms_helper]
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? ttwu_do_activate+0x7a/0x90
Jul 13 11:45:32 andre-Vostro1510 kernel:  drm_fb_helper_initial_config+0x35/0x40 [drm_kms_helper]
Jul 13 11:45:32 andre-Vostro1510 kernel:  intel_fbdev_initial_config+0x18/0x30 [i915]
Jul 13 11:45:32 andre-Vostro1510 kernel:  async_run_entry_fn+0x3c/0x150
Jul 13 11:45:32 andre-Vostro1510 kernel:  process_one_work+0x1de/0x410
Jul 13 11:45:32 andre-Vostro1510 kernel:  worker_thread+0x32/0x410
Jul 13 11:45:32 andre-Vostro1510 kernel:  kthread+0x121/0x140
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? process_one_work+0x410/0x410
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? do_syscall_64+0x73/0x130
Jul 13 11:45:32 andre-Vostro1510 kernel:  ? SyS_exit_group+0x14/0x20
Jul 13 11:45:32 andre-Vostro1510 kernel:  ret_from_fork+0x35/0x40
Jul 13 11:45:32 andre-Vostro1510 kernel: Code: ff ff e8 a3 33 66 cf 48 8d 75 a8 4c 89 ff e8 97 94 6a cf 45 85 ed 0f 85 ff fe ff ff 44 89 e6 48 c7 c7 10 74 24 c0 e8 df 30 66 cf <0f> 0b e9 e9 fe ff ff 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 
Jul 13 11:45:32 andre-Vostro1510 kernel: ---[ end trace ef6a06defb265b9a ]---
Could this be causing the long kernal boot?
Image

User avatar
smurphos
Level 11
Level 11
Posts: 3732
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by smurphos » Sat Jul 13, 2019 7:17 am

This is the problem

Code: Select all

Graphics:
  Device-1: Intel Mobile GM965/GL960 Integrated Graphics
This is the solution - viewtopic.php?p=1605180#p1605180
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.

User avatar
karlchen
Level 20
Level 20
Posts: 10859
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by karlchen » Sat Jul 13, 2019 8:15 am

To Larry78723 and smurphos: Great catch, I'd say. :D
Hoping that the linked solution will resolve the problem for Andre as well ...
Image
Linux Mint 18.1 64-bit Cinnamon Desktop, Total Commander 9.22a 64-bit
Ubuntu 18.04.2 32-bit Mate Desktop, Total Commander 9.22a 32-bit
Windows? - 1 window in every room

Andre dsouza
Level 1
Level 1
Posts: 5
Joined: Thu Jul 11, 2019 8:40 am

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by Andre dsouza » Sat Jul 13, 2019 8:24 am

hi larry, smurphos and karlchen
thanks for all the help, the post posted by smurphos solved my problem. thanks to everyone here for being so helpful. Now my boot time is a lot faster :D :D :) :) :o :o
regards
Andre

User avatar
Larry78723
Level 5
Level 5
Posts: 727
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Slow Boot Time - Is K4.15.0-20 the cause?

Post by Larry78723 » Sat Jul 13, 2019 8:28 am

Glad to hear that Smurpos' link worked for you. Enjoy your faster boot times. Please change the subject of the original post and add [SOLVED] to it.
Image

Andre dsouza
Level 1
Level 1
Posts: 5
Joined: Thu Jul 11, 2019 8:40 am

Re: [Solved] Slow Boot Time - Is K4.15.0-20 the cause?

Post by Andre dsouza » Sun Jul 14, 2019 5:53 am

Hi everyone
Now that I have solved the problem, is it advisable to install a newer kernel as suggested by karlchen (4.15.0-54) :?:

DAMIEN1307
Level 7
Level 7
Posts: 1805
Joined: Tue Feb 21, 2017 8:13 pm
Location: Alamogordo, New Mexico, USA

Re: [Solved] Slow Boot Time - Is K4.15.0-20 the cause?

Post by DAMIEN1307 » Sun Jul 14, 2019 7:59 am

Now that I have solved the problem, is it advisable to install a newer kernel as suggested by karlchen (4.15.0-54) :?:
YES!, When new kernels become available within the LTS series of kernels, (Long Term Support), such as the 4.15.0-xx series is for your LM 19.1 Tessa base,
what happens here is that the newest kernel within the series updates the kernel within that series and contains fixes for "bugs" as well as any "security" updates necessary in that series...this is how and why Linux OSs are inherently much more secure than either Mac or Windows OSs...DAMIEN

PS...keep in mind that karlchen is not only a moderator for the LM forums but has experience with LM OSs since at least Sat Dec 31, 2011.
ORDO AB CHAO

Post Reply

Return to “Installation & Boot”