issue during shutdown/rebooting the system

seth · 2022-03-10 07:19:01

now what do you need exactly ?

seth wrote:

We're then interested at the tail of the shutdown process that includes the "shutdown[1]: could not detach DM /dev/dm-0: Device or resource busy" message.
In doubt as a photo if it does never show up in the system journal.

AbdullahAlharbi · 2022-03-10 07:21:15

seth wrote:

now what do you need exactly ?
seth wrote:
We're then interested at the tail of the shutdown process that includes the "shutdown[1]: could not detach DM /dev/dm-0: Device or resource busy" message.
In doubt as a photo if it does never show up in the system journal.

i'm sorry how i can get the tail of the shutdown process?

also now i don't see the issues when shutdown / restarting and i don't know yet if they are still exists

seth · 2022-03-10 07:36:25

"sudo journalctl -b -1" shows the journal of the previous boot, "sudo journalctl -b -2" of the second previous and so on.
The "tail" is the end of the journal (ie. the last number of lines by timestamp)
Look at previous boots until you find one that has the error message. If there's none, you'll have to wait until the problem re-occurs and since this might happen after the journal was synced to disk, make a photo of the monitor.

AbdullahAlharbi · 2022-03-10 07:52:37

seth wrote:

"sudo journalctl -b -1" shows the journal of the previous boot, "sudo journalctl -b -2" of the second previous and so on.
The "tail" is the end of the journal (ie. the last number of lines by timestamp)
Look at previous boots until you find one that has the error message. If there's none, you'll have to wait until the problem re-occurs and since this might happen after the journal was synced to disk, make a photo of the monitor.

alright thank you so much

AbdullahAlharbi · 2022-03-10 22:58:40

okay the problem occurred during last restart and i have took a picture and this i think it has the timestamp

"shutdown[1]: could not detach DM /dev/dm-0: Device or resource busy"

i also looked into "sudo journalctl -b -1" but i did not find it there

and i noticed this thing this time:
https://i.ibb.co/922YRyB/2022-03-11-01-52.png

also this is another picture with the timestamp note this picture was taken after the previous picture up:
https://i.ibb.co/b2QtG20/2022-03-11-01-54.png

BR..Abdullah

Last edited by AbdullahAlharbi (2022-03-10 22:59:48)

seth · 2022-03-11 06:57:15

You session doesn't terminate immediately - this should absolutely be reflected in the journal.
So please post the system journal for the boot that ended in https://i.ibb.co/922YRyB/2022-03-11-01-52.png

AbdullahAlharbi · 2022-03-12 06:52:10

Hello,

sorry for taking so much time to reply

but do you have any suggestions on how to upload the journal ?

i have used this command to get the whole journal from that day:
journalctl --since 2022-03-10 --until 2022-03-12

until yesterday i will see how i can upload the journal file 68k lines..
i'm sure they will have everything lol

Last edited by AbdullahAlharbi (2022-03-12 06:53:06)

AbdullahAlharbi · 2022-03-12 07:05:10

here is the journal file

...

also do you think that the errors can be caused by external drive ?

EDIT:

i have found this "Stopped Session 2 of User rx" in the file
and i decided to just share the output from that

https://pastebin.com/xrYQ7G85

BR..Abdullah

Last edited by AbdullahAlharbi (2022-03-12 07:37:24)

seth · 2022-03-12 08:44:41

Mar 11 01:11:28 localhost systemd[1]: Stopped Session 2 of User rx.
…
Mar 11 01:11:29 localhost systemd-journald[443]: Journal stopped
-- Boot 44035bd616bf49d292bbc02a6be72d85 --
Mar 11 01:11:50 localhost kernel: Linux version 5.16.13-arch1-1 (linux@archlinux) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT Tue, 08 Mar 2022 20:07:36 +0000

But that one takes 1 second to the end of the journal and 22 seconds to the beginning of the next boot - there's no 90 second stall here.

You also have't fixed your hostname.

AbdullahAlharbi · 2022-03-12 10:02:15

seth wrote:

Mar 11 01:11:28 localhost systemd[1]: Stopped Session 2 of User rx.
…
Mar 11 01:11:29 localhost systemd-journald[443]: Journal stopped
-- Boot 44035bd616bf49d292bbc02a6be72d85 --
Mar 11 01:11:50 localhost kernel: Linux version 5.16.13-arch1-1 (linux@archlinux) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT Tue, 08 Mar 2022 20:07:36 +0000
But that one takes 1 second to the end of the journal and 22 seconds to the beginning of the next boot - there's no 90 second stall here.
You also have't fixed your hostname.

i did this for the hostname:
hostnamectl set-hostname localhost

and then when i was installing i edited the /etc/hosts file and added these

127.0.0.1        localhost
::1              localhost

[rx@localhost ~]$ hostnamectl 
   Static hostname: localhost
