You are not logged in.

Pages: 1

#1 2022-12-20 13:38:56

hully
Member
Registered: 2022-11-14
Posts: 164

My laptop takes a LONG time to reboot

My laptop takes a very long time to reboot (maybe 5 minutes?).

What can I do to debug the issue?

Offline

#2 2022-12-20 13:46:10

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,657
Website

Re: My laptop takes a LONG time to reboot

hully wrote:

My laptop takes a very long time to reboot (maybe 5 minutes?).

What can I do to debug the issue?

Make it faster.

If you want a more fine-tailored answer, provide at least some information about your system.
Like 

# systemd-analyze blame

for starters.

Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#3 2022-12-20 13:49:13

2ManyDogs
Forum Fellow
Registered: 2012-01-15
Posts: 4,648

Re: My laptop takes a LONG time to reboot

Moving to Newbie Corner.

Offline

#4 2022-12-20 14:18:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,411

Re: My laptop takes a LONG time to reboot

Which part of the REboot is slow - shutdown or (new) boot?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2022-12-21 03:07:51

hully
Member
Registered: 2022-11-14
Posts: 164

Re: My laptop takes a LONG time to reboot

seth wrote:

Which part of the REboot is slow - shutdown or (new) boot?

The shutdown

Offline

#6 2022-12-21 03:09:44

hully
Member
Registered: 2022-11-14
Posts: 164

Re: My laptop takes a LONG time to reboot

schard wrote:
hully wrote:

My laptop takes a very long time to reboot (maybe 5 minutes?).

What can I do to debug the issue?

Make it faster.

If you want a more fine-tailored answer, provide at least some information about your system.
Like 

# systemd-analyze blame

for starters.

