[SOLVED] Shut down takes up a lot of time

dezire · 2021-05-28 04:52:32

I am using a 500gb nvme which has dram so the speed should not be a problem...
The problem I am facing is that the while shut down it shows

"Starting version (some version number)"
and remains there for about 1 min before shutdown.

Last edited by dezire (2021-06-16 17:12:14)

seth · 2021-05-28 06:20:38

Inspect the system journal for the prvious boot or undo your silent-boot efforts (and remove the quiet kernel parameter)
The cause is typically that some userspace process takes its time to terminate (and might be ultimately killed by the system)

dezire · 2021-06-01 06:42:56

I read quite a bit but didn't understand a thing. Sorry to say but i don't know what to. I even tried fresh install still its the same thing. So as far as the common sense goes this is caused my something i have already installed.

seth · 2021-06-01 07:06:37

Please post the system journal for the previous boot. (sudo journalctl -b -1)

dezire · 2021-06-03 06:03:33

Jun 03 03:35:39 dezire-PC kernel: Linux version 5.12.8-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Fri, 28 May 2021 15:10:20 +0000
Jun 03 03:35:39 dezire-PC kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ce0857c4-5df3-4b6d-a514-fdcff9d47454 rw rootflags=subvol=@ loglevel=3 quiet
Jun 03 03:35:39 dezire-PC kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 03 03:35:39 dezire-PC kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 03 03:35:39 dezire-PC kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 03 03:35:39 dezire-PC kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 03 03:35:39 dezire-PC kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Jun 03 03:35:39 dezire-PC kernel: BIOS-provided physical RAM map:
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009e01fff] usable
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x0000000009e02000-0x0000000009ffffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20ffff] ACPI NVS
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x000000000a210000-0x000000000affffff] usable
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000db123fff] usable
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000db124000-0x00000000db4a3fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000db4a4000-0x00000000db507fff] ACPI data
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000db508000-0x00000000dcc06fff] ACPI NVS
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000dcc07000-0x00000000ddb56fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000ddb57000-0x00000000ddbfefff] type 20
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000ddbff000-0x00000000deffffff] usable
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x0000000100000000-0x000000041f37ffff] usable
Jun 03 03:35:39 dezire-PC kernel: BIOS-e820: [mem 0x000000041f380000-0x000000041fffffff] reserved
Jun 03 03:35:39 dezire-PC kernel: NX (Execute Disable) protection: active
Jun 03 03:35:39 dezire-PC kernel: efi: EFI v2.70 by American Megatrends
Jun 03 03:35:39 dezire-PC kernel: efi: ACPI=0xdcbf0000 ACPI 2.0=0xdcbf0014 SMBIOS=0xdda06000 MEMATTR=0xd7826698
Jun 03 03:35:39 dezire-PC kernel: SMBIOS 2.8 present.
Jun 03 03:35:39 dezire-PC kernel: DMI: Micro-Star International Co., Ltd. MS-7C56/MPG B550 GAMING PLUS (MS-7C56), BIOS 1.60 05/13/2021
Jun 03 03:35:39 dezire-PC kernel: tsc: Fast TSC calibration using PIT
Jun 03 03:35:39 dezire-PC kernel: tsc: Detected 4400.291 MHz processor
Jun 03 03:35:39 dezire-PC kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 03 03:35:39 dezire-PC kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 03 03:35:39 dezire-PC kernel: last_pfn = 0x41f380 max_arch_pfn = 0x400000000
Jun 03 03:35:39 dezire-PC kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
Jun 03 03:35:39 dezire-PC kernel: total RAM covered: 3583M
Jun 03 03:35:39 dezire-PC kernel: Found optimal setting for mtrr clean up
Jun 03 03:35:39 dezire-PC kernel:  gran_size: 64K         chunk_size: 64M         num_reg: 4          lose cover RAM: 0G
Jun 03 03:35:39 dezire-PC kernel: e820: update [mem 0xdd320000-0xdd32ffff] usable ==> reserved
Jun 03 03:35:39 dezire-PC kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Jun 03 03:35:39 dezire-PC kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
lines 1-57

seth · 2021-06-03 06:18:21

That's only the head. Don't copy out of the pager, see the 1st link in my signature instead.

dezire · 2021-06-05 06:44:16

