issue during shutdown/rebooting the system

AbdullahAlharbi · 2022-03-08 15:23:54

hello guys,

i'm new in arch linux and i noticed this when ever i shutdown the system or rebooting the system:

__common_interrupt: 1.55 No irq handler for vector
__common_interrupt: 2.55 No irq handler for vector
__common_interrupt: 3.55 No irq handler for vector
__common_interrupt: 4.55 No irq handler for vector
__common_interrupt: 5.55 No irq handler for vector
__common_interrupt: 6.55 No irq handler for vector
__common_interrupt: 7.55 No irq handler for vector
__common_interrupt: 8.55 No irq handler for vector
__common_interrupt: 9.55 No irq handler for vector
__common_interrupt: 10.55 No irq handler for vector
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.

how i can fix these errors ?

some informations about my system:

[rx@localhost ~]$ inxi -Fazy
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "en_US:ar",
        LC_ALL = (unset),
        LC_MONETARY = "en_US.UTF-8",
        LC_MEASUREMENT = "ar_SA.UTF-8",
        LC_TIME = "en_US.UTF-8",
        LC_NUMERIC = "en_US.UTF-8",
        LANG = "ar_SA.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
System:
  Kernel: 5.16.12-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-linux
    root=/dev/mapper/volgroup0-lv_root rw loglevel=3 quiet
  Desktop: KDE Plasma 5.24.3 tk: Qt 5.15.3 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0
    serial: <superuser required> UEFI: American Megatrends v: A.50
    date: 08/07/2020
