Turning off the pc does not work

General system Kernel, boot, graphics & hardware
41

If you want to hunt down the issue, I suggest you start from a clear state and add things up one by one.
I mean, remove extra CMDLINE entries from grub and module(s) from mkinitcpio MODULES array. Also add the common watchdog module(s), like iTCO_wdt in blacklist (/etc/modprobe.d/watchdog.conf), as Archwiki reports the grub method sometimes doesn’t work.
Built kernel(s) and reboot. Then shutdown.
If it fails to shutdown, reboot and check previous journal finishing part, for signs of the running/holding reasons (you might post that part to a pastebin and share).

Next time, please, post a complete inxi (inxi -Faz).

42

@petsam

$ inxi -Faz
System:
  Kernel: 5.15.14-hardened1-1-hardened x86_64 bits: 64 compiler: gcc
    v: 11.1.0 parameters: pti=on page_alloc.shuffle=1
    BOOT_IMAGE=/boot/vmlinuz-linux-hardened
    root=UUID=414f6e6c-8604-4d9c-b648-fc027c3a70d2 rw quiet loglevel=3
    acpi=off pci=nomsi,noaer nowatchdog
  Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: xfwm 4.16.1
    vt: 7 dm: LightDM 1.30.0 Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B365M DS3H v: x.x
    serial: <superuser required> UEFI: American Megatrends v: F5
    date: 08/13/2019
CPU:
  Info: model: Intel Core i5-9400 bits: 64 type: MCP arch: Coffee Lake
    family: 6 model-id: 0x9E (158) stepping: 0xD (13) microcode: 0xEA
  Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB
    desc: 1x9 MiB
  Speed (MHz): avg: 800 min/max: 800/4100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
    bogomips: 34814
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  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 and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
  Type: srbds mitigation: TSX disabled
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Gigabyte driver: nvidia
    v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1f82
    class-ID: 0300
  Display: x11 server: X.Org 1.21.1.3 compositor: xfwm4 v: 4.16.1 driver:
    loaded: nvidia unloaded: fbdev,modesetting,vesa alternate: nouveau,nv
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3")
    s-diag: 583mm (23")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 102
    size: 480x270mm (18.9x10.6") diag: 551mm (21.7")
  Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
    class-ID: 0403
  Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel
    bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403
  Sound Server-1: ALSA v: k5.15.14-hardened1-1-hardened running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.43 running: no
Network:
  Device-1: Realtek RTL8188EE Wireless Network Adapter driver: rtl8188ee
    v: kernel port: d000 bus-ID: 04:00.0 chip-ID: 10ec:8179 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: N/A modules: r8169 port: c000 bus-ID: 07:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  Device-3: 802.11g Adapter [Linksys WUSB54GC v3] WUSB54GC v3 802.11g
    Adapter [Ralink RT2070L]
    type: USB driver: rt2800usb bus-ID: 1-1:2 chip-ID: 1737:0077
    class-ID: 0000 serial: <filter>
  IF: wlan1 state: up mac: <filter>
Drives:
  Local Storage: total: 894.26 GiB used: 17.2 GiB (1.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WDS480G2G0A-00JH30 size: 447.13 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0400
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WDS480G2G0A-00JH30 size: 447.13 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0400
    scheme: GPT
Partition:
  ID-1: / raw-size: 222.27 GiB size: 222.16 GiB (99.95%)
    used: 17.2 GiB (7.7%) fs: xfs dev: /dev/sdb5 maj-min: 8:21
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 300 KiB (0.1%) fs: vfat dev: /dev/sdb4 maj-min: 8:20
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A gpu: nvidia temp: 42 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 57%
Info:
  Processes: 212 Uptime: 0m wakeups: 0 Memory: 15.58 GiB
  used: 887.5 MiB (5.6%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 Packages: pacman: 886 lib: 238 Shell: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.11


$ cat /etc/modprobe.d/watchdog.conf
iTCO_wdt
43

Why did you add these? Explain, please.

Acpi may be related. I know it is required in some cases, but not unjustified and after a best approach assessment for an existing issue.

44

This won’t fix it but may act as a workaround. Try editing /etc/systemd/system.conf

#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s

Change it to this:

DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

You could also try using the nvidia-dkms driver instead of nvidia. Then add the shutdown hook to your mkinitcpio to force the driver module unload at shutdown

45

For the reason that when I installed EOS or Mageia or Fedora and other distros, when I rebooted I got a cascade effect both acpi and dbus when starting the newly installed system → https://www.zeppelinux.es/mensaje-de-er … corrected/
https://www.kernel.org/doc/html/latest/ … eters.html

46

I will try again later. Thank you.

47

This is not exactly clear, but I suggest you remove acpi=off unless you have a proven benefit. But still, you have to balance benefits from those params. They are not without consequences.

48

also see for update version bios

see Bios > F7 Read before

1 Like
49

On my Intel system with Nvidia i do not have this file

cat /etc/modprobe.d/watchdog.conf
50

[quote=“Resiliencia, post:45, topic:20398, full:true”]

The acpi=off is disabling power managment. On a desktop it isn’t a huge deal. You might find lifetime of some components impacted, like SSD and CPU. But most likely negligible. It’s just going to mostly be an increase in power consumption. Still worth looking into fixing probably.

The pci=nomsi,noaer was most likely added for pci bus errors. The nomsi is disabling message signal interrupts on all devices and is not ideal. The noaer is just suppressing the message/logging and not fixing anything; the issue is still happening just not showing in logs.

I would remove both and depending on the bus errors you were receiving:
Try pci=nommconf That will revert to more traditional handling of the memory management configuration space. Might result in slight performance decrease.
Or, pcie_aspm=off That will disable the advanced state power management. Which would result in less power usage efficiency, but less of a concern on a desktop

1 Like
51

It does not work with either 10s or 5s.

I already did this in the beginning of this installation, because without nvidia-dkms I could not use the kernel-hardened.

Also, without success.

52

@KDen

I have removed them both, to no avail.

53

@Resiliencia
I don’t have the watchdog conf.file.

1 Like
54

There is no need for that file at all, I have already deleted it.
They are files that I am proving as they give me help in the forum.

1 Like
55

Well, I’m ending this post as all the information that could not be resolved.
I thank everyone who helped me !!!

56

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.