你不如用Stacer查看一下启动服务项和自启应用。
下次重启卡的时候,进入系统后终端执行:sudo journalctl > ~/Desktop/journal.txt
把这个启动日志贴出来看看
反馈问题提供下日志吧,研发也不会算卦
systemd-analyze blame看哪个服务耗时长
反馈问题提供下日志吧,研发也不会算卦
systemd-analyze blame看哪个服务耗时长
不太懂呀,我试试。
反馈问题提供下日志吧,研发也不会算卦
systemd-analyze blame看哪个服务耗时长
下面的是日志,可以吗?
wangwq-lonng@wangwq-lonng-PC:~/Desktop$ systemd-analyze blame
52.304s nmbd.service
6.332s NetworkManager-wait-online.service
2.023s plymouth-quit-wait.service
1.286s udisks2.service
854ms ModemManager.service
753ms accounts-daemon.service
707ms lightdm.service
678ms user@1000.service
672ms cups.service
576ms dev-sda5.device
571ms dev-sda4.device
515ms com.home.appstore.daemon.service
506ms polkit.service
501ms fprintd.service
423ms avahi-daemon.service
411ms smbd.service
407ms dbus.service
353ms upower.service
352ms systemd-tmpfiles-clean.service
267ms deepin-authenticate.service
237ms systemd-udev-trigger.service
202ms loonggl-sw.service
154ms winbind.service
137ms samba-ad-dc.service
131ms systemd-logind.service
116ms NetworkManager.service
lines 1-26...skipping...
52.304s nmbd.service
6.332s NetworkManager-wait-online.service
2.023s plymouth-quit-wait.service
1.286s udisks2.service
854ms ModemManager.service
753ms accounts-daemon.service
707ms lightdm.service
678ms user@1000.service
672ms cups.service
576ms dev-sda5.device
571ms dev-sda4.device
515ms com.home.appstore.daemon.service
506ms polkit.service
501ms fprintd.service
423ms avahi-daemon.service
411ms smbd.service
407ms dbus.service
353ms upower.service
352ms systemd-tmpfiles-clean.service
267ms deepin-authenticate.service
237ms systemd-udev-trigger.service
202ms loonggl-sw.service
154ms winbind.service
137ms samba-ad-dc.service
131ms systemd-logind.service
116ms NetworkManager.service
112ms systemd-journal-flush.service
109ms wpa_supplicant.service
103ms dde-dconfig-daemon.service
97ms e2scrub_reap.service
95ms systemd-fsck@dev-disk-by\x2duuid-B314\x2d736C.service
93ms org.deepin.linglong.PackageManager.service
93ms lvm2-monitor.service
92ms grub-common.service
87ms systemd-udevd.service
79ms systemd-fsck@dev-disk-by\x2duuid-abefda3a\x2d2510\x2d4d2b\x2d9a73\x2df0ee51133b62.service
73ms systemd-journald.service
69ms plymouth-start.service
58ms bluetooth.service
56ms lm-sensors.service
54ms deepin-login-sound.service
41ms systemd-timesyncd.service
40ms systemd-tmpfiles-setup-dev-early.service
39ms ipwatchd.service
39ms uos-ste-resourced.service
32ms systemd-modules-load.service
27ms alsa-restore.service
25ms systemd-tmpfiles-setup.service
24ms systemd-remount-fs.service
23ms dev-hugepages.mount
23ms dev-mqueue.mount
22ms systemd-sysctl.service
22ms sys-kernel-debug.mount
22ms binfmt-support.service
22ms sys-kernel-tracing.mount
21ms kmod-static-nodes.service
21ms blk-availability.service
20ms modprobe@configfs.service
19ms systemd-binfmt.service
19ms modprobe@drm.service
19ms modprobe@efi_pstore.service
19ms user-runtime-dir@1000.service
18ms modprobe@fuse.service
18ms plymouth-read-write.service
15ms systemd-random-seed.service
14ms boot-efi.mount
13ms systemd-fsck@dev-disk-by\x2duuid-76869dd2\x2d4333\x2d422b\x2d8f27\x2d74285615737a.service
12ms modprobe@dm_mod.service
12ms modprobe@loop.service
12ms dev-disk-by\x2duuid-d0d464ee\x2d48d3\x2d4286\x2dbd1c\x2d8d2c9a79b04e.swap
11ms systemd-tmpfiles-setup-dev.service
11ms sys-fs-fuse-connections.mount
10ms systemd-update-utmp-runlevel.service
10ms home.mount
lines 1-74
你不如用Stacer查看一下启动服务项和自启应用。
龙架构没有Stacer这个软件。
下面的是日志,可以吗?
wangwq-lonng@wangwq-lonng-PC:~/Desktop$ systemd-analyze blame
52.304s nmbd.service
6.332s NetworkManager-wait-online.service
2.023s plymouth-quit-wait.service
1.286s udisks2.service
854ms ModemManager.service
753ms accounts-daemon.service
707ms lightdm.service
678ms user@1000.service
672ms cups.service
576ms dev-sda5.device
571ms dev-sda4.device
515ms com.home.appstore.daemon.service
506ms polkit.service
501ms fprintd.service
423ms avahi-daemon.service
411ms smbd.service
407ms dbus.service
353ms upower.service
352ms systemd-tmpfiles-clean.service
267ms deepin-authenticate.service
237ms systemd-udev-trigger.service
202ms loonggl-sw.service
154ms winbind.service
137ms samba-ad-dc.service
131ms systemd-logind.service
116ms NetworkManager.service
lines 1-26...skipping...
52.304s nmbd.service
6.332s NetworkManager-wait-online.service
2.023s plymouth-quit-wait.service
1.286s udisks2.service
854ms ModemManager.service
753ms accounts-daemon.service
707ms lightdm.service
678ms user@1000.service
672ms cups.service
576ms dev-sda5.device
571ms dev-sda4.device
515ms com.home.appstore.daemon.service
506ms polkit.service
501ms fprintd.service
423ms avahi-daemon.service
411ms smbd.service
407ms dbus.service
353ms upower.service
352ms systemd-tmpfiles-clean.service
267ms deepin-authenticate.service
237ms systemd-udev-trigger.service
202ms loonggl-sw.service
154ms winbind.service
137ms samba-ad-dc.service
131ms systemd-logind.service
116ms NetworkManager.service
112ms systemd-journal-flush.service
109ms wpa_supplicant.service
103ms dde-dconfig-daemon.service
97ms e2scrub_reap.service
95ms systemd-fsck@dev-disk-by\x2duuid-B314\x2d736C.service
93ms org.deepin.linglong.PackageManager.service
93ms lvm2-monitor.service
92ms grub-common.service
87ms systemd-udevd.service
79ms systemd-fsck@dev-disk-by\x2duuid-abefda3a\x2d2510\x2d4d2b\x2d9a73\x2df0ee51133b62.service
73ms systemd-journald.service
69ms plymouth-start.service
58ms bluetooth.service
56ms lm-sensors.service
54ms deepin-login-sound.service
41ms systemd-timesyncd.service
40ms systemd-tmpfiles-setup-dev-early.service
39ms ipwatchd.service
39ms uos-ste-resourced.service
32ms systemd-modules-load.service
27ms alsa-restore.service
25ms systemd-tmpfiles-setup.service
24ms systemd-remount-fs.service
23ms dev-hugepages.mount
23ms dev-mqueue.mount
22ms systemd-sysctl.service
22ms sys-kernel-debug.mount
22ms binfmt-support.service
22ms sys-kernel-tracing.mount
21ms kmod-static-nodes.service
21ms blk-availability.service
20ms modprobe@configfs.service
19ms systemd-binfmt.service
19ms modprobe@drm.service
19ms modprobe@efi_pstore.service
19ms user-runtime-dir@1000.service
18ms modprobe@fuse.service
18ms plymouth-read-write.service
15ms systemd-random-seed.service
14ms boot-efi.mount
13ms systemd-fsck@dev-disk-by\x2duuid-76869dd2\x2d4333\x2d422b\x2d8f27\x2d74285615737a.service
12ms modprobe@dm_mod.service
12ms modprobe@loop.service
12ms dev-disk-by\x2duuid-d0d464ee\x2d48d3\x2d4286\x2dbd1c\x2d8d2c9a79b04e.swap
11ms systemd-tmpfiles-setup-dev.service
11ms sys-fs-fuse-connections.mount
10ms systemd-update-utmp-runlevel.service
10ms home.mount
lines 1-74
上一次是关机再开机还是直接重启
上一次是关机再开机还是直接重启
关机后再重启的,总共用时15分钟。
关机后再重启的,总共用时15分钟。
耗时最长的是nmbd.service,平时用samba文件共享吗,不用的话可以禁用掉再试
耗时最长的是nmbd.service,平时用samba文件共享吗,不用的话可以禁用掉再试
偶尔用一下。
下次重启卡的时候,进入系统后终端执行:sudo journalctl > ~/Desktop/journal.txt
把这个启动日志贴出来看看
帖不上来呀,太长了。文件也太大。也发不上来。
偶尔用一下。
开启了samba文件共享,开机时间长那就是自然的事了。
开启了samba文件共享,开机时间长那就是自然的事了。
这个东西是默认打开的吗?我印象我没访问局域网时,也是启动时间过长呀。另外我的笔记本x86的v25就没有问题呀。
帖不上来呀,太长了。文件也太大。也发不上来。
放网盘,然后发个链接上来呗

放网盘,然后发个链接上来呗

摸索出了快速删除没用页面的方法,文件变小了,可以上传了。10点50关机后重启,11点5分左右重启成功。
Popular Events
More

中文 
龙架构深度v25,关机再启动15分钟,直接重启1分钟?什么原因?
龙架构v25现在很好用了,一直用做生产力,但关机再起动时间过长一直困扰着我,有大佬能分析出原因吗?常用软件的安装是通过星火商店安装的,是这个原因吗?
另外一晚上待机重启也很快,就是好几天待机重启也正常。就是关机后,再重启时间就很长。