Hello All,
I hope you are doing well. I have an issue where my framework laptop often fails to reboot under Fedora 38. This issue also existed in Fedora 37. Sometimes it works… but rarely. Most of the time it hangs and i have to press the power button to get it to shut off and then I can boot it again.
To initiate a reboot I open up Konsole and type “sudo reboot”
System Info:
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.14-300.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-1280P
Memory: 62.5 GiB of RAM
Graphics Processor: AMD Radeon RX 5700
Manufacturer: Framework
Product Name: Laptop (12th Gen Intel Core)
System Version: A8
System reboot started at
May 3 19:01:44 fedora-matt systemd-logind[1307]: The system will reboot now!
I got the relevent part of my messages logs below:
ay 3 19:01:46 fedora-matt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=
lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 3 19:01:46 fedora-matt systemd[1]: Removed slice system-systemd\x2dzram\x2dsetup.slice - Slice /system/systemd-zram-setup.
May 3 19:01:46 fedora-matt systemd[1]: Reached target shutdown.target - System Shutdown.
May 3 19:01:46 fedora-matt systemd[1]: Reached target final.target - Late Shutdown Services.
May 3 19:01:46 fedora-matt systemd[1]: systemd-reboot.service: Deactivated successfully.
May 3 19:01:46 fedora-matt systemd[1]: Finished systemd-reboot.service - System Reboot.
May 3 19:01:46 fedora-matt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit
=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 3 19:01:46 fedora-matt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=
systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 3 19:01:46 fedora-matt systemd[1]: Reached target reboot.target - System Reboot.
May 3 19:01:46 fedora-matt systemd[1]: Shutting down.
May 3 19:01:46 fedora-matt audit: BPF prog-id=70 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=69 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=61 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=60 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=56 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=55 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=54 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=65 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=64 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=63 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=72 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=71 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=58 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=57 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=74 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=73 op=UNLOAD
May 3 19:01:46 fedora-matt audit: BPF prog-id=50 op=UNLOAD
May 3 19:01:46 fedora-matt systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
May 3 19:01:46 fedora-matt systemd[1]: Watchdog running with a timeout of 10min.
May 3 19:01:46 fedora-matt kernel: watchdog: watchdog0: watchdog did not stop!
May 3 19:01:46 fedora-matt systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
May 3 19:01:46 fedora-matt systemd-shutdown[1]: Watchdog running with a timeout of 10min.
May 3 19:01:46 fedora-matt systemd-shutdown[1]: Syncing filesystems and block devices.
May 3 19:01:46 fedora-matt systemd-shutdown[1]: Sending SIGTERM to remaining processes...
May 3 19:01:46 fedora-matt systemd-journald[961]: Received SIGTERM from PID 1 (systemd-shutdow).
May 3 19:01:46 fedora-matt systemd-journald[961]: Journal stopped
May 3 19:10:10 fedora-matt systemd-journald[351]: Received SIGTERM from PID 1 (n/a).
May 3 19:10:10 fedora-matt kernel: audit: type=1404 audit(1683141010.110:4): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability network_peer_controls=1
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability open_perms=1
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability extended_socket_class=1
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability always_check_network=0
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability cgroup_seclabel=1
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability nnp_nosuid_transition=1
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability genfs_seclabel_symlinks=1
May 3 19:10:10 fedora-matt kernel: SELinux: policy capability ioctl_skip_cloexec=0
May 3 19:10:10 fedora-matt kernel: audit: type=1403 audit(1683141010.173:5): auid=4294967295 ses=4294967295 lsm=selinux res=1
May 3 19:10:10 fedora-matt systemd[1]: Successfully loaded SELinux policy in 64.588ms.
May 3 19:10:10 fedora-matt systemd[1]: RTC configured in localtime, applying delta of -420 minutes to system time.
May 3 19:10:10 fedora-matt systemd[1]: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 22.664ms.
This seems to be the relevent part here:
May 3 19:01:46 fedora-matt systemd-journald[961]: Received SIGTERM from PID 1 (systemd-shutdow).
May 3 19:01:46 fedora-matt systemd-journald[961]: Journal stopped
May 3 19:10:10 fedora-matt systemd-journald[351]: Received SIGTERM from PID 1 (n/a). ← Me pressing the power button
Is there anything I can provide that might be helpful in getting this fixed at some point? If I were to file a bug which project should I pick? I have the full log available but I don’t see a way to attach it.