Долгая загрузка

Здесь можно задавать любые вопросы по установке и настройке Lubuntu Linux

Модератор: Vadim

Ответить

Автор темы
k25neo
Сообщения: 1
Зарегистрирован: 19 сен 2019, 21:23

Долгая загрузка

#1

Сообщение k25neo » 19 сен 2019, 21:31

Добрый день. После обновления и установки драйверов стала долго запускаться система на ssd. До этого включалась очень быстро.
В линуксе плохо разбираюсь. Помогите разобраться.

Код: Выделить всё

systemd-analyze blame
          6.608s NetworkManager-wait-online.service
          1.872s dev-sda1.device
          1.186s snapd.service
          1.026s apport.service
           845ms grub-common.service
           748ms networkd-dispatcher.service
           745ms systemd-logind.service
           680ms udisks2.service
           659ms systemd-journal-flush.service
           658ms accounts-daemon.service
           631ms ModemManager.service
           577ms systemd-resolved.service
           548ms avahi-daemon.service
           493ms systemd-timesyncd.service
           476ms plymouth-quit.service
           475ms systemd-journald.service
           475ms dev-loop1.device
           463ms dev-loop2.device
           456ms dev-loop5.device
           452ms rsyslog.service
           434ms dev-loop4.device
           424ms dev-loop0.device
           396ms dev-loop3.device
           338ms NetworkManager.service
           319ms ofono.service
           308ms zram-config.service
           297ms wpa_supplicant.service
           286ms pppd-dns.service
           261ms thermald.service
           194ms apparmor.service
           191ms gpu-manager.service
           157ms keyboard-setup.service
           147ms systemd-modules-load.service
           137ms snap-core18-1144.mount
           136ms snap-snapd-4022.mount
           135ms snap-kde\x2dframeworks\x2d5\x2dcore18-30.mount
           132ms snap-kde\x2dframeworks\x2d5\x2dcore18-32.mount
           122ms upower.service
           105ms polkit.service
            95ms snap-core18-1098.mount
            93ms snap-snapd-4605.mount
            86ms systemd-udev-trigger.service
            82ms plymouth-read-write.service
            79ms plymouth-start.service
            74ms user@1000.service
            72ms lvm2-monitor.service
            69ms zram-setup@zram1.service
            61ms systemd-udevd.service
            60ms zram-setup@zram0.service
            52ms zram-setup@zram2.service
            50ms dev-zram1.device
            47ms zram-setup@zram3.service
            45ms systemd-tmpfiles-clean.service
            44ms dev-zram3.device
            43ms systemd-sysusers.service
            41ms systemd-tmpfiles-setup.service
            39ms sys-fs-fuse-connections.mount
            39ms systemd-sysctl.service
            38ms dev-zram0.device
            36ms snapd.seeded.service
            33ms snapd.socket
            30ms dev-zram2.device
            26ms console-setup.service
            26ms systemd-update-utmp.service
            24ms bluetooth.service
            22ms tmp.mount
            22ms ufw.service
            22ms blk-availability.service
            21ms dev-mqueue.mount
            21ms grub-initrd-fallback.service
            21ms setvtrgb.service
            20ms kerneloops.service
            19ms kmod-static-nodes.service
            18ms user-runtime-dir@1000.service
            18ms systemd-tmpfiles-setup-dev.service
            18ms sys-kernel-debug.mount
            17ms systemd-remount-fs.service
            17ms systemd-user-sessions.service
            13ms rtkit-daemon.service
            11ms nvidia-persistenced.service
            10ms systemd-random-seed.service
             9ms dev-hugepages.mount
             7ms sys-kernel-config.mount
             7ms systemd-update-utmp-runlevel.service
             6ms sddm.service

Код: Выделить всё