50.305s dev-ttyS31.device
50.305s sys-devices-platform-serial8250-tty-ttyS31.device
50.304s sys-devices-platform-serial8250-tty-ttyS0.device
50.304s dev-ttyS0.device
50.303s sys-devices-platform-serial8250-tty-ttyS1.device
50.303s dev-ttyS1.device
50.302s dev-ttyS11.device
50.302s sys-devices-platform-serial8250-tty-ttyS11.device
50.301s dev-ttyS12.device
50.301s sys-devices-platform-serial8250-tty-ttyS12.device
50.300s sys-devices-platform-serial8250-tty-ttyS10.device
50.300s dev-ttyS10.device
50.300s sys-devices-platform-serial8250-tty-ttyS14.device
50.300s dev-ttyS14.device
50.299s dev-ttyS13.device
50.299s sys-devices-platform-serial8250-tty-ttyS13.device
50.298s dev-ttyS17.device
50.298s sys-devices-platform-serial8250-tty-ttyS17.device
50.298s dev-ttyS16.device
50.298s sys-devices-platform-serial8250-tty-ttyS16.device
50.298s sys-devices-platform-serial8250-tty-ttyS18.device
50.298s dev-ttyS18.device
50.296s sys-devices-platform-serial8250-tty-ttyS2.device
50.296s dev-ttyS2.device
50.296s dev-ttyS19.device
50.296s sys-devices-platform-serial8250-tty-ttyS19.device
50.294s sys-devices-platform-serial8250-tty-ttyS21.device
50.294s dev-ttyS21.device
50.294s sys-devices-platform-serial8250-tty-ttyS15.device
50.294s dev-ttyS15.device
50.293s sys-devices-platform-serial8250-tty-ttyS20.device
50.293s dev-ttyS20.device
50.292s dev-ttyS23.device
50.292s sys-devices-platform-serial8250-tty-ttyS23.device
50.291s dev-ttyS24.device
50.291s sys-devices-platform-serial8250-tty-ttyS24.device
50.291s dev-ttyS25.device
50.291s sys-devices-platform-serial8250-tty-ttyS25.device
50.290s sys-devices-platform-serial8250-tty-ttyS27.device
50.290s dev-ttyS27.device
50.290s dev-disk-by\x2duuid-ded45054\x2dbdce\x2d450c\x2d91d7\x2dd6f1de296bec.device
50.290s dev-disk-by\x2dlabel-INTDATA.device
50.290s dev-disk-by\x2ddiskseq-1.device
50.290s dev-disk-by\x2did-ata\x2dSanDisk_SSD_PLUS_1000GB_19248A804346.device
50.290s dev-disk-by\x2did-wwn\x2d0x5001b448b8e21ad4.device
50.290s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.device
50.290s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda.device
50.290s dev-sda.device
50.290s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0.device
50.289s dev-ttyS26.device
50.289s sys-devices-platform-serial8250-tty-ttyS26.device
50.288s dev-ttyS28.device
50.288s sys-devices-platform-serial8250-tty-ttyS28.device
50.288s dev-ttyS22.device
50.288s sys-devices-platform-serial8250-tty-ttyS22.device
50.286s dev-ttyS29.device
50.286s sys-devices-platform-serial8250-tty-ttyS29.device
50.286s sys-devices-platform-serial8250-tty-ttyS30.device
50.286s dev-ttyS30.device
50.284s sys-devices-platform-serial8250-tty-ttyS3.device
50.284s dev-ttyS3.device
50.282s dev-ttyS5.device
50.282s sys-devices-platform-serial8250-tty-ttyS5.device
50.280s dev-ttyS7.device
50.280s sys-devices-platform-serial8250-tty-ttyS7.device
50.279s sys-devices-platform-serial8250-tty-ttyS6.device
50.279s dev-ttyS6.device
50.277s dev-ttyS8.device
50.277s sys-devices-platform-serial8250-tty-ttyS8.device
50.276s dev-ttyS9.device
50.276s sys-devices-platform-serial8250-tty-ttyS9.device
50.228s sys-module-configfs.device
49.980s sys-devices-pci0000:00-0000:00:1d.0-0000:06:00.0-nvme-nvme0-nvme0n1.device
49.980s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKW512G7_BTPY71310B71512F.device
49.980s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25cc7f4b54d01.device
49.979s dev-nvme0n1.device
49.979s dev-disk-by\x2ddiskseq-2.device
49.979s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1.device
49.975s dev-nvme0n1p3.device
49.975s dev-disk-by\x2duuid-919512c5\x2dc7f3\x2d4754\x2d85c0\x2d5b6f04a0e294.device
49.975s dev-disk-by\x2dpartuuid-39128694\x2d4076\x2d5e4a\x2d91a8\x2d437b93742f25.device
49.975s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKW512G7_BTPY71310B71512F\x2dpart3.device
49.975s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25cc7f4b54d01\x2dpart3.device
49.975s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1\x2dpart3.device
49.975s sys-devices-pci0000:00-0000:00:1d.0-0000:06:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
49.955s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1\x2dpart2.device
49.955s sys-devices-pci0000:00-0000:00:1d.0-0000:06:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
49.955s dev-disk-by\x2dpartuuid-35c856da\x2dfa99\x2d744f\x2d8258\x2da2b6381423b1.device
49.955s dev-nvme0n1p2.device
49.955s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25cc7f4b54d01\x2dpart2.device
49.955s dev-disk-by\x2duuid-6d8b3140\x2d3fa1\x2d4642\x2d974e\x2d5dbaf1615659.device
49.955s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKW512G7_BTPY71310B71512F\x2dpart2.device
49.954s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKKW512G7_BTPY71310B71512F\x2dpart1.device
49.954s sys-devices-pci0000:00-0000:00:1d.0-0000:06:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
49.954s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25cc7f4b54d01\x2dpart1.device
49.954s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1\x2dpart1.device
49.954s dev-disk-by\x2duuid-B869\x2d1788.device
49.954s dev-disk-by\x2dpartuuid-50c66e62\x2d3c9d\x2deb46\x2d88bd\x2daa1ec86b1e64.device
49.954s dev-nvme0n1p1.device
 6.276s NetworkManager-wait-online.service
 3.696s systemd-cryptsetup@dataint.service
 1.008s initrd-switch-root.service
  476ms docker.service
  399ms systemd-udev-trigger.service
  336ms systemd-remount-fs.service
  304ms cups.service
  284ms systemd-modules-load.service
  278ms systemd-tmpfiles-setup-dev.service
  272ms modprobe@fuse.service
  262ms boot.mount
  208ms lvm2-monitor.service
  204ms modprobe@drm.service
  184ms systemd-journal-flush.service
  168ms user@1000.service
  118ms systemd-rfkill.service
  117ms systemd-random-seed.service
  109ms mnt-dataint.mount
  103ms systemd-tmpfiles-setup.service
   94ms kmod-static-nodes.service
   81ms systemd-user-sessions.service
   81ms systemd-udevd.service
   69ms udisks2.service
   66ms user-runtime-dir@1000.service
   63ms systemd-fsck@dev-mapper-dataint.service
   58ms systemd-journald.service
   52ms dev-hugepages.mount
   52ms systemd-fsck@dev-disk-by\x2duuid-B869\x2d1788.service
   49ms dev-mqueue.mount
   47ms sys-kernel-debug.mount
   44ms sys-kernel-tracing.mount
   44ms systemd-sysctl.service
   40ms NetworkManager.service
   37ms bluetooth.service
   36ms initrd-cleanup.service
   33ms systemd-logind.service
   33ms colord.service
   31ms dbus.service
   31ms initrd-parse-etc.service
   30ms systemd-backlight@backlight:intel_backlight.service
   29ms systemd-update-utmp.service
   20ms sys-fs-fuse-connections.mount
   17ms sys-kernel-config.mount
   17ms initrd-udevadm-cleanup-db.service
   14ms systemd-fsck-root.service
   12ms wpa_supplicant.service
   11ms polkit.service
    9ms dev-disk-by\x2duuid-6d8b3140\x2d3fa1\x2d4642\x2d974e\x2d5dbaf1615659.swap
    7ms NetworkManager-dispatcher.service
    5ms modprobe@configfs.service
    3ms rtkit-daemon.service
    2ms tmp.mount
    1ms docker.socket