CPU:
  Info: model: AMD Ryzen 9 3900XT bits: 64 type: MT MCP arch: Zen 2
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 4x16 MiB
  Speed (MHz): avg: 2796 high: 4667 min/max: 2200/4776 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2063 2: 3599
    3: 2132 4: 3973 5: 3540 6: 4410 7: 2157 8: 2197 9: 3058 10: 2200 11: 2200
    12: 2200 13: 2175 14: 4081 15: 2038 16: 4667 17: 2088 18: 4365 19: 2117
    20: 2177 21: 3075 22: 2199 23: 2199 24: 2199 bogomips: 182489
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP:
    conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Micro-Star MSI
    driver: nvidia v: 510.54 alternate: nouveau,nvidia_drm pcie: gen: 2
    speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 2d:00.0
    chip-ID: 10de:1e84 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 93 s-size: 524x292mm (20.6x11.5")
    s-diag: 600mm (23.6")
  Monitor-1: DP-0 res: 1920x1080 dpi: 94 size: 521x293mm (20.5x11.5")
    diag: 598mm (23.5")
  OpenGL: renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.54 direct render: Yes
Audio:
  Device-1: NVIDIA TU104 HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 2d:00.1
    chip-ID: 10de:10f8 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Kingston HyperX Cloud II Wireless type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-2:2 chip-ID: 0951:1718
    class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k5.16.12-arch1-1 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 27:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp39s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 28:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:3
    chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 931.51 GiB used: 24.39 GiB (2.6%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 42.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 40 GiB size: 39.08 GiB (97.69%) used: 13.23 GiB (33.9%)
    fs: ext4 dev: /dev/dm-0 maj-min: 254:0 mapped: volgroup0-lv_root
  ID-2: /home raw-size: 891.02 GiB size: 875.96 GiB (98.31%)
    used: 11.16 GiB (1.3%) fs: ext4 dev: /dev/dm-1 maj-min: 254:1
    mapped: volgroup0-lv_home
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Info:
  Processes: 404 Uptime: 43m wakeups: 0 Memory: 31.34 GiB
  used: 5.57 GiB (17.8%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 Packages: pacman: 909 lib: 277 Shell: Bash v: 5.1.16
  running-in: konsole inxi: 3.3.13

uname and lsblk output :

[rx@localhost ~]$ uname -a
Linux localhost 5.16.12-arch1-1 #1 SMP PREEMPT Wed, 02 Mar 2022 12:22:51 +0000 x86_64 GNU/Linux
[rx@localhost ~]$ lsblk
NAME                  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1               259:0    0 931.5G  0 disk 
|-nvme0n1p1           259:1    0   500M  0 part 
`-nvme0n1p2           259:2    0   931G  0 part 
  |-volgroup0-lv_root 254:0    0    40G  0 lvm  /
  `-volgroup0-lv_home 254:1    0   891G  0 lvm  /home

best regards..Abdullah.

Last edited by AbdullahAlharbi (2022-03-08 15:28:00)

seth · 2022-03-08 16:39:16

perl: warning: Setting locale failed.

(Probably) unrelated, but please the output of

localectl
locale
locale -a

About the error, something™ maintains an open file handle on the root device - could be some rogue/zombit process, could be the kernel itself.
The problem is ahead of the posted segment and likely shows after the shutdown is initiated.

sudo journalctl -b -1

to inspect the previous boot itr.

Since this looks like plasma: do you have the same issues when you log out of plasma and shut down the system from your DM (probably SDDM)?

AbdullahAlharbi · 2022-03-08 16:53:43

seth wrote:

perl: warning: Setting locale failed.
(Probably) unrelated, but please the output of
localectl
locale
locale -a
About the error, something™ maintains an open file handle on the root device - could be some rogue/zombit process, could be the kernel itself.
The problem is ahead of the posted segment and likely shows after the shutdown is initiated.
sudo journalctl -b -1
to inspect the previous boot itr.
Since this looks like plasma: do you have the same issues when you log out of plasma and shut down the system from your DM (probably SDDM)?

thank you so much for having a look into this i really appreciate your time to help me debug / and fix this

the outputs of the locale commands:

[rx@localhost ~]$ localectl
   System Locale: LANG=C
       VC Keymap: n/a
      X11 Layout: n/a
[rx@localhost ~]$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=ar_SA.UTF-8
LC_CTYPE="ar_SA.UTF-8"
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="ar_SA.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="ar_SA.UTF-8"
LC_PAPER="ar_SA.UTF-8"
LC_NAME="ar_SA.UTF-8"
LC_ADDRESS="ar_SA.UTF-8"
LC_TELEPHONE="ar_SA.UTF-8"
LC_MEASUREMENT=ar_SA.UTF-8
LC_IDENTIFICATION="ar_SA.UTF-8"
LC_ALL=
[rx@localhost ~]$ locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX
en_US.utf8
[rx@localhost ~]$

as for this command

sudo journalctl -b -1

you can find the output here:
https://pastebin.com/mZhHBTwn

AbdullahAlharbi · 2022-03-08 17:02:53

sorry i did not notice the last question:

seth wrote:

Since this looks like plasma: do you have the same issues when you log out of plasma and shut down the system from your DM (probably SDDM)?

yes i do see them when i restart or shutdown

AbdullahAlharbi · 2022-03-08 17:23:20

sorry again

i have did the same as you suggested log out and then shut down from sddm ui

after i did that and logged in again this is what happened:

1. there was an output in the screen after i clicked "shutdown" but it was so fast that i could not read anything nor take a picture
2. i noticed my refresh rate was resetted to 60hz altho my monitor support 144hz, so i set it back from the settings

Last edited by AbdullahAlharbi (2022-03-08 17:27:34)

AbdullahAlharbi · 2022-03-08 17:32:35

this is another pastebin for the command: "sudo journalctl -b -1" after i did what you suggested

https://pastebin.com/Bf7ReVgZ

Last edited by AbdullahAlharbi (2022-03-08 17:32:52)

mcloaked · 2022-03-08 17:34:22

The set of lines with

__common_interrupt: 1.55 No irq handler for vector

is common with newer AMD Ryzen systems - I had those when I first got my Ryzen machine, and only a BIOS/EFI firmware update eventually made those lines on boot go away. I believe those specific lines are benign though.

The lines following that set are not related and a separate issue.

Last edited by mcloaked (2022-03-08 17:36:25)

AbdullahAlharbi · 2022-03-08 17:39:20

mcloaked wrote:

The set of lines with
__common_interrupt: 1.55 No irq handler for vector
is common with newer AMD Ryzen systems - I had those when I first got my Ryzen machine, and only a BIOS/EFI firmware update eventually made those lines on boot go away. I believe those specific lines are benign though.

thank you so much i have been looking for these and found some interesting stuff about them
i will update BIOS later when fixing the main problems:

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.

Scimmia · 2022-03-08 17:56:15

Not your issue, but definitely fix your locale. You have some things set to use ar_SA.UTF-8, but you didn't generate that locale.

AbdullahAlharbi · 2022-03-08 18:02:01

Scimmia wrote:

Not your issue, but definitely fix your locale. You have some things set to use ar_SA.UTF-8, but you didn't generate that locale.

when i was installing arch linux i have did this:
open up this file: /etc/locale.gen

and then i uncommented this: en_US.UTF-8 UTF-8
and also i uncommented this: ar_SA.UTF-8 UTF-8

and finally i run:
locale-gen

and then that actually what break the locale
so i went back to the same file and comment out: ar_SA.UTF-8 UTF-8
and run the command again: locale-gen

but still that did not solve the problem ;(

the reason is i thought it's required in order to have the arabic keyboard layout

Last edited by AbdullahAlharbi (2022-03-08 18:03:54)

Scimmia · 2022-03-08 18:03:05

That didn't break the locale. What you did to attempt to fix it broke the locale.

AbdullahAlharbi · 2022-03-08 18:04:56

Scimmia wrote:

That didn't break the locale. What you did to attempt to fix it broke the locale.

lol do you have any suggestions on fixing this ?

i would really appreciate it

Scimmia · 2022-03-08 18:05:37

Fixing what? As I said, this is unrelated to your shutdown issues, but still needs fixed. If you want to use ar_SA.UTF-8, you have to generate it.

AbdullahAlharbi · 2022-03-08 18:09:09

Scimmia wrote:

Fixing what? As I said, this is unrelated to your shutdown issues, but still needs fixed. If you want to use ar_SA.UTF-8, you have to generate it.

ik its not related but do you mean uncomment the ar_SA.UTF-8 UTF-8 and then generate locale again ?

AbdullahAlharbi · 2022-03-08 20:15:51

AbdullahAlharbi wrote:

Scimmia wrote:
Fixing what? As I said, this is unrelated to your shutdown issues, but still needs fixed. If you want to use ar_SA.UTF-8, you have to generate it.
ik its not related but do you mean uncomment the ar_SA.UTF-8 UTF-8 and then generate locale again ?

update: i have fixed the locale issue

outputs:

[rx@localhost ~]$ localectl
   System Locale: LANG=en_US.UTF-8
       VC Keymap: n/a
      X11 Layout: n/a
[rx@localhost ~]$ locale
LANG=ar_SA.UTF-8
LC_CTYPE="ar_SA.UTF-8"
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="ar_SA.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="ar_SA.UTF-8"
LC_PAPER="ar_SA.UTF-8"
LC_NAME="ar_SA.UTF-8"
LC_ADDRESS="ar_SA.UTF-8"
LC_TELEPHONE="ar_SA.UTF-8"
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION="ar_SA.UTF-8"
LC_ALL=
[rx@localhost ~]$ locale -a
ar_SA.utf8
C
en_US.utf8
POSIX
[rx@localhost ~]$

seth · 2022-03-08 20:51:05

While we're at fixing your system:
https://wiki.archlinux.org/title/Networ … e_hostname
https://wiki.archlinux.org/title/Networ … k_managers
(You've at least networkmanager and dhcpcd enabled, you probably want to disable dhcpcd)

The shutdown in the journal you posted in #3 and #6 actually looks uninhibited?
Notbaly there's no "shutdown[1]: could not detach DM /dev/dm-0: Device or resource busy"

AbdullahAlharbi · 2022-03-08 21:00:59

seth wrote:

While we're at fixing your system:
https://wiki.archlinux.org/title/Networ … e_hostname
https://wiki.archlinux.org/title/Networ … k_managers
(You've at least networkmanager and dhcpcd enabled, you probably want to disable dhcpcd)
The shutdown in the journal you posted in #3 and #6 actually looks uninhibited?
Notbaly there's no "shutdown[1]: could not detach DM /dev/dm-0: Device or resource busy"

yeah after i installed arch the wlan driver did not work and i was trying some stuff and one of them was dhcpd
as for why it did not work it was because i did not had linux-firmware
i will disable dhcpd

i'm sorry but what do you mean by "actually looks uninhibited" ? i did not understand

as for this:
"shutdown[1]: could not detach DM /dev/dm-0: Device or resource busy"
yes i noticed that too but the weird thing about it its showing during shutdown or restart either from kde or from sddm

AbdullahAlharbi · 2022-03-08 22:49:11

i'm sorry but could this can or might lead to the issues on the shutdown ?

==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: xhci_pci

i got this when updating the kernel

Last edited by AbdullahAlharbi (2022-03-08 22:49:35)

seth · 2022-03-09 06:58:38

i'm sorry but what do you mean by "actually looks uninhibited" ? i did not understand

There's no sign of any delay.

could this can or might lead to the issues on the shutdown

Unlikely. If you had any related device in your system, it would not work.

it its showing during shutdown or restart either from kde or from sddm

Where and when?
Also, do you perceive any "misbehavior" (please describe the symptoms) or do you just concern the messages?

AbdullahAlharbi · 2022-03-09 14:03:31

seth wrote:

There's no sign of any delay.

that's great

seth wrote:

Unlikely. If you had any related device in your system, it would not work.

i did not notice anything that did not work

seth wrote:

Where and when?
Also, do you perceive any "misbehavior" (please describe the symptoms) or do you just concern the messages?

when i click shutdown / restart this is what i get after 1/2 minutes in the screen:

https://i.ibb.co/H21phCT/2022-03-09-16-55.png

i did not notice any "misbehavior" i have concerns after i got this and i thought there might be a problem that i'm not aware of

thank you so much..

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2022-03-09 16:06:22)

seth · 2022-03-09 15:37:57

Unfortunately the photo caps the timestamps.

what i get after 1/2 minutes

"30 seconds" or "60 to 120 seconds"?
The systemd service timeout is 90 seconds.

Does the system power off afterwards?

To get us some more context, please remove the "quiet" parameter from the kernel command line.

AbdullahAlharbi · 2022-03-09 16:13:05

seth wrote:

Unfortunately the photo caps the timestamps.
what i get after 1/2 minutes
"30 seconds" or "60 to 120 seconds"?
The systemd service timeout is 90 seconds.
Does the system power off afterwards?
To get us some more context, please remove the "quiet" parameter from the kernel command line.

i don't really know the exact amount of the time

yes it does power off afterwards

alright i will see how to remove the quiet parameter
but then you need the output of "sudo journalctl -b -1" ?
or is there another command you want me to run ?

best regards.

AbdullahAlharbi · 2022-03-09 16:35:39

do you have any reference on how to remove the quiet parameter ?

thanks ...

seth · 2022-03-09 19:56:29

https://wiki.archlinux.org/title/Kernel_parameters

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 01:53:13

seth wrote:

https://wiki.archlinux.org/title/Kernel_parameters
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.

alright i have disabled the "quiet" parameter in grub and then i run grub-mkconfig

and i can confirm that now the quite parameter is disabled via this(before there was "quiet" after "loglevel=3":

[root@localhost rx]# cat /proc/cmdline  
BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw loglevel=3

i also noticed when starting the system i get a lot of stuff

now what do you need exactly ?

Best Regards..Abdullah

Arch Linux

#1 2022-03-08 15:23:54

issue during shutdown/rebooting the system

#2 2022-03-08 16:39:16

Re: issue during shutdown/rebooting the system

#3 2022-03-08 16:53:43

Re: issue during shutdown/rebooting the system

#4 2022-03-08 17:02:53

Re: issue during shutdown/rebooting the system

#5 2022-03-08 17:23:20

Re: issue during shutdown/rebooting the system

#6 2022-03-08 17:32:35

Re: issue during shutdown/rebooting the system

#7 2022-03-08 17:34:22

Re: issue during shutdown/rebooting the system

#8 2022-03-08 17:39:20

Re: issue during shutdown/rebooting the system

#9 2022-03-08 17:56:15

Re: issue during shutdown/rebooting the system

#10 2022-03-08 18:02:01

Re: issue during shutdown/rebooting the system

#11 2022-03-08 18:03:05

Re: issue during shutdown/rebooting the system

#12 2022-03-08 18:04:56

Re: issue during shutdown/rebooting the system

#13 2022-03-08 18:05:37

Re: issue during shutdown/rebooting the system

#14 2022-03-08 18:09:09

Re: issue during shutdown/rebooting the system

#15 2022-03-08 20:15:51

Re: issue during shutdown/rebooting the system

#16 2022-03-08 20:51:05

Re: issue during shutdown/rebooting the system

#17 2022-03-08 21:00:59

Re: issue during shutdown/rebooting the system

#18 2022-03-08 22:49:11

Re: issue during shutdown/rebooting the system

#19 2022-03-09 06:58:38

Re: issue during shutdown/rebooting the system

#20 2022-03-09 14:03:31

Re: issue during shutdown/rebooting the system

#21 2022-03-09 15:37:57

Re: issue during shutdown/rebooting the system

#22 2022-03-09 16:13:05

Re: issue during shutdown/rebooting the system

#23 2022-03-09 16:35:39

Re: issue during shutdown/rebooting the system

#24 2022-03-09 19:56:29

Re: issue during shutdown/rebooting the system

#25 2022-03-10 01:53:13

Re: issue during shutdown/rebooting the system

Board footer