Transient hostname: archlinux
         Icon name: computer-desktop
           Chassis: desktop ?
        Machine ID: 2d84888ecdbd44a2ae87adadea5768dd
           Boot ID: b3c5123389924b2089020be4f7689cd9
  Operating System: Arch Linux                        
            Kernel: Linux 5.16.13-arch1-1
      Architecture: x86-64
   Hardware Vendor: Micro-Star International Co., Ltd.
    Hardware Model: MS-7C35
[rx@localhost ~]$ cat /etc/hostname 
localhost

should i change the hostname to something else ?

also i will have now a look into the journal again now

Last edited by AbdullahAlharbi (2022-03-12 10:04:21)

AbdullahAlharbi · 2022-03-12 10:57:18

could you please have a look at this ?

https://pastebin.com/LTvZ6s52

i think the problem could be from wpa_supplicant because i got some issues with it before

V1del · 2022-03-12 11:57:37

localhost is a reserved keyword and should not be your actual hostname.

There's no indication in that output that wpa_supplicant is causing an issue. And I also don't see anything that's delaying the user session unless that would be the relevant parts at the beginning that aren't present.

Last edited by V1del (2022-03-12 12:06:41)

AbdullahAlharbi · 2022-03-12 12:04:37

V1del wrote:

localhost is a reserved keyword and should not be your actual hostname.
There's no indication in that output that wpa_supplicant is causing an issue.

thank you..

i will change the hostname then
i'm still swimming in the 68k line reached line 20k ...
i did not find anything yet with 90 second stall all i can notice is sometimes this:

Mar 11 01:20:24 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

and then 3 seconds to get this:

Mar 11 01:20:27 localhost NetworkManager[707]: <info>  [1646950827.2419] caught SIGTERM, shutting down normally.

AbdullahAlharbi · 2022-03-12 12:28:36

okay here's the full journal file

https://drive.google.com/file/d/1clmBs2 … sp=sharing

sorry

BR

Last edited by AbdullahAlharbi (2022-03-12 12:34:46)

seth · 2022-03-13 06:51:06