dev@dev-pc:~$ dmesg -l err,Warn
[    0.131342] APIC calibration not consistent with PM-Timer: 120ms instead of 100ms
[    0.171593] pmd_set_huge: Cannot satisfy [mem 0xf0000000-0xf0200000] with a huge-page mapping due to MTRR override.
[    0.182488] pci 0000:00:01.0: ASPM: current common clock configuration is broken, reconfiguring
[    1.316306] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    1.316308] platform eisa.0: Cannot allocate resource for EISA slot 1
[    1.316309] platform eisa.0: Cannot allocate resource for EISA slot 2
[    1.316310] platform eisa.0: Cannot allocate resource for EISA slot 3
[    1.316311] platform eisa.0: Cannot allocate resource for EISA slot 4
[    1.316312] platform eisa.0: Cannot allocate resource for EISA slot 5
[    1.316313] platform eisa.0: Cannot allocate resource for EISA slot 6
[    1.316315] platform eisa.0: Cannot allocate resource for EISA slot 7
[    1.316316] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.612528] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000084F (\PMRG) (20181213/utaddress-213)
[    1.612537] ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x00000000000004AF (\GPR2) (20181213/utaddress-213)
[    1.612567] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    1.658678] nvidia: loading out-of-tree module taints kernel.
[    1.658690] nvidia: module license 'NVIDIA' taints kernel.
[    1.658690] Disabling lock debugging due to kernel taint
[    1.782756] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 CDT 2019
[   35.585250] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
[   35.859737] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000dffff window]
[   35.860178] caller os_map_kernel_space.part.10+0x84/0x90 [nvidia] mapping multiple BARs
[   38.601592] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000dffff window]
[   38.602007] caller os_map_kernel_space.part.10+0x84/0x90 [nvidia] mapping multiple BARs
[   41.780623] kauditd_printk_skb: 16 callbacks suppressed

Код: Выделить всё

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 @9.566s
└─multi-user.target @9.566s
  └─kerneloops.service @9.545s +20ms
    └─network-online.target @9.543s
      └─NetworkManager-wait-online.service @2.933s +6.608s
        └─NetworkManager.service @2.529s +338ms
          └─dbus.service @2.516s
            └─basic.target @2.296s
              └─sockets.target @2.296s
                └─snapd.socket @2.254s +33ms
                  └─sysinit.target @2.193s
                    └─systemd-timesyncd.service @1.700s +493ms
                      └─systemd-tmpfiles-setup.service @1.644s +41ms
                        └─systemd-journal-flush.service @890ms +659ms
                          └─systemd-journald.service @311ms +475ms
                            └─systemd-journald-dev-log.socket @309ms
                              └─system.slice @288ms
                                └─-.slice @288ms

Код: Выделить всё

systemd-analyze
Startup finished in 34.575s (kernel) + 9.579s (userspace) = 44.155s 
graphical.target reached after 9.566s in userspace

Код: Выделить всё

blkid
/dev/sda1: UUID="aad08f13-bede-4010-a679-b87a67ce156d" TYPE="ext4" PARTUUID="3818d132-01"

Код: Выделить всё

cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=aad08f13-bede-4010-a679-b87a67ce156d /              ext4    defaults,discard 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0


ВикторА
Сообщения: 470
Зарегистрирован: 06 ноя 2011, 11:10

Re: Долгая загрузка

#2

Сообщение ВикторА » 21 сен 2019, 13:05

А с дисками никаких операций не производили? (отключение-подключение...) Система изначально устанавливалась как на основной диск?
Раздел /home в файле fstab не указан потому, что вся система на одном разделе?

У меня для раздела / стоят настройки : / ext4 errors=remount-ro 0 1

а у вас по умолчанию, как для /home...

Аватара пользователя

denkin
Сообщения: 1968
Зарегистрирован: 07 сен 2011, 17:21

Re: Долгая загрузка

#3

Сообщение denkin » 22 сен 2019, 01:30

У меня так,
корень:
UUID=376fc080-f182-4fef-b1c3-2b23e30fea6c / ext4 errors=remount-ro 0
домашний:
UUID=ad064de1-546a-472b-b65c-c2426128bcfb /home ext4 defaults 0


MikeRM
Сообщения: 64
Зарегистрирован: 19 окт 2018, 19:53

Re: Долгая загрузка

#4

Сообщение MikeRM » 22 сен 2019, 13:58

Проблема тут:
k25neo писал(а):
19 сен 2019, 21:31
[ 1.782756] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019
[ 35.585250]
Проверить можно отключив модули NVIDIA при загрузке добавив в /etc/default/grub для параметра GRUB_CMDLINE_LINUX_DEFAULT следующую опцию

Код: Выделить всё

module_blacklist=nvidia,nvidia-current,nvidia_drm,nvidia_uvm,nvidia_modeset,nouveau
Но самой проблемы это не решит. Нужно пробовать разный версии драйверов: постарее-поновее, свободные-проприетарные. Я в NVIDIA не очень хорошо разбираюсь.


