[Solved]Xorg takes a long Time to shutdown

LyXAssembler · 2022-10-21 18:17:21

Hi,
I was having this problem for around 3 months.
When I try to shutdown or reboot it will take a very long time around 10 Minutes and show a error message about waiting for Xorg to shutdown. I already tried disabling GRUB-Framebuffer which didn’t help.

The error message is: [ 2230.4089341 shutdown(11: Waiting for process: 617 (Xorg)

Logs:
Journal: https://0x0.st/oxAU.txt
Kernel: https://0x0.st/oxTS.txt
Xorg: https://0x0.st/oxAY.0.log

Would appreciate any help.
I am not sure if this belongs to another (sub)forum so if it does please tell me.

Last edited by LyXAssembler (2022-10-22 09:26:36)

seth · 2022-10-21 19:44:07

The journal seems from a running session and not to cover any shutdown?
Try "sudo journalctl -b -1"

Edit: but you've at least netwrokmanager and systemd-networkd enabled - pick one, disable the other and post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Edit #2: iwd and wpa_supplicant are running concurrently as well and there may be no static hostname

hostnamectl

Last edited by seth (2022-10-21 19:47:09)

LyXAssembler · 2022-10-22 05:52:44

Sorry for the late answer:
Output of

 find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
fstrim.timer                             | timers.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
tor.service                              | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants

Output of

hostnamectl

shows that there is a static hostname:

 Static hostname: archlinux
       Icon name: computer-laptop
         Chassis: laptop ?
      Machine ID: 07ed4acf21144aab8a56b40a8ffbcf01
         Boot ID: 10753ab5d1d44cc198bcc92fed810068
Operating System: Arch Linux                               
          Kernel: Linux 6.0.2-arch1-1
    Architecture: x86-64
 Hardware Vendor: HP
  Hardware Model: HP ZBook Firefly 15 G7 Mobile Workstation
Firmware Version: S73 Ver. 01.09.00

seth · 2022-10-22 06:27:00

iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants

If you want to use iwd as NM backend, please disable the service and use https://wiki.archlinux.org/title/Networ … Fi_backend

Also

seth wrote:

The journal seems from a running session and not to cover any shutdown?
Try "sudo journalctl -b -1"

LyXAssembler · 2022-10-22 07:55:55

Journal: http://0x0.st/oxju.txt

seth · 2022-10-22 08:00:34

Okt 22 08:47:37 archlinux sudo[16032]: paul : TTY=pts/0 ; PWD=/home/paul ; USER=root ; COMMAND=/usr/bin/journalctl -b

seth wrote:

sudo journalctl -b -1

You're complaining about shutdown issues, journals of a running boot are obviously useless.

LyXAssembler · 2022-10-22 08:20:21

Sorry I sent the false file,
This one should be correct:
http://0x0.st/oxjl.txt

seth · 2022-10-22 08:30:38

Oct 22 10:07:15 archlinux systemd[1]: lightdm.service: State 'stop-sigterm' timed out. Killing.
Oct 22 10:07:15 archlinux systemd[1]: lightdm.service: Killing process 559 (lightdm) with signal SIGKILL.
Oct 22 10:07:15 archlinux systemd[1]: lightdm.service: Killing process 566 (Xorg) with signal SIGKILL.
Oct 22 10:07:15 archlinux systemd[1]: lightdm.service: Killing process 563 (gdbus) with signal SIGKILL.
Oct 22 10:07:15 archlinux systemd[1]: lightdm.service: Main process exited, code=killed, status=9/KILL
Oct 22 10:08:45 archlinux systemd[1]: lightdm.service: State 'final-sigterm' timed out. Killing.
Oct 22 10:08:45 archlinux systemd[1]: lightdm.service: Killing process 566 (Xorg) with signal SIGKILL.
Oct 22 10:09:02 archlinux kernel: INFO: task kworker/0:3:1159 blocked for more than 122 seconds.
Oct 22 10:09:02 archlinux kernel:       Tainted: P           OE      6.0.2-arch1-1 #1
Oct 22 10:09:02 archlinux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 22 10:09:02 archlinux kernel: task:kworker/0:3     state:D stack:    0 pid: 1159 ppid:     2 flags:0x00004000
Oct 22 10:09:02 archlinux kernel: Workqueue: kacpi_notify acpi_os_execute_deferred
Oct 22 10:09:02 archlinux kernel: Call Trace:
Oct 22 10:09:02 archlinux kernel:  <TASK>
Oct 22 10:09:02 archlinux kernel:  __schedule+0x343/0x11c0
Oct 22 10:09:02 archlinux kernel:  schedule+0x5e/0xd0
Oct 22 10:09:02 archlinux kernel:  schedule_timeout+0x11c/0x150
Oct 22 10:09:02 archlinux kernel:  __down_common+0x11a/0x230
Oct 22 10:09:02 archlinux kernel:  down+0x47/0x60
Oct 22 10:09:02 archlinux kernel:  os_acquire_mutex+0x36/0x50 [nvidia 2d40d2c6d2c08350d8412d83c82225befc5323f3]
Oct 22 10:09:02 archlinux kernel:  _nv037233rm+0xc/0x30 [nvidia 2d40d2c6d2c08350d8412d83c82225befc5323f3]
Oct 22 10:09:02 archlinux kernel:  _nv037225rm+0x15/0x20 [nvidia 2d40d2c6d2c08350d8412d83c82225befc5323f3]
Oct 22 10:09:02 archlinux kernel:  _nv038140rm+0x18d/0x1d0 [nvidia 2d40d2c6d2c08350d8412d83c82225befc5323f3]
Oct 22 10:09:02 archlinux kernel:  rm_system_event+0x47/0x110 [nvidia 2d40d2c6d2c08350d8412d83c82225befc5323f3]
Oct 22 10:09:02 archlinux kernel:  acpi_ev_notify_dispatch+0x4b/0x63
Oct 22 10:09:02 archlinux kernel:  acpi_os_execute_deferred+0x17/0x30
Oct 22 10:09:02 archlinux kernel:  process_one_work+0x1c4/0x380
Oct 22 10:09:02 archlinux kernel:  worker_thread+0x51/0x390
Oct 22 10:09:02 archlinux kernel:  ? rescuer_thread+0x3b0/0x3b0
Oct 22 10:09:02 archlinux kernel:  kthread+0xdb/0x110
Oct 22 10:09:02 archlinux kernel:  ? kthread_complete_and_exit+0x20/0x20
Oct 22 10:09:02 archlinux kernel:  ret_from_fork+0x1f/0x30
Oct 22 10:09:02 archlinux kernel:  </TASK>
Oct 22 10:10:15 archlinux systemd[1]: lightdm.service: Processes still around after final SIGKILL. Entering failed mode.

This seems to hinge on the nvidia ./. 6.0.x ACPI changes - do you get the same problem w/ the LTS kernel?

LyXAssembler · 2022-10-22 09:26:13

No with LTS it works,
Thanks for the help

Arch Linux

#1 2022-10-21 18:17:21

[Solved]Xorg takes a long Time to shutdown

#2 2022-10-21 19:44:07

Re: [Solved]Xorg takes a long Time to shutdown

#3 2022-10-22 05:52:44

Re: [Solved]Xorg takes a long Time to shutdown

#4 2022-10-22 06:27:00

Re: [Solved]Xorg takes a long Time to shutdown

#5 2022-10-22 07:55:55

Re: [Solved]Xorg takes a long Time to shutdown

#6 2022-10-22 08:00:34

Re: [Solved]Xorg takes a long Time to shutdown

#7 2022-10-22 08:20:21

Re: [Solved]Xorg takes a long Time to shutdown

#8 2022-10-22 08:30:38

Re: [Solved]Xorg takes a long Time to shutdown

#9 2022-10-22 09:26:13

Re: [Solved]Xorg takes a long Time to shutdown

Board footer