No rebooot takes more than 40 seconds, most aoround 20.
What /is/ there is

Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 932 (kwin_x11) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 986 (QQmlThread) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 10287 (FreezeDetector) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 67794 (n/a) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 68455 (n/a) with signal SIGKILL.
Mar 11 01:26:48 localhost systemd[869]: app-firefox-4016c7db7ce346e9b2ded54cfee14109.scope: Killing process 1054 (JS Watchdog) with signal SIGKILL.
Mar 11 01:28:22 localhost systemd[867]: app-firefox-2619db18f80c45469d1954514fd8fb3e.scope: Killing process 1101 (Renderer) with signal SIGKILL.
Mar 11 01:28:22 localhost systemd[867]: app-firefox-2619db18f80c45469d1954514fd8fb3e.scope: Killing process 1850 (ImageIO) with signal SIGKILL.
Mar 11 01:28:22 localhost systemd[867]: app-firefox-2619db18f80c45469d1954514fd8fb3e.scope: Killing process 1970 (MediaSu~isor #2) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 936 (kwin_x11) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 1029 (vsync event mon) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 1056 (CPMMListener) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 2611 (n/a) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 77405 (QSGRenderThread) with signal SIGKILL.

what fits the pattern of https://bbs.archlinux.org/viewtopic.php?id=269549 and is related to rebooting from within the session.

AbdullahAlharbi · 2022-03-13 10:05:54

seth wrote:

No rebooot takes more than 40 seconds, most aoround 20.
What /is/ there is

Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 932 (kwin_x11) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 986 (QQmlThread) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 10287 (FreezeDetector) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 67794 (n/a) with signal SIGKILL.
Mar 11 01:11:28 localhost systemd[1]: session-2.scope: Killing process 68455 (n/a) with signal SIGKILL.
Mar 11 01:26:48 localhost systemd[869]: app-firefox-4016c7db7ce346e9b2ded54cfee14109.scope: Killing process 1054 (JS Watchdog) with signal SIGKILL.
Mar 11 01:28:22 localhost systemd[867]: app-firefox-2619db18f80c45469d1954514fd8fb3e.scope: Killing process 1101 (Renderer) with signal SIGKILL.
Mar 11 01:28:22 localhost systemd[867]: app-firefox-2619db18f80c45469d1954514fd8fb3e.scope: Killing process 1850 (ImageIO) with signal SIGKILL.
Mar 11 01:28:22 localhost systemd[867]: app-firefox-2619db18f80c45469d1954514fd8fb3e.scope: Killing process 1970 (MediaSu~isor #2) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 936 (kwin_x11) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 1029 (vsync event mon) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 1056 (CPMMListener) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 2611 (n/a) with signal SIGKILL.
Mar 11 07:26:43 localhost systemd[1]: session-2.scope: Killing process 77405 (QSGRenderThread) with signal SIGKILL.

what fits the pattern of https://bbs.archlinux.org/viewtopic.php?id=269549 and is related to rebooting from within the session.

Hello,

first thank you so much for taking the time to look into this i really appreciate your time to help me

as for kde here's my configurations:
1. i'm using the default breeze dark with breeze decorations
2. i don't have any community plugins and i don't have any themes installed as well
3. i don't have kvantum

sometimes i noticed this the screen refresh rate is rest to 60hz however i don't know if this can have any relations with the issue

as for rebooting within the session sometimes it hangs and sometimes it does not hang and rebooting fast

when i log out from kde and reboot from sddm i notice this the refresh rate is rest to 60hz again so my guess:
1. it could be from nvidia drivers / i did not saw any issues with it i have played some games and i did not notice any frame drop or anything
2. my kde installation was not correct because i just installed plasma-desktop and that kde is missing a library in fact it was missing kscreen library and this one is used to configure the display settings

what's your thoughts on this and do you have any suggestions to fix this or to try some settings perhaps ?

BR

Last edited by AbdullahAlharbi (2022-03-13 10:07:42)

AbdullahAlharbi · 2022-03-14 08:00:54

Hello, i have reinstalled arch but this time i have used the script(archinstall) and just choose the defaults

i'm still getting this:
https://i.ibb.co/922YRyB/2022-03-11-01-52.png

and i still have the same issue also this is what i found in journal:

Mar 14 10:19:58 arch systemd[1]: session-2.scope: Stopping timed out. Killing.
Mar 14 10:19:58 arch systemd[1]: session-2.scope: Killing process 830 (kwin_x11) with signal SIGKILL.
Mar 14 10:19:58 arch systemd[1]: session-2.scope: Killing process 887 (QQmlThread) with signal SIGKILL.
Mar 14 10:19:58 arch systemd[1]: session-2.scope: Killing process 2997 (FreezeDetector) with signal SIGKILL.
Mar 14 10:19:58 arch systemd[1]: session-2.scope: Failed with result 'timeout'.

do you think that the issue is in kde ?

BR..Abdullah Alharbi

seth · 2022-03-14 11:26:55

do you think that the issue is in kde ?

It certainly fits the pattern.
To confirm, you should not get any sort of delay when logging out of the session and shutting down/rebooting from SDDM. Only when you shut down/reboot right out of the KDE session.

We've never established what's wrong w/ KDE in this case

AbdullahAlharbi · 2022-03-14 11:51:31

it's very weird that it's happening only in "arch" or what i like to call it "native arch"
considering this, when i install manjaro or endeavourOS and choose kde i do not get this issues/messages

i have installed gnome to just make sure that the issue is from kde and not from one of the missing firmwares i shared before
or from my external hard drive because i saw "unmount /oldroot" and i thought that was from it

in fact in gnome i do not see these messages at all and also the shutdown/reboot is quick and i don't need to wait 1m 30s:

watchdog: watchdog0 did not stop!
sd-umount[1961]: failed to unmount /oldroot: device or resource is busy
sd-umount[1964]: failed to unmount /oldroot/sys: device or resource is busy
shutdown[1]: could not detach DM /dev/dm-0: Device or resource busy
shutdown[1]: failed to finalize file systems, DM devices, ignoring.

thank you so much for great help and support,
i hope kde fix this issue and i'm pretty sure they will fix it and i will go back to kde

BR..Abdullah

Arch Linux

#26 2022-03-10 07:19:01

Re: issue during shutdown/rebooting the system

#27 2022-03-10 07:21:15

Re: issue during shutdown/rebooting the system

#28 2022-03-10 07:36:25

Re: issue during shutdown/rebooting the system

#29 2022-03-10 07:52:37

Re: issue during shutdown/rebooting the system

#30 2022-03-10 22:58:40

Re: issue during shutdown/rebooting the system

#31 2022-03-11 06:57:15

Re: issue during shutdown/rebooting the system

#32 2022-03-12 06:52:10

Re: issue during shutdown/rebooting the system

#33 2022-03-12 07:05:10

Re: issue during shutdown/rebooting the system

#34 2022-03-12 08:44:41

Re: issue during shutdown/rebooting the system

#35 2022-03-12 10:02:15

Re: issue during shutdown/rebooting the system

#36 2022-03-12 10:57:18

Re: issue during shutdown/rebooting the system

#37 2022-03-12 11:57:37

Re: issue during shutdown/rebooting the system

#38 2022-03-12 12:04:37

Re: issue during shutdown/rebooting the system

#39 2022-03-12 12:28:36

Re: issue during shutdown/rebooting the system

#40 2022-03-13 06:51:06

Re: issue during shutdown/rebooting the system

#41 2022-03-13 10:05:54

Re: issue during shutdown/rebooting the system

#42 2022-03-14 08:00:54

Re: issue during shutdown/rebooting the system

#43 2022-03-14 11:26:55

Re: issue during shutdown/rebooting the system

#44 2022-03-14 11:51:31

Re: issue during shutdown/rebooting the system

Board footer