MikeRM
Сообщения: 64
Зарегистрирован: 19 окт 2018, 19:53

Re: Долгая загрузка

#5

Сообщение MikeRM » 22 сен 2019, 14:01

А пардон, не увидел что:
k25neo писал(а):
19 сен 2019, 21:31
dmesg -l err,Warn
Выложите полный dmesg. Тогда увидим кто ест 30 секунд при загрузке.


JohnDoe_71Rus
Сообщения: 264
Зарегистрирован: 05 сен 2011, 15:09

Re: Долгая загрузка

#6

Сообщение JohnDoe_71Rus » 29 сен 2019, 08:07

позвольте присоединиться к проблеме. После таймера груб система что-то ждет секунд 30 и только потом появляется активность диска. Общая загрузка со входом пользователя около 2 минут.

Код: Выделить всё

~$ systemd-analyze blame
         30.872s apt-daily.service
         11.306s systemd-journal-flush.service
          7.222s apparmor.service
          5.600s apt-daily-upgrade.service
          5.074s binfmt-support.service
          4.863s console-setup.service
          4.713s dev-sda11.device
          4.573s qemu-kvm.service
          4.510s dns-clean.service
          3.190s snapd.service
          2.979s NetworkManager-wait-online.service
          2.923s timidity.service
          2.907s NetworkManager.service
          2.789s networkd-dispatcher.service
          2.496s motd-news.service
          2.359s udisks2.service
          2.055s accounts-daemon.service
          2.048s ModemManager.service
          1.906s thermald.service
          1.875s systemd-rfkill.service
          1.664s systemd-fsck@dev-disk-by\x2duuid-90a11bb6\x2d6482\x2d496c\x2d9216\x2d62bb8ad6a767.service
          1.603s home.mount
          1.520s rsyslog.service
          1.484s systemd-fsck@dev-disk-by\x2duuid-4784df5c\x2d6201\x2d4df0\x2da9ac\x2d7d103123023d.service
          1.122s media-DRIVE\x20L.mount
          1.038s wpa_supplicant.service
          1.007s grub-common.service
           890ms alsa-restore.service
           882ms var.mount
           867ms nmbd.service
           619ms systemd-modules-load.service
           572ms lm-sensors.service
           561ms systemd-udevd.service
           496ms keyboard-setup.service
           478ms apport.service
           478ms console-kit-log-system-start.service
           464ms gpu-manager.service
           451ms systemd-tmpfiles-setup-dev.service
           426ms hddtemp.service
           395ms systemd-sysctl.service
           382ms systemd-tmpfiles-setup.service
           377ms dev-disk-by\x2duuid-900aebe2\x2ddda7\x2d41a1\x2d81b6\x2d44bc755bec60.swap
           367ms networking.service
           347ms systemd-random-seed.service
           335ms smbd.service
           270ms media-DRIVE\x20J.mount
           255ms bluetooth.service
           252ms systemd-udev-trigger.service
           238ms systemd-timesyncd.service
         30.872s apt-daily.service
         11.306s systemd-journal-flush.service
          7.222s apparmor.service
          5.600s apt-daily-upgrade.service
          5.074s binfmt-support.service
          4.863s console-setup.service
          4.713s dev-sda11.device
          4.573s qemu-kvm.service
          4.510s dns-clean.service
          3.190s snapd.service
          2.979s NetworkManager-wait-online.service
          2.923s timidity.service
          2.907s NetworkManager.service
          2.789s networkd-dispatcher.service
          2.496s motd-news.service
          2.359s udisks2.service
          2.055s accounts-daemon.service
          2.048s ModemManager.service
          1.906s thermald.service
          1.875s systemd-rfkill.service
          1.664s systemd-fsck@dev-disk-by\x2duuid-90a11bb6\x2d6482\x2d496c\x2d9216\x2d62bb8ad6a767.service
          1.603s home.mount
          1.520s rsyslog.service
          1.484s systemd-fsck@dev-disk-by\x2duuid-4784df5c\x2d6201\x2d4df0\x2da9ac\x2d7d103123023d.service
          1.122s media-DRIVE\x20L.mount
          1.038s wpa_supplicant.service
          1.007s grub-common.service
           890ms alsa-restore.service
           882ms var.mount
           867ms nmbd.service
           619ms systemd-modules-load.service
           572ms lm-sensors.service
           561ms systemd-udevd.service
           496ms keyboard-setup.service
           478ms apport.service
           478ms console-kit-log-system-start.service
           464ms gpu-manager.service
           451ms systemd-tmpfiles-setup-dev.service
           426ms hddtemp.service
           395ms systemd-sysctl.service
           382ms systemd-tmpfiles-setup.service
           377ms dev-disk-by\x2duuid-900aebe2\x2ddda7\x2d41a1\x2d81b6\x2d44bc755bec60.swap
           367ms networking.service
           347ms systemd-random-seed.service
           335ms smbd.service
           270ms media-DRIVE\x20J.mount
           255ms bluetooth.service
           252ms systemd-udev-trigger.service
           238ms systemd-timesyncd.service
           232ms systemd-resolved.service
           229ms systemd-logind.service
           211ms kmod-static-nodes.service
           209ms lightdm.service
           201ms plymouth-quit-wait.service
           190ms systemd-journald.service
           184ms polkit.service
           137ms user@1000.service
            80ms ufw.service
            79ms dev-mqueue.mount
            78ms sys-kernel-debug.mount
            76ms plymouth-start.service
            45ms systemd-remount-fs.service
            34ms setvtrgb.service
            25ms systemd-update-utmp.service
            23ms pppd-dns.service
            22ms snapd.seeded.service
            14ms ureadahead-stop.service
            12ms rtkit-daemon.service
            12ms plymouth-read-write.service
            11ms systemd-update-utmp-runlevel.service
            10ms resolvconf-pull-resolved.service
             8ms avahi-daemon.service
             7ms proc-sys-fs-binfmt_misc.mount
             6ms dev-hugepages.mount
             5ms systemd-user-sessions.service
             4ms resolvconf.service
             4ms sys-kernel-config.mount
             3ms sys-fs-fuse-connections.mount
             1ms snapd.socket

