Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799470 Title: slow boot in kubuntu 18.04 Status in linux package in Ubuntu: Incomplete Bug description: I have the bug with the Kubuntu 18.04 sb_release -rd: Description: Ubuntu 18.04.1 LTS Release: 18.04 Before, i was using the 16 (LTS) version and the boot was quick. I have first try un update and i have the problem, with a fresh install, i have also the same problem. In the boot, i have a long time (33s) without message and action In this extract of the dmesg, you can see the 33 seconds without messages [ 5.434266] sdc: sdc1 sdc2 [ 5.434268] sd 11:0:0:0: [sdd] 537234768 512-byte logical blocks: (275 GB/256 GiB) [ 5.434288] sd 11:0:0:0: [sdd] Write Protect is off [ 5.434290] sd 11:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [ 5.434312] sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.434404] ata12.00: Enabling discard_zeroes_data [ 5.434436] sd 5:0:0:0: [sdc] Attached SCSI disk [ 5.435541] sdd: sdd1 sdd2 [ 5.435661] ata12.00: Enabling discard_zeroes_data [ 5.435893] sd 11:0:0:0: [sdd] supports TCG Opal [ 5.435895] sd 11:0:0:0: [sdd] Attached SCSI disk [ 38.317233] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 38.439463] ip_tables: (C) 2000-2006 Netfilter Core Team [ 38.548456] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 38.568547] systemd[1]: Detected architecture x86-64. [ 38.572697] systemd[1]: Set hostname to <lune>. [ 38.649301] systemd[1]: Created slice User and Session Slice. [ 38.649610] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 38.649680] systemd[1]: Created slice System Slice. [ 38.649716] systemd[1]: Listening on fsck to fsckd communication Socket. [ 38.649740] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 38.649760] systemd[1]: Listening on udev Kernel Socket. [ 38.649768] systemd[1]: Reached target Slices. [ 38.667706] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro With the command sudo systemd-analyze time [sudo] Mot de passe de jacky : Startup finished in 12.351s (firmware) + 11.414s (loader) + 38.418s (kernel) + 1.902s (userspace) = 1min 4.086s graphical.target reached after 1.898s in userspace You can see the 38 seconds in the kernel mode In the blame, there is any long action sudo systemd-analyze blame 352ms disk-tera.mount 321ms NetworkManager.service 273ms dev-mapper-kubuntu\x2d\x2dvg\x2droot.device 264ms udisks2.service 236ms networkd-dispatcher.service 234ms snapd.service 201ms systemd-logind.service 196ms mpd.service 192ms ModemManager.service 170ms disk-sdb.mount 157ms systemd-timesyncd.service 132ms systemd-resolved.service 130ms accounts-daemon.service 84ms thermald.service 79ms alsa-restore.service 76ms pppd-dns.service 74ms keyboard-setup.service 74ms plymouth-quit.service 71ms systemd-journal-flush.service 68ms wpa_supplicant.service 61ms lvm2-pvscan@8:50.service 58ms gpu-manager.service 57ms colord.service 56ms systemd-udev-trigger.service 53ms systemd-udevd.service 52ms upower.service 51ms packagekit.service 49ms lvm2-monitor.service 49ms apparmor.service 46ms rsyslog.service 44ms user@119.service 42ms systemd-journald.service 41ms grub-common.service 39ms polkit.service 27ms systemd-modules-load.service 27ms plymouth-start.service 26ms user@1000.service 26ms apport.service 23ms systemd-tmpfiles-setup-dev.service 21ms avahi-daemon.service 17ms systemd-remount-fs.service 14ms plymouth-read-write.service 14ms sys-kernel-debug.mount 12ms dev-mqueue.mount 11ms systemd-tmpfiles-clean.service 11ms systemd-tmpfiles-setup.service 10ms dev-hugepages.mount 9ms lvm2-pvscan@8:34.service 9ms systemd-sysctl.service 8ms kerneloops.service 8ms ufw.service 8ms blk-availability.service 8ms snapd.seeded.service 7ms systemd-random-seed.service 6ms kmod-static-nodes.service 5ms ureadahead-stop.service 4ms systemd-update-utmp.service 4ms rtkit-daemon.service 4ms dev-mapper-kubuntu\x2d\x2dvg\x2dswap_1.swap 3ms systemd-user-sessions.service 2ms systemd-update-utmp-runlevel.service 2ms console-setup.service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jacky 1399 F.... pulseaudio /dev/snd/controlC1: jacky 1399 F.... pulseaudio CurrentDesktop: KDE Date: Tue Oct 23 15:50:11 2018 HibernationDevice: RESUME=UUID=6e57e929-ea31-4512-9599-1ceb93a37576 InstallationDate: Installed on 2018-10-07 (16 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lo no wireless extensions. enp8s0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. A320MA-M.2 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: A320MA-M.2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnA320MA-M.2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320MA-M.2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320MA-M.2 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