Offline

#7 2022-12-21 05:17:14

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,653

Re: My laptop takes a LONG time to reboot

49.954s dev-nvme0n1p1.device

Ouch!

From my system:

623ms dev-nvme0n1p6.device

Half a second versus the lion's share of a minute a minute.
All of your disk related stuff takes on the order of 49 to 50 seconds.  Also, What is with all the ttySxx devices?

What is the output of find /etc/systemd   ?

How about of systemd-analyze critical-chain   ?

Here is what I expect:

ewaller@odin/~[130]% systemd-analyze critical-chain 
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @3.547s
└─multi-user.target @3.547s
  └─getty.target @3.547s
    └─getty@tty1.service @3.546s
      └─systemd-user-sessions.service @2.157s +30ms
        └─network.target @1.986s
          └─iwd.service @3.772s +108ms
            └─basic.target @1.880s
              └─sockets.target @1.879s
                └─dbus.socket @1.877s
                  └─sysinit.target @1.869s
                    └─systemd-backlight@leds:asus::kbd_backlight.service @3.661s +43ms
                      └─system-systemd\x2dbacklight.slice @3.561s
                        └─system.slice @753ms
                          └─-.slice @754ms
ewaller@odin/~%

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#8 2022-12-21 05:42:13

hully
Member
Registered: 2022-11-14
Posts: 164

Re: My laptop takes a LONG time to reboot

Half a second versus the lion's share of a minute a minute.
All of your disk related stuff takes on the order of 49 to 50 seconds.

Does the half a second account for the time to insert the LUKS password?

Also, What is with all the ttySxx devices?

I don't know what a ttySxx device is

What is the output of find /etc/systemd   ?

