PC freezes at reboot

[Noroc]

I have been getting the follow message for a while every other time I reboot.

Any idea why it freezes at this point.

I have seen the same issue when I tell it to shutdown.

Below is what is running

[thefrog]

Start by getting and viewing the logs and posting relevant information.

https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

[Noroc]

You need everyone of those logs or something more specific?

journalctl -b -0 | grep fail
Apr 03 19:05:20 box kernel: ACPI: _OSC evaluation for CPUs failed, trying _PDC
Apr 03 19:05:20 box kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Apr 03 19:05:23 box kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Apr 03 19:05:23 box kernel: cfg80211: failed to load regulatory.db
Apr 03 19:05:24 box kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
Apr 03 19:05:24 box dbus-broker-launch[673]: Activation request for ‘org.freedesktop.resolve1’ failed: The systemd unit ‘dbus-org.freedesktop.resolve1.service’ could not be found.
Apr 03 19:05:27 box dbus-broker-launch[673]: Activation request for ‘org.freedesktop.home1’ failed: The systemd unit ‘dbus-org.freedesktop.home1.service’ could not be found.
Apr 03 19:05:30 box dbus-broker-launch[673]: Activation request for ‘org.freedesktop.ModemManager1’ failed: The systemd unit ‘dbus-org.freedesktop.ModemManager1.service’ could not be found.
“Could not activate remote peer: activation request failed: unknown unit.”
Apr 03 19:05:30 box org_kde_powerdevil[1176]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed “Charge thresholds are not supported by the kernel for this hardware”
Apr 03 19:05:30 box org_kde_powerdevil[1176]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
Apr 03 19:05:32 box org_kde_powerdevil[1176]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed “Charge thresholds are not supported by the kernel for this hardware”
/usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/dri, suffix _dri)
Apr 03 19:05:59 box bluetoothd[677]: src/service.c:btd_service_connect() a2dp-source profile connect failed for C8:7B:23:A4:5F:B5: Device or resource busy
Apr 03 19:06:28 box bluetoothd[677]: src/service.c:btd_service_connect() a2dp-source profile connect failed for C8:7B:23:A4:5F:B5: Device or resource busy
Apr 03 19:06:31 box bluetoothd[677]: src/service.c:btd_service_connect() a2dp-source profile connect failed for C8:7B:23:A4:5F:B5: Device or resource busy
Apr 03 19:06:36 box bluetoothd[677]: src/service.c:btd_service_connect() a2dp-source profile connect failed for C8:7B:23:A4:5F:B5: Device or resource busy
Apr 03 19:06:59 box bluetoothd[677]: src/service.c:btd_service_connect() a2dp-source profile connect failed for C8:7B:23:A4:5F:B5: Device or resource busy
Apr 03 19:07:11 box bluetoothd[677]: src/service.c:btd_service_connect() a2dp-source profile connect failed for C8:7B:23:A4:5F:B5: Device or resource busy
Apr 03 19:26:44 box NetworkManager[793]: [1712186804.9746] ndisc[0x5fc6669282c0,“wlan0”]: solicit: failure sending router solicitation: Operation not permitted (1)
Apr 03 19:36:15 box gameoverlayui[3833]: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed
Apr 03 19:36:43 box NetworkManager[793]: [1712187403.9745] ndisc[0x5fc6669282c0,“wlan0”]: solicit: failure sending router solicitation: Operation not permitted (1)
Apr 03 19:42:39 box gameoverlayui[3903]: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed
Apr 03 20:49:06 box kwin_wayland[954]: kwin_wayland_drm: Setting dpms mode failed!
Apr 03 20:49:06 box kwin_wayland[954]: kwin_wayland_drm: Setting dpms mode failed!
Apr 03 20:49:24 box unix_chkpwd[4939]: password check failed for user (box)
Apr 03 20:49:24 box kscreenlocker_greet[4369]: pam_unix(kde:auth): authentication failure; logname=box uid=1000 euid=1000 tty= ruser= rhost= user=box
Apr 03 20:53:16 box kwin_wayland[954]: kwin_wayland_drm: atomic commit failed: Invalid argument
Apr 03 20:53:16 box kwin_wayland[954]: kwin_wayland_drm: atomic commit failed: Invalid argument
Apr 03 20:53:16 box kwin_wayland[954]: kwin_wayland_drm: atomic commit failed: Invalid argument
Apr 03 20:53:16 box kwin_wayland[954]: kwin_wayland_drm: atomic commit failed: Invalid argument
Apr 03 21:01:31 box bluetoothd[677]: src/service.c:btd_service_connect() a2dp-source profile connect failed for C8:7B:23:B3:2A:B3: Device or resource busy

[pebcak]

There have been a few reports about similar issue on the forum. If I have understood it it correctly, it is about a kernel regression which affects systems with Intel Wi-Fi 6 AX200.

This should have already been fixed in the next kernel which is in the testing repo at the moment.

Endeavouros did not reboot or shutdown (watchdog0 did not restart - SP5000 TCO)r

Hello everybody, Here is the issue while rebooting: [image] i m facing a weird issue. The last row that appears is that the system has umounted all the filesystems and swap saying “Rebooting”… i don’t get out of there, systems doesn’t reboot or shutdown. I didn’t run endeavouros per months. I did update yesterday, had to chroot to repair grub, also fixed a not synching pacman issue, and never faced an issue like this. I have followed this advice: New install with new Radeon 7800XT, PC won'…

System hangs on shutdown and reboot. Audio broken

Hi all, I am aware we have similar threads these days. I briefly browsed through them, but none seems to fit my case. I am on a Thinkpad X280 (pure Intel Kaby Lake R stack), running EndeavorOS KDE with linux-lts kernel and doing full system updates about 2-3 times a week. After one of the last system updates (I could not tell which exactly, around 29th/30th-ish) the system would not properly shutdown (and neither reboot) any more. It gets stuck with the following messages (“Not all DM devices…

[Noroc]

Thank you

[pebcak]

You are welcome!

I can see that both the LTS and the latest stable kernels are still in the core-testing repo.

It’s just a question of time before they hit the regular core repo. Hopefully this “annoying” issue of getting stuck on reboot and shutdown will be resolved.