Shutdown and reboot hang

Question

9 times out of 10 my computer would take ≅ 2 minutes to shutdown or reboot. I tried many things like adding systemd and/or shutdown to initcpio hooks, but no luck.

reboot -f never hangs so I followed these steps to debug. After adding the options /proc/cmdline becomes

initrd=\intel-ucode.img initrd=\initramfs-linux.img root=PARTUUID=d596f77d-aafa-479f-ad3c-df9e7c91fc7b rw quiet systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on enforcing=0

and debug.sh

#!/bin/sh
mount -o remount,rw /
dmesg > /shutdown-log.txt
mount -o remount,ro /

To my surprise this greatly reduced the number of hangs but I managed to fill shutdown-log.txt on reboot: https://gist.github.com/MatTheCat/99498b006651110462f3488dcb454b40

Here is shutdown-log.txt when reboot is fine: https://gist.github.com/MatTheCat/77f168927008bb0b886bb944d19337f1

Computer is a Dell XPS 13 9380.

$ lspci
00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30)
00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 9de8 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 9de9 (rev 30)
00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller (rev 30)
00:1c.0 PCI bridge: Intel Corporation Device 9dbe (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 9db4 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30)
00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30)
00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30)
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
02:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
03:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
03:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
03:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02)
38:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02)
6d:00.0 Non-Volatile memory controller: SK hynix Device 1527

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0489:e0a2 Foxconn / Hon Hai 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

---

Seems to match https://bugs.archlinux.org/index.php?do=details&task_id=50420 because of

[ 2144.333960] systemd-shutdown[1]: Sending SIGTERM to remaining
...
[ 2234.342297] systemd-shutdown[1]: Sending SIGKILL to PID 306 (lvmetad).

Investigating.

Solution

Setting use_lvmetad to 0 instead of 1 in /etc/lvm/lvm.conf works around the issue. I have no idea what's going on so I just hope this won't cause any issue since I'm not using LVM.

I'm still open to any explanation.

---

It's been some time since I wrote this so I tried to reset use_lvmetad.

$ lvm version
  LVM version:     2.02.185(2) (2019-05-13)
  Library version: 1.02.158 (2019-05-13)
  Driver version:  4.40.0

$ systemctl --version
systemd 242 (242.84-1-arch)

Can't see any issue after about ten reboots. Keeping my fingers crossed.

Comments

[Rui F Ribeiro]

Please add to the question the out of cat /proc/cmdline

[MatTheCat]

@RuiFRibeiro done

[Rui F Ribeiro]

Nothing out of ordinary there. lspci and lsusb might be useful. Also model and brand of notebook

[MatTheCat]

I reproduced the hang; seems to be random. I edited my question accordingly.

[Kusalananda]

This doesn't really solve the issue, it's only a workaround that may not even work for the user with the question. Could you, for example, say something about why this would be the correct solution for this particular user?