❯ find /etc/systemd
/etc/systemd
/etc/systemd/user
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/sockets.target.wants/gcr-ssh-agent.socket
/etc/systemd/user/sockets.target.wants/pipewire.socket
/etc/systemd/user/sockets.target.wants/pipewire-pulse.socket
/etc/systemd/user/sockets.target.wants/gnome-keyring-daemon.socket
/etc/systemd/user/default.target.wants
/etc/systemd/user/default.target.wants/xdg-user-dirs-update.service
/etc/systemd/user/pipewire-session-manager.service
/etc/systemd/user/pipewire.service.wants
/etc/systemd/user/pipewire.service.wants/wireplumber.service
/etc/systemd/network
/etc/systemd/system
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/expressvpn.service
/etc/systemd/system/multi-user.target.wants/LanguageTool.service
/etc/systemd/system/multi-user.target.wants/docker.service
/etc/systemd/system/multi-user.target.wants/cups.service
/etc/systemd/system/multi-user.target.wants/cups.path
/etc/systemd/system/multi-user.target.wants/piavpn.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/network-online.target.wants
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/system/dbus-org.bluez.service
/etc/systemd/system/bluetooth.target.wants
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/LanguageTool.service
/etc/systemd/system/piavpn.service
/etc/systemd/system/printer.target.wants
/etc/systemd/system/printer.target.wants/cups.service
/etc/systemd/system/sockets.target.wants
/etc/systemd/system/sockets.target.wants/cups.socket
/etc/systemd/logind.conf
/etc/systemd/coredump.conf
/etc/systemd/homed.conf
/etc/systemd/journal-remote.conf
/etc/systemd/journal-upload.conf
/etc/systemd/journald.conf
/etc/systemd/networkd.conf
/etc/systemd/oomd.conf
/etc/systemd/pstore.conf
/etc/systemd/resolved.conf
/etc/systemd/sleep.conf
/etc/systemd/system.conf
/etc/systemd/timesyncd.conf
/etc/systemd/user.conf

How about of systemd-analyze critical-chain   ?

❯ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @12.733s
└─multi-user.target @12.733s
  └─docker.service @12.188s +544ms
    └─network-online.target @12.118s
      └─NetworkManager-wait-online.service @5.824s +6.293s
        └─NetworkManager.service @5.741s +39ms
          └─dbus.service @5.698s +39ms
            └─basic.target @5.693s
              └─sockets.target @5.693s
                └─docker.socket @5.691s +2ms
                  └─sysinit.target @5.688s
                    └─systemd-update-done.service @5.654s +33ms
                      └─ldconfig.service @5.178s +423ms
                        └─local-fs.target @5.120s
                          └─var-lib-docker-btrfs.mount @12.458s
                            └─local-fs-pre.target @1.761s
                              └─systemd-tmpfiles-setup-dev.service @1.707s +53ms
                                └─systemd-sysusers.service @1.505s +185ms
                                  └─systemd-remount-fs.service @1.105s +309ms
                                    └─systemd-fsck-root.service @584542y 2w 2d 20h 1min 49.263s +14ms
                                      └─systemd-journald.socket
                                        └─system.slice
                                          └─-.slice

Offline

#9 2022-12-21 08:26:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,411

Re: My laptop takes a LONG time to reboot

hully wrote:
seth wrote:

Which part of the REboot is slow - shutdown or (new) boot?

The shutdown

Please post the system journal of the previous boot, after such slow reboot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2022-12-24 10:45:17

hully
Member
Registered: 2022-11-14
Posts: 164

Re: My laptop takes a LONG time to reboot

seth wrote:
hully wrote:
seth wrote:

Which part of the REboot is slow - shutdown or (new) boot?

The shutdown

Please post the system journal of the previous boot, after such slow reboot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Here it is [REMOVED]

Last edited by hully (2023-01-02 18:28:07)

Offline

#11 2022-12-24 15:27:34

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,411

Re: My laptop takes a LONG time to reboot