Код: Выделить всё

~$ dmesg -l err,Warn
[    0.000000] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20170831/tbfadt-658)
[    0.160000]  #2
[    0.160132]  #3
[    1.564836] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564845] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564852] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564858] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564864] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564870] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564875] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564881] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564887] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564893] xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564899] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564905] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564910] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564916] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564921] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564927] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564932] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564938] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[    1.564943] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0010 address=0x00000000be102880 flags=0x0000]
[   11.564749] xhci_hcd 0000:02:00.0: can't setup: -110
[   11.564842] xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110
[   11.564892] xhci_hcd: probe of 0000:02:00.0 failed with error -110
[   12.770538] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
[   28.259485] CRAT table not found
[   28.260918] amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
[   29.725383] FAT-fs (sda9): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   29.991150] FAT-fs (sda9): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   40.687370] kauditd_printk_skb: 492 callbacks suppressed


JohnDoe_71Rus
Сообщения: 264
Зарегистрирован: 05 сен 2011, 15:09

Re: Долгая загрузка

#7

Сообщение JohnDoe_71Rus » 29 сен 2019, 08:08

Код: Выделить всё

~$ 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 @28.388s
└─multi-user.target @28.388s
  └─smbd.service @28.052s +335ms
    └─nmbd.service @27.181s +867ms
      └─network-online.target @27.179s
        └─NetworkManager-wait-online.service @24.198s +2.979s
          └─NetworkManager.service @21.289s +2.907s
            └─dbus.service @20.945s
              └─basic.target @20.927s
                └─sockets.target @20.927s
                  └─snapd.socket @20.925s +1ms
                    └─sysinit.target @20.891s
                      └─systemd-timesyncd.service @20.651s +238ms
                        └─systemd-tmpfiles-setup.service @20.252s +382ms
                          └─systemd-journal-flush.service @8.944s +11.306s
                            └─var.mount @8.059s +882ms
                              └─systemd-fsck@dev-disk-by\x2duuid-4784df5c\x2d6201\x2d4df0\x2da9ac\x2d7d103123023d.service @6.574s +1.484s
                                └─dev-disk-by\x2duuid-4784df5c\x2d6201\x2d4df0\x2da9ac\x2d7d103123023d.device @6.573s

Код: Выделить всё

~$ systemd-analyze
Startup finished in 23.201s (kernel) + 29.680s (userspace) = 52.882s
graphical.target reached after 28.388s in userspace
Проводил апгрейд mainboard и видеокарты
полный dmesg https://paste.ubuntu.com/p/2xZpDdS5CF/

Ответить