I am sorry I am a novice in this matter but here is the link
http://sprunge.us/HliaMZ

seth · 2021-06-05 07:37:14

Jun 05 02:54:51 dezire-PC kernel: Linux version 5.12.8-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Fri, 28 May 2021 15:10:20 +0000
…
Jun 05 02:55:03 dezire-PC kernel: audit: type=1131 audit(1622841903.097:129): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 04 21:25:23 dezire-PC systemd-timesyncd[510]: Initial synchronization to time server 13.126.27.131:123 (2.arch.pool.ntp.org).
…
Jun 04 21:26:13 dezire-PC systemd[864]: Reached target Shutdown.
…
Jun 04 23:59:59 dezire-PC plasmashell[1236]: file:///home/dezire/.local/share/plasma/plasmoids/org.kde.fancyclock/contents/ui/main.qml:117:9: QML DropShadow: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
Jun 05 00:00:00 dezire-PC plasmashell[1236]: file:///home/dezire/.local/share/plasma/plasmoids/org.kde.fancyclock/contents/ui/main.qml:105:9: QML DropShadow: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
…
Jun 05 02:32:56 dezire-PC dbus-daemon[1133]: [session uid=1000 pid=1133] Successfully activated service 'org.kde.Shutdown'
Jun 05 02:33:06 dezire-PC kactivitymanagerd[1224]: The X11 connection broke (error 1). Did the X11 server die?
Jun 05 02:33:06 dezire-PC kscreen_backend_launcher[1314]: The X11 connection broke (error 1). Did the X11 server die?
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC systemd[1]: Stopping TeamViewer remote control daemon...
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kwin_x11[1186]: The X11 connection broke: I/O error (code 1)
Jun 05 02:33:06 dezire-PC systemd[1009]: run-media-dezire-Important.mount: Deactivated successfully.
Jun 05 02:33:06 dezire-PC baloorunner[1554]: The X11 connection broke (error 1). Did the X11 server die?
Jun 05 02:33:06 dezire-PC systemd[1009]: plasma-kglobalaccel.service: Deactivated successfully.
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC kded5[1182]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Jun 05 02:33:06 dezire-PC crond[516]: (CRON) INFO (Shutting down)
Jun 05 02:33:06 dezire-PC avahi-daemon[515]: avahi-daemon 0.8 exiting.
Jun 05 02:33:06 dezire-PC systemd[1009]: plasma-baloorunner.service: Main process exited, code=exited, status=1/FAILURE
Jun 05 02:33:06 dezire-PC systemd[1009]: plasma-baloorunner.service: Failed with result 'exit-code'.
Jun 05 02:33:06 dezire-PC kded5[1182]: The X11 connection broke: I/O error (code 1)
…
Jun 05 02:33:06 dezire-PC mkinitcpio[68393]:   -> Running build hook: [sd-shutdown]
…
Jun 05 02:33:06 dezire-PC mkinitcpio[68393]: ==> Build complete.
…
Jun 05 02:33:08 dezire-PC systemd[1]: sddm.service: Deactivated successfully.
Jun 05 02:33:08 dezire-PC systemd[1]: Stopped Simple Desktop Display Manager.
Jun 05 02:33:08 dezire-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
…
Jun 05 02:33:08 dezire-PC systemd[1]: sddm.service: Consumed 1min 50.314s CPU time.
…
Jun 05 02:34:36 dezire-PC systemd[1]: session-2.scope: Stopping timed out. Killing.
Jun 05 02:34:36 dezire-PC systemd[1]: session-2.scope: Killing process 1186 (kwin_x11) with signal SIGKILL.
Jun 05 02:34:36 dezire-PC systemd[1]: session-2.scope: Killing process 1340 (n/a) with signal SIGKILL.
Jun 05 02:34:36 dezire-PC systemd[1]: session-2.scope: Killing process 1368 (CPMMListener) with signal SIGKILL.
Jun 05 02:34:36 dezire-PC systemd[1]: session-2.scope: Failed with result 'timeout'.
Jun 05 02:34:36 dezire-PC systemd[1]: Stopped Session 2 of user dezire.
…
Jun 05 02:34:37 dezire-PC systemd[1]: Stopping Flush Journal to Persistent Storage...
Jun 05 02:34:37 dezire-PC systemd[1]: boot.mount: Deactivated successfully.
Jun 05 02:34:37 dezire-PC systemd[1]: Unmounted /boot.
Jun 05 02:34:37 dezire-PC systemd[1]: home.mount: Deactivated successfully.