Dec 24 10:50:43 raffadora systemd[2766]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Dec 24 10:50:43 raffadora systemd[2766]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Dec 24 10:50:43 raffadora systemd[2766]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
Dec 24 10:50:43 raffadora systemd[2766]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'.
…
Dec 24 10:52:13 raffadora systemd[2766]: xdg-document-portal.service: State 'stop-sigterm' timed out. Killing.
Dec 24 10:52:13 raffadora systemd[2766]: xdg-document-portal.service: Killing process 2962 (xdg-document-po) with signal SIGKILL.
Dec 24 10:52:13 raffadora systemd[2766]: xdg-document-portal.service: Killing process 2967 (fusermount3) with signal SIGKILL.
Dec 24 10:52:13 raffadora systemd[2766]: xdg-document-portal.service: Killing process 2963 (gmain) with signal SIGKILL.
Dec 24 10:52:13 raffadora systemd[2766]: xdg-document-portal.service: Main process exited, code=killed, status=9/KILL
Dec 24 10:52:13 raffadora systemd[2766]: xdg-document-portal.service: Failed with result 'timeout'.
Dec 24 10:52:13 raffadora systemd[2766]: Stopped flatpak document portal service.

It's because flatschpak.
Could be down to the specific xdg-desktop-portal-hyprland-git

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2022-12-24 19:35:42

hully
Member
Registered: 2022-11-14
Posts: 164

Re: My laptop takes a LONG time to reboot

What's wrong with xdg-desktop-portal-hyprland-git?

Should I report it as a bug?

Offline

#13 2022-12-24 21:05:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,411

Re: My laptop takes a LONG time to reboot

I don't know what's wrong with it and we have no established /that/ something is wrong with it.

seth wrote:

Could be … the specific xdg-desktop-portal-hyprland-git

But it could also just be an innocent messenger for a more general flatschpak SNAFU.

Try to replace it w/ one of the other xdg-portal implementations and see whether the issue remains.
If yes, see what happens when you remove flatpak/xdg-portal* entirely.

This should tell us whether and which element of the flatschpak/portal chain causes this.

Also, since SDDM causes similar(?) problems w/ KDE, try to log out of the hyprland session and reboot from SDDM and see whether xdg-document-portal.service still acts up.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2023-01-02 18:27:47

hully
Member
Registered: 2022-11-14
Posts: 164

Re: My laptop takes a LONG time to reboot

I have uninstalled all xdg-desktop-portal and even flatpak and it still takes a long time to reboot.

I think it is due to SDDM:

Jan 02 19:20:56 HOSTNAME systemd[1]: piavpn.service: Consumed 10.174s CPU time.
Jan 02 19:22:24 HOSTNAME systemd[1]: sddm.service: State 'stop-sigterm' timed out. Killing.
Jan 02 19:22:24 HOSTNAME systemd[1]: sddm.service: Killing process 2197 (sddm) with signal SIGKILL.
Jan 02 19:22:24 HOSTNAME systemd[1]: sddm.service: Killing process 6920 (Xorg) with signal SIGKILL.
Jan 02 19:22:24 HOSTNAME systemd[1]: sddm.service: Main process exited, code=killed, status=9/KILL
Jan 02 19:22:24 HOSTNAME systemd[1]: sddm.service: Failed with result 'timeout'.
Jan 02 19:22:25 HOSTNAME systemd[1]: Stopped Simple Desktop Display Manager.

Looks like SIGTERM times out and it is killed.

Offline

#15 2023-01-02 19:11:24

hully
Member
Registered: 2022-11-14
Posts: 164

Re: My laptop takes a LONG time to reboot

Fixed by installing sddm-git from the AUR.

Seems to be this problem: https://github.com/sddm/sddm/issues/1476

It isn't clear the commit that fixed it, but it is fixed in develop branch.

The latest stable that Arch ships is from 2 years ago.

Last edited by hully (2023-01-04 07:54:21)

Offline

Pages: 1

Board footer

Powered by FluxBB