Your system time is off by 5½ hours?

You initiate the shutdown Jun 05, 02:32:56
SDDM finishes Jun 05, 02:33:08 (so 12s later) but the session doesn't quit properly and some session processes (kwin_x11, CPMMListener) linger around and need to be killed on a timeout 90 seconds later.

=> log out of the session first and shut down from SDDM. Does it still take "a lot of time"?

dezire · 2021-06-05 09:41:30

Yes it did shut down fast when I logged out explicitly.
And I live in India the timezone is GMT+5½(IST) so i think thats why my time is ahead by 5½ hours...

Last edited by dezire (2021-06-05 12:27:19)

seth · 2021-06-05 14:01:18

But it starts 5½ ahead and is then set back. Do you have a parallel windows installation?

The problem is that plasma doesn't cleanly exit on a shutdown, but I can't tell you why, but eg. https://bbs.archlinux.org/viewtopic.php?id=264233 and a google for "CPMMListener" basically only yields this kind of stuff, eg. https://bugs.kde.org/show_bug.cgi?id=432604 & https://bugs.kde.org/show_bug.cgi?id=431863

It seems to be some named kwin_x11 thread, but I couldn't find more details on it…

dezire · 2021-06-05 15:29:11

Yes I have windows installed but i have turned fast boot off

seth · 2021-06-05 15:30:16

More than fastboot, windows probably sets the system clock in local time, https://feldspaten.org/2019/11/03/windo … ck-in-utc/

dezire · 2021-06-07 14:15:12

I would like to use IST instead is that viable?

seth · 2021-06-07 14:27:22

The point is to align the used timezones - no matter how.

The reasonable approach is to keep the hardware in UTC and have the software drift against that.
You /can/ go for localtime everywhere instead, but the downside is that the OS might interfere with each other.

So unless there're some really strong reservations against UTC, keep the HW in UTC for the less troublesome approach to the problem.

dezire · 2021-06-11 15:03:35

I just did what that article said still the shutdown is taking longer than usual.

seth · 2021-06-11 15:11:02

The clock thing was an unrelated off-hand remark.

The problem itself is related to your plasma session that fails to exit cleanly on shutdown (see 2nd paragraph in #10) but other than "plasma bug" I can't say really why, sorry.

dezire · 2021-06-16 17:11:43

Seems like there was some problem with KDE. The problem is no longer there after if switched to using qtile

Arch Linux

#1 2021-05-28 04:52:32

[SOLVED] Shut down takes up a lot of time

#2 2021-05-28 06:20:38

Re: [SOLVED] Shut down takes up a lot of time

#3 2021-06-01 06:42:56

Re: [SOLVED] Shut down takes up a lot of time

#4 2021-06-01 07:06:37

Re: [SOLVED] Shut down takes up a lot of time

#5 2021-06-03 06:03:33

Re: [SOLVED] Shut down takes up a lot of time

#6 2021-06-03 06:18:21

Re: [SOLVED] Shut down takes up a lot of time

#7 2021-06-05 06:44:16

Re: [SOLVED] Shut down takes up a lot of time

#8 2021-06-05 07:37:14

Re: [SOLVED] Shut down takes up a lot of time

#9 2021-06-05 09:41:30

Re: [SOLVED] Shut down takes up a lot of time

#10 2021-06-05 14:01:18

Re: [SOLVED] Shut down takes up a lot of time

#11 2021-06-05 15:29:11

Re: [SOLVED] Shut down takes up a lot of time

#12 2021-06-05 15:30:16

Re: [SOLVED] Shut down takes up a lot of time

#13 2021-06-07 14:15:12

Re: [SOLVED] Shut down takes up a lot of time

#14 2021-06-07 14:27:22

Re: [SOLVED] Shut down takes up a lot of time

#15 2021-06-11 15:03:35

Re: [SOLVED] Shut down takes up a lot of time

#16 2021-06-11 15:11:02

Re: [SOLVED] Shut down takes up a lot of time

#17 2021-06-16 17:11:43

Re: [SOLVED] Shut down takes up a lot of time

Board footer