F42 Workstation System randomly freezes - need to force reboot

Ask Fedora
, , , ,
1

Hey,

i am currently experiencing random freezes or system hangs, sometimes just minutes after boot. Most of the time the entire screen freezes, and i cannot move the cursor, click, or control anything via the keyboard. Sometimes Applications simply stop responding, while the OS itself seems to be “fine” at first. Either way the only way to do anything is to force reboot the system. I encountered the issue previously on the KDE version, and now on the Workstation edition too.

Heres the system information copied from the settings app:

Hardware Information:

  • Hardware Model: Lenovo Lenovo V15 G4 IRU
  • Memory: 24.0 GiB
  • Processor: 13th Gen Intel® Core™ i5-13420H × 12
  • Graphics: Intel® Graphics (RPL-P)
  • Disk Capacity: 1.0 TB

Software Information:

  • Firmware Version: MCCN30WW
  • OS Name: Fedora Linux 42 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 48
  • Windowing System: Wayland
  • Kernel Version: Linux 6.16.12-200.fc42.x86_64

I could not find any issues listed in the problem reporting app. i am not experienced enough to check any logs, let alone locate them. Trying to search for similar issues online hasnt really lead to any solution for me, all i could find were discussions about “power management settings” but i am not sure which ones, or where to change them.

Please let me know if you need any more information to help.
Thanks!

2

Post the output from inxi -Fzxx so we can see what your full set of hardware is. You can also post the output from fpaste --sysinfo --printonly.

When these crashes occur, can you switch to an alternative TTY with Ctrl+Alt+F3 and be prompted for a login? That would tell us if the entire thing has locked up solid, or it’s just a display lock up.

2 Likes
3

output of inxi -Fzxx:

System:
  Kernel: 6.16.12-200.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 15.2.1
  Console: pty pts/1 wm: gnome-shell DM: GDM Distro: Fedora Linux 42
    (Workstation Edition)
Machine:
  Type: Laptop System: LENOVO product: 83A1 v: Lenovo V15 G4 IRU
    serial: <filter> Chassis: type: 10 v: Lenovo V15 G4 IRU serial: <filter>
  Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <filter>
    part-nu: LENOVO_MT_83A1_BU_idea_FM_V15 G4 IRU UEFI: LENOVO v: MCCN35WW
    date: 07/22/2025
Battery:
  ID-1: BAT0 charge: 21.9 Wh (56.6%) condition: 38.7/38 Wh (101.9%)
    volts: 8.18 min: 7.68 model: LGC L20L2PF0 serial: <filter> charging:
    status: charging cycles: 80
  Device-1: apple_mfi_fastcharge_3-4 model: N/A serial: N/A charge: N/A
    status: N/A
CPU:
  Info: 8-core (4-mt/4-st) model: 13th Gen Intel Core i5-13420H bits: 64
    type: MST AMCP arch: Raptor Lake rev: 2 cache: L1: 704 KiB L2: 7 MiB
    L3: 12 MiB
  Speed (MHz): avg: 829 min/max: 400/4600:3400 cores: 1: 829 2: 829 3: 829
    4: 829 5: 829 6: 829 7: 829 8: 829 9: 829 10: 829 11: 829 12: 829
    bogomips: 62668
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Raptor Lake-P [UHD Graphics] vendor: Lenovo driver: i915
    v: kernel arch: Xe ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4,
    HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:a7a8
  Device-2: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-8:2 chip-ID: 13d3:54b1
  Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP-1 model: AU Optronics 0x369f res: 1920x1080 hz: 60 dpi: 143
    diag: 395mm (15.5")
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.1.9 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (RPL-P)
    device-ID: 8086:a7a8
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Raptor Lake-P/U/H cAVS vendor: Lenovo driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:51ca
  API: ALSA v: k6.16.12-200.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.9 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8852BE PCIe 802.11ax Wireless Network vendor: Lenovo
    driver: rtw89_8852be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 4000
    bus-ID: 02:00.0 chip-ID: 10ec:b852
  IF: wlp2s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: enp3s0 state: down mac: <filter>
  IF-ID-1: enp0s20f0u2c4i2 state: down mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-10:3 chip-ID: 0bda:4853
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 953.87 GiB used: 11.42 GiB (1.2%)
  ID-1: /dev/nvme0n1 vendor: KingSpec model: NE-1TB 2280 size: 953.87 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
Partition:
  ID-1: / size: 487.28 GiB used: 10.98 GiB (2.3%) fs: btrfs
    dev: /dev/nvme0n1p6
  ID-2: /boot size: 973.4 MiB used: 390.3 MiB (40.1%) fs: ext4
    dev: /dev/nvme0n1p5
  ID-3: /boot/efi size: 96 MiB used: 58.9 MiB (61.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 487.28 GiB used: 10.98 GiB (2.3%) fs: btrfs
    dev: /dev/nvme0n1p6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 24 GiB available: 23.19 GiB used: 3.1 GiB (13.4%)
    igpu: 60 MiB
  Processes: 421 Power: uptime: 2m wakeups: 0 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 15.2.1
    Shell: Sudo v: 1.9.17p1 running-in: ptyxis-agent inxi: 3.3.39
4

output of fpaste --sysinfo --printonly:

Gathering system info ..................................... 
=== fpaste 0.5.0.0 System Information ===
* OS Release (cat /etc/*-release | uniq):
     Fedora release 42 (Adams)
     NAME="Fedora Linux"
     VERSION="42 (Workstation Edition)"
     RELEASE_TYPE=stable
     ID=fedora
     VERSION_ID=42
     VERSION_CODENAME=""
     PLATFORM_ID="platform:f42"
     PRETTY_NAME="Fedora Linux 42 (Workstation Edition)"
     ANSI_COLOR="0;38;2;60;110;180"
     LOGO=fedora-logo-icon
     CPE_NAME="cpe:/o:fedoraproject:fedora:42"
     DEFAULT_HOSTNAME="fedora"
     HOME_URL="https://fedoraproject.org/"
     DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f42/"
     SUPPORT_URL="https://ask.fedoraproject.org/"
     BUG_REPORT_URL="https://bugzilla.redhat.com/"
     REDHAT_BUGZILLA_PRODUCT="Fedora"
     REDHAT_BUGZILLA_PRODUCT_VERSION=42
     REDHAT_SUPPORT_PRODUCT="Fedora"
     REDHAT_SUPPORT_PRODUCT_VERSION=42
     SUPPORT_END=2026-05-13
     VARIANT="Workstation Edition"
     VARIANT_ID=workstation
     Fedora release 42 (Adams)
     
* CPU Model (grep 'model name' /proc/cpuinfo | awk -F: '{print $2}' | uniq -c |
     sed -re 's/^ +//' ):
     12  13th Gen Intel(R) Core(TM) i5-13420H
     
* 64-bit Support (grep -q ' lm ' /proc/cpuinfo && echo Yes || echo No):
     Yes
     
* Hardware Virtualization Support (grep -Eq '(vmx|svm)' /proc/cpuinfo && echo Yes || echo No):
     Yes
     
* Kernel (uname -r):
     6.16.12-200.fc42.x86_64
     
* Kernel cmdline (cat /proc/cmdline):
     BOOT_IMAGE=(hd0,gpt5)/vmlinuz-6.16.12-200.fc42.x86_64 root=UUID=0a9e387c-ab39-40aa-a844-6ac3a23adf4f ro rootflags=subvol=root rhgb quiet
     
* Desktop(s) Running (ps -eo comm= | grep -E '(gnome-session|startkde|startactive|xfce.?-session|fluxbox|blackbox|hackedbox|ratpoison|enlightenment|icewm-session|od-session|wmaker|wmx|openbox-lxde|openbox-gnome-session|openbox-kde-session|mwm|e16|fvwm|xmonad|sugar-session|mate-session|lxqt-session|cinnamon|lxdm-session|awesome|phosh|sway|Hyperland)' ):
     gnome-session-b
     gnome-session-c
     gnome-session-b
     
* Desktop(s) Installed (ls -m /usr/share/{xsessions,wayland-sessions}/ | sed 's/\.desktop//g' ):
     /usr/share/wayland-sessions/:
     gnome-classic, gnome-classic-wayland, gnome,
     gnome-wayland
     
     /usr/share/xsessions/:
     
* Session Type (env | grep 'XDG_SESSION_TYPE' | sed 's/.*=//' ):
     wayland
     
* SELinux Status (sestatus):
     SELinux status:                 enabled
     SELinuxfs mount:                /sys/fs/selinux
     SELinux root directory:         /etc/selinux
     Loaded policy name:             targeted
     Current mode:                   enforcing
     Mode from config file:          enforcing
     Policy MLS status:              enabled
     Policy deny_unknown status:     allowed
     Memory protection checking:     actual (secure)
     Max kernel policy version:      34
     
* SELinux Errors (without results: "selinuxenabled && journalctl --no-hostname --since yesterday |grep avc: | grep -Eo comm="[^ ]+" | sort |uniq -c |sort -rn"):
     N/A

* Memory usage (free -hm):
                    total        used        free      shared  buff/cache   available
     Mem:            23Gi       3.1Gi        17Gi       617Mi       3.1Gi        20Gi
     Swap:          8.0Gi          0B       8.0Gi
     
* ZRAM usage (zramctl --output-all):
     NAME       DISKSIZE DATA COMPR ALGORITHM STREAMS ZERO-PAGES TOTAL MEM-LIMIT MEM-USED MIGRATED MOUNTPOINT
     /dev/zram0       8G   4K   80B lzo-rle                    0   12K        0B      12K       0B [SWAP]
     
* Load average (uptime):
      15:12:37 up 2 min,  2 users,  load average: 0.83, 0.53, 0.22
     
* Pressure Stall Information (grep -R . /proc/pressure/):
     /proc/pressure/io:some avg10=0.23 avg60=0.27 avg300=0.11 total=1032734
     /proc/pressure/io:full avg10=0.23 avg60=0.25 avg300=0.11 total=951908
     /proc/pressure/cpu:some avg10=0.00 avg60=0.06 avg300=0.08 total=916075
     /proc/pressure/cpu:full avg10=0.00 avg60=0.00 avg300=0.00 total=0
     /proc/pressure/irq:full avg10=0.57 avg60=0.50 avg300=0.24 total=1745205
     /proc/pressure/memory:some avg10=0.00 avg60=0.00 avg300=0.00 total=19
     /proc/pressure/memory:full avg10=0.00 avg60=0.00 avg300=0.00 total=19
     
* Top 5 CPU hogs (ps axuScnh | awk '$2!=4791' | sort -rnk3 | head -5):
         1000    2993 20.6  1.8 3549428 443720 ?      Sl   15:10   0:23 firefox
         1000    2275 13.2  0.7 1396104 193504 ?      Sl   15:10   0:19 gnome-software
            0       1 12.0  0.0  38560 21952 ?        Ss   15:09   0:20 systemd
         1000    2113 10.4  0.8 4723940 218004 ?      Ssl  15:10   0:15 gnome-shell
         1000    1947  9.2  0.0  23980 15732 ?        Ss   15:10   0:13 systemd
     
* Top 5 Memory hogs (ps axuScnh | sort -rnk4 | head -5):
         1000    2993 20.5  1.8 3549428 443720 ?      Sl   15:10   0:23 firefox
         1000    3728  3.4  1.6 3095912 393148 ?      Sl   15:11   0:02 Isolated Web Co
            0    1386  2.5  1.0 810256 261252 ?       Ssl  15:10   0:04 packagekitd
         1000    3773  6.3  0.9 2883528 237688 ?      Sl   15:11   0:04 Isolated Web Co
         1000    2113 10.4  0.8 4723940 218004 ?      Ssl  15:10   0:15 gnome-shell
     
* block devices (lsblk -o NAME,FSTYPE,SIZE,FSUSE%,MOUNTPOINT,UUID,MIN-IO,SCHED,DISC-GRAN,MODEL):
     NAME        FSTYPE   SIZE FSUSE% MOUNTPOINT UUID                                 MIN-IO SCHED DISC-GRAN MODEL
     zram0       swap       8G        [SWAP]     cca78153-44d1-444e-8fe8-ee0f407f7c7c   4096              4K 
     nvme0n1            953.9G                                                           512 none       512B NE-1TB 2280
     ├─nvme0n1p1 vfat     100M    61% /boot/efi  36C3-33D7                               512 none       512B 
     ├─nvme0n1p2           16M                                                           512 none       512B 
     ├─nvme0n1p3 ntfs   464.6G                   72EEC569EEC52667                        512 none       512B 
     ├─nvme0n1p4 ntfs     891M                   2E60EDA360ED71CF                        512 none       512B 
     ├─nvme0n1p5 ext4       1G    40% /boot      8771e262-279f-4cb2-a742-fa3202946155    512 none       512B 
     └─nvme0n1p6 btrfs  487.3G     2% /home      0a9e387c-ab39-40aa-a844-6ac3a23adf4f    512 none       512B 
     
* PCI devices (lspci -nn):
     00:00.0 Host bridge [0600]: Intel Corporation Device [8086:a716]
     00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [UHD Graphics] [8086:a7a8] (rev 04)
     00:04.0 Signal processing controller [1180]: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant [8086:a71d]
     00:06.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port [8086:a74d]
     00:0d.0 USB controller [0c03]: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller [8086:a71e]
     00:14.0 USB controller [0c03]: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller [8086:51ed] (rev 01)
     00:14.2 RAM memory [0500]: Intel Corporation Alder Lake PCH Shared SRAM [8086:51ef] (rev 01)
     00:15.0 Serial bus controller [0c80]: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 [8086:51e8] (rev 01)
     00:15.1 Serial bus controller [0c80]: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 [8086:51e9] (rev 01)
     00:16.0 Communication controller [0780]: Intel Corporation Alder Lake PCH HECI Controller [8086:51e0] (rev 01)
     00:17.0 SATA controller [0106]: Intel Corporation Alder Lake-P SATA AHCI Controller [8086:51d3] (rev 01)
     00:1d.0 PCI bridge [0604]: Intel Corporation Alder Lake PCI Express Root Port #9 [8086:51b0] (rev 01)
     00:1d.1 PCI bridge [0604]: Intel Corporation Alder Lake PCI Express x1 Root Port #10 [8086:51b1] (rev 01)
     00:1e.0 Communication controller [0780]: Intel Corporation Alder Lake PCH UART #0 [8086:51a8] (rev 01)
     00:1e.3 Serial bus controller [0c80]: Intel Corporation Alder Lake SPI Controller [8086:51ab] (rev 01)
     00:1f.0 ISA bridge [0601]: Intel Corporation Raptor Lake LPC/eSPI Controller [8086:519d] (rev 01)
     00:1f.3 Multimedia audio controller [0401]: Intel Corporation Raptor Lake-P/U/H cAVS [8086:51ca] (rev 01)
     00:1f.4 SMBus [0c05]: Intel Corporation Alder Lake PCH-P SMBus Host Controller [8086:51a3] (rev 01)
     00:1f.5 Serial bus controller [0c80]: Intel Corporation Alder Lake-P PCH SPI Controller [8086:51a4] (rev 01)
     01:00.0 Non-Volatile memory controller [0108]: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1202 (DRAM-less) [1e4b:1202] (rev 01)
     02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [10ec:b852]
     03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
     
* USB devices (lsusb):
     Bus 001 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     Bus 003 Device 002: ID 13d3:54b1 IMC Networks Integrated Camera
     Bus 003 Device 003: ID 0bda:4853 Realtek Semiconductor Corp. Bluetooth Radio
     Bus 003 Device 004: ID 05ac:12a8 Apple, Inc. iPhone 5/5C/5S/6/SE/7/8/X/XR
     Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     
* PCI Video Card (lspci |  grep -i -E 'vga' | cut -b1-7 | xargs -i lspci -vnnks {} | grep -v "<access denied>"):
     00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [UHD Graphics] [8086:a7a8] (rev 04) (prog-if 00 [VGA controller])
     	Subsystem: Lenovo Device [17aa:3f95]
     	Flags: bus master, fast devsel, latency 0, IRQ 150
     	Memory at 6000000000 (64-bit, non-prefetchable) [size=16M]
     	Memory at 4000000000 (64-bit, prefetchable) [size=256M]
     	I/O ports at 5000 [size=64]
     	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
     	Kernel driver in use: i915
     	Kernel modules: i915, xe
     
     
* GL Support (glxinfo -B | grep -E "OpenGL version|OpenGL renderer"):
     OpenGL renderer string: Mesa Intel(R) Graphics (RPL-P)
     OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.1.9
     
* DRM Information (journalctl -k -b --no-hostname | grep -o 'kernel:.*drm.*$' | cut -d ' ' -f 2- ):
     ACPI: bus type drm_connector registered
     simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
     [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
     simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
     i915 0000:00:02.0: [drm] Found alderlake_p/raptorlake_p (device ID a7a8) integrated display version 13.00 stepping E0
     i915 0000:00:02.0: [drm] Using Transparent Hugepages
     i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
     i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.49.4
     i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
     i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
     i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
     i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
     i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
     i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
     [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1
     fbcon: i915drmfb (fb0) is primary device
     i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
     
* Xorg modules (grep LoadModule /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d \" -f 2 | xargs):
     
     
* Xorg errors (without results: "grep '^\[.*(EE)' /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d ':' -f 2- "):
     N/A

* PCI Audio devices (lspci |  grep -i -E 'audio' | cut -b1-7 | xargs -i lspci -vnnks {} | grep -v "<access denied>"):
     00:1f.3 Multimedia audio controller [0401]: Intel Corporation Raptor Lake-P/U/H cAVS [8086:51ca] (rev 01)
     	Subsystem: Lenovo Device [17aa:385f]
     	Flags: bus master, fast devsel, latency 32, IRQ 153
     	Memory at 6001130000 (64-bit, non-prefetchable) [size=16K]
     	Memory at 6001000000 (64-bit, non-prefetchable) [size=1M]
     	Kernel driver in use: snd_hda_intel
     	Kernel modules: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_tgl
     
     
* Audio devices (cat /proc/asound/cards):
      0 [PCH            ]: HDA-Intel - HDA Intel PCH
                           HDA Intel PCH at 0x6001130000 irq 153
     
* User audio services (systemctl --user --no-pager status wireplumber pipewire* | sed "s/$(hostname)/ahost/"):
     ● wireplumber.service - Multimedia Service Session Manager
          Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
         Drop-In: /usr/lib/systemd/user/service.d
                  └─10-timeout-abort.conf
          Active: active (running) since Mon 2025-10-20 15:10:08 CEST; 2min 30s ago
      Invocation: f2b4f4dd34cd4da1bb96f9436fef0f33
        Main PID: 2076 (wireplumber)
           Tasks: 9 (limit: 28344)
          Memory: 6.9M (peak: 8M)
             CPU: 269ms
          CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
                  └─2076 /usr/bin/wireplumber
     
     Oct 20 15:10:08 ahost systemd[1947]: Started wireplumber.service - Multimedia Service Session Manager.
     Oct 20 15:10:08 ahost wireplumber[2076]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
     Oct 20 15:10:08 ahost wireplumber[2076]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
     Oct 20 15:10:08 ahost wireplumber[2076]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
     Oct 20 15:10:08 ahost wireplumber[2076]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
     Oct 20 15:10:08 ahost wireplumber[2076]: [0:00:20.758483974] [2076]  INFO Camera camera_manager.cpp:327 libcamera v0.4.0
     
     ● pipewire.service - PipeWire Multimedia Service
          Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
         Drop-In: /usr/lib/systemd/user/pipewire.service.d
                  └─00-uresourced.conf
                  /usr/lib/systemd/user/service.d
                  └─10-timeout-abort.conf
          Active: active (running) since Mon 2025-10-20 15:10:08 CEST; 2min 30s ago
      Invocation: 1edd29bc920543908d6c5478ce4230c1
     TriggeredBy: ● pipewire.socket
        Main PID: 2074 (pipewire)
           Tasks: 3 (limit: 28344)
          Memory: 5.5M (peak: 6.2M)
             CPU: 87ms
          CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
                  └─2074 /usr/bin/pipewire
     
     Oct 20 15:10:08 ahost systemd[1947]: Started pipewire.service - PipeWire Multimedia Service.
     
     ● pipewire.socket - PipeWire Multimedia System Sockets
          Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
          Active: active (running) since Mon 2025-10-20 15:10:07 CEST; 2min 30s ago
      Invocation: 0d6ecd1ede6b45aaab4d0bc980312c06
        Triggers: ● pipewire.service
          Listen: /run/user/1000/pipewire-0 (Stream)
                  /run/user/1000/pipewire-0-manager (Stream)
          CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket
     
     Oct 20 15:10:07 ahost systemd[1947]: Listening on pipewire.socket - PipeWire Multimedia System Sockets.
     
     ● pipewire-pulse.socket - PipeWire PulseAudio
          Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
          Active: active (running) since Mon 2025-10-20 15:10:07 CEST; 2min 30s ago
      Invocation: e4e93b8b10ad48fdbc83c35c437ad7e2
        Triggers: ● pipewire-pulse.service
          Listen: /run/user/1000/pulse/native (Stream)
          CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket
     
     Oct 20 15:10:07 ahost systemd[1947]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.
     
     ● pipewire-pulse.service - PipeWire PulseAudio
          Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
         Drop-In: /usr/lib/systemd/user/service.d
                  └─10-timeout-abort.conf
          Active: active (running) since Mon 2025-10-20 15:10:09 CEST; 2min 28s ago
      Invocation: 429876cb7cb94052ae3a4cd3ca75a195
     TriggeredBy: ● pipewire-pulse.socket
        Main PID: 2642 (pipewire-pulse)
           Tasks: 3 (limit: 28344)
          Memory: 3M (peak: 4.2M)
             CPU: 46ms
          CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
                  └─2642 /usr/bin/pipewire-pulse
     
     Oct 20 15:10:09 ahost systemd[1947]: Started pipewire-pulse.service - PipeWire PulseAudio.
     
* PCI Network devices (lspci |  grep -i -E 'net' | cut -b1-7 | xargs -i lspci -vnnks {} | grep -v "<access denied>"):
     02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [10ec:b852]
     	Subsystem: Lenovo Device [17aa:4853]
     	Flags: bus master, fast devsel, latency 0, IRQ 154
     	I/O ports at 4000 [size=256]
     	Memory at 50500000 (64-bit, non-prefetchable) [size=1M]
     	Kernel driver in use: rtw89_8852be
     	Kernel modules: rtw89_8852be
     
     03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
     	Subsystem: Lenovo Device [17aa:395d]
     	Flags: bus master, fast devsel, latency 0, IRQ 17
     	I/O ports at 3000 [size=256]
     	Memory at 50404000 (64-bit, non-prefetchable) [size=4K]
     	Memory at 50400000 (64-bit, non-prefetchable) [size=16K]
     	Kernel driver in use: r8169
     	Kernel modules: r8169
     
     
* Network status (ip -br addr | awk '{print $1" " $2}' | column -t):
     lo               UNKNOWN
     enp3s0           DOWN
     wlp2s0           UP
     enp0s20f0u2c4i2  DOWN
     
* Kernel buffer tail (journalctl --no-hostname -k --lines 50):
     Oct 20 15:09:53 kernel: Bluetooth: MGMT ver 1.23
     Oct 20 15:09:53 kernel: NET: Registered PF_QIPCRTR protocol family
     Oct 20 15:09:53 kernel: Consider using thermal netlink events interface
     Oct 20 15:09:53 kernel: RPC: Registered named UNIX socket transport module.
     Oct 20 15:09:53 kernel: RPC: Registered udp transport module.
     Oct 20 15:09:53 kernel: RPC: Registered tcp transport module.
     Oct 20 15:09:53 kernel: RPC: Registered tcp-with-tls transport module.
     Oct 20 15:09:53 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
     Oct 20 15:09:54 kernel: Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
     Oct 20 15:09:54 kernel: r8169 0000:03:00.0 enp3s0: Link is Down
     Oct 20 15:09:58 kernel: wlp2s0: authenticate with 9c:8c:d8:16:95:02 (local address=a2:09:b6:0d:2d:22)
     Oct 20 15:09:58 kernel: wlp2s0: send auth to 9c:8c:d8:16:95:02 (try 1/3)
     Oct 20 15:09:58 kernel: wlp2s0: authenticated
     Oct 20 15:09:58 kernel: wlp2s0: associate with 9c:8c:d8:16:95:02 (try 1/3)
     Oct 20 15:09:58 kernel: wlp2s0: RX AssocResp from 9c:8c:d8:16:95:02 (capab=0x421 status=0 aid=1)
     Oct 20 15:09:58 kernel: wlp2s0: associated
     Oct 20 15:10:02 kernel: rfkill: input handler disabled
     Oct 20 15:10:03 kernel: Bluetooth: RFCOMM TTY layer initialized
     Oct 20 15:10:03 kernel: Bluetooth: RFCOMM socket layer initialized
     Oct 20 15:10:03 kernel: Bluetooth: RFCOMM ver 1.11
     Oct 20 15:10:07 kernel: rfkill: input handler enabled
     Oct 20 15:10:09 kernel: rfkill: input handler disabled
     Oct 20 15:10:34 kernel: usb 3-2: new high-speed USB device number 4 using xhci_hcd
     Oct 20 15:10:34 kernel: usb 3-2: New USB device found, idVendor=05ac, idProduct=12a8, bcdDevice=14.04
     Oct 20 15:10:34 kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
     Oct 20 15:10:34 kernel: usb 3-2: Product: iPhone
     Oct 20 15:10:34 kernel: usb 3-2: Manufacturer: Apple Inc.
     Oct 20 15:10:34 kernel: usb 3-2: SerialNumber: 000081100011493A0262401E
     Oct 20 15:10:34 kernel: usbcore: registered new device driver apple-mfi-fastcharge
     Oct 20 15:10:34 kernel: ipheth 3-2:4.2: ipheth_enable_ncm: usb_control_msg: 0
     Oct 20 15:10:34 kernel: ipheth 3-2:4.2: Apple iPhone USB Ethernet device attached
     Oct 20 15:10:34 kernel: usbcore: registered new interface driver ipheth
     Oct 20 15:10:34 kernel: usbcore: registered new interface driver cdc_ether
     Oct 20 15:10:34 kernel: usbcore: registered new interface driver cdc_ncm
     Oct 20 15:10:34 kernel: ipheth 3-2:4.2 enp0s20f0u2c4i2: renamed from eth0
     Oct 20 15:11:03 kernel: wlp2s0: deauthenticating from 9c:8c:d8:16:95:02 by local choice (Reason: 3=DEAUTH_LEAVING)
     Oct 20 15:11:05 kernel: wlp2s0: authenticate with 9c:8c:d8:15:e3:62 (local address=a2:09:b6:0d:2d:22)
     Oct 20 15:11:05 kernel: wlp2s0: send auth to 9c:8c:d8:15:e3:62 (try 1/3)
     Oct 20 15:11:05 kernel: wlp2s0: authenticated
     Oct 20 15:11:05 kernel: wlp2s0: associate with 9c:8c:d8:15:e3:62 (try 1/3)
     Oct 20 15:11:05 kernel: wlp2s0: RX AssocResp from 9c:8c:d8:15:e3:62 (capab=0x421 status=0 aid=1)
     Oct 20 15:11:05 kernel: wlp2s0: associated
     Oct 20 15:11:39 kernel: wlp2s0: disconnect from AP 9c:8c:d8:15:e3:62 for new auth to 9c:8c:d8:16:95:02
     Oct 20 15:11:40 kernel: wlp2s0: authenticate with 9c:8c:d8:16:95:02 (local address=a2:09:b6:0d:2d:22)
     Oct 20 15:11:40 kernel: wlp2s0: send auth to 9c:8c:d8:16:95:02 (try 1/3)
     Oct 20 15:11:40 kernel: wlp2s0: authenticated
     Oct 20 15:11:40 kernel: wlp2s0: associate with 9c:8c:d8:16:95:02 (try 1/3)
     Oct 20 15:11:40 kernel: wlp2s0: RX ReassocResp from 9c:8c:d8:16:95:02 (capab=0x421 status=0 aid=1)
     Oct 20 15:11:40 kernel: wlp2s0: associated
     Oct 20 15:11:41 kernel: evm: overlay not supported
     
* Last few reboots (last -x -n10 reboot runlevel):
     runlevel (to lvl 5)   6.16.12-200.fc42 Mon Oct 20 15:10   still running
     reboot   system boot  6.16.12-200.fc42 Mon Oct 20 15:09   still running
     runlevel (to lvl 5)   6.16.12-200.fc42 Mon Oct 20 13:21 - 13:46  (00:25)
     reboot   system boot  6.16.12-200.fc42 Mon Oct 20 13:21 - 13:46  (00:25)
     runlevel (to lvl 5)   6.16.12-200.fc42 Mon Oct 20 11:48 - 13:21  (01:32)
     reboot   system boot  6.16.12-200.fc42 Mon Oct 20 11:48 - crash  (01:32)
     runlevel (to lvl 5)   6.16.12-200.fc42 Mon Oct 20 10:24 - 11:48  (01:24)
     reboot   system boot  6.16.12-200.fc42 Mon Oct 20 10:23 - crash  (01:24)
     runlevel (to lvl 5)   6.16.10-200.fc42 Sun Oct 19 13:11 - 10:24  (21:12)
     reboot   system boot  6.16.10-200.fc42 Sun Oct 19 13:11 - crash  (21:12)
     
     wtmp begins Mon Oct 13 23:36:50 2025
     
* DNF Repositories (dnf repolist):
     repo id                                        repo name
     code                                           Visual Studio Code
     copr:copr.fedorainfracloud.org:phracek:PyCharm Copr repo for PyCharm owned by phracek
     fedora                                         Fedora 42 - x86_64
     fedora-cisco-openh264                          Fedora 42 openh264 (From Cisco) - x86_64
     google-chrome                                  google-chrome
     rpmfusion-nonfree-nvidia-driver                RPM Fusion for Fedora 42 - Nonfree - NVIDIA Driver
     rpmfusion-nonfree-steam                        RPM Fusion for Fedora 42 - Nonfree - Steam
     updates                                        Fedora 42 - x86_64 - Updates
     
* DNF Extras (without results: "dnf -C list extras"):
     N/A

* Last 20 packages installed (rpm -qa --nodigest --nosignature --last | head -20):
     xrandr-1.5.3-2.fc42.x86_64                    Mon 20 Oct 2025 03:12:16 PM CEST
     xdpyinfo-1.3.4-2.fc42.x86_64                  Mon 20 Oct 2025 03:12:16 PM CEST
     wmctrl-1.07-39.fc42.x86_64                    Mon 20 Oct 2025 03:12:16 PM CEST
     perl-XML-Dumper-0.81-51.fc42.noarch           Mon 20 Oct 2025 03:12:16 PM CEST
     perl-Sys-Hostname-1.25-519.fc42.x86_64        Mon 20 Oct 2025 03:12:16 PM CEST
     perl-PerlIO-utf8_strict-0.010-9.fc42.x86_64   Mon 20 Oct 2025 03:12:16 PM CEST
     perl-Math-BigInt-2.0040.01-1.fc42.noarch      Mon 20 Oct 2025 03:12:16 PM CEST
     perl-IO-Compress-Brotli-0.004001-15.fc42.x86_64 Mon 20 Oct 2025 03:12:16 PM CEST
     lm_sensors-3.6.0-22.fc42.x86_64               Mon 20 Oct 2025 03:12:16 PM CEST
     libXxf86dga-1.1.6-5.fc42.x86_64               Mon 20 Oct 2025 03:12:16 PM CEST
     ipmitool-1.8.19-10.fc42.x86_64                Mon 20 Oct 2025 03:12:16 PM CEST
     inxi-3.3.39-1.fc42.noarch                     Mon 20 Oct 2025 03:12:16 PM CEST
     hddtemp-0.3-0.58.beta15.fc42.x86_64           Mon 20 Oct 2025 03:12:16 PM CEST
     freeipmi-1.6.15-3.fc42.x86_64                 Mon 20 Oct 2025 03:12:16 PM CEST
     perl-XML-Parser-2.47-6.fc42.x86_64            Mon 20 Oct 2025 03:12:15 PM CEST
     perl-WWW-RobotRules-6.02-41.fc42.noarch       Mon 20 Oct 2025 03:12:15 PM CEST
     perl-Try-Tiny-0.32-2.fc42.noarch              Mon 20 Oct 2025 03:12:15 PM CEST
     perl-Time-HiRes-1.9777-512.fc42.x86_64        Mon 20 Oct 2025 03:12:15 PM CEST
     perl-TimeDate-2.33-16.fc42.noarch             Mon 20 Oct 2025 03:12:15 PM CEST
     perl-subs-1.04-519.fc42.noarch                Mon 20 Oct 2025 03:12:15 PM CEST
     
* EFI boot manager output (efibootmgr -v):
     BootCurrent: 0000
     Timeout: 0 seconds
     BootOrder: 0000,0004,2001,2002,2003
     Boot0000* Fedora	HD(1,GPT,8acb7f79-25be-4c5f-a845-87c77c703cd1,0x800,0x32000)/\EFI\fedora\shim.efiRC
           dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 79 7f cb 8a be 25 5f 4c a8 45 87 c7 7c 70 3c d1 02 02 / 04 04 2e 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
         data: 52 43
     Boot0002* EFI PXE 0 for IPv4 (C4-EF-BB-CD-C2-57) 	PciRoot(0x0)/Pci(0x1d,0x1)/Pci(0x0,0x0)/MAC(c4efbbcdc257,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)RC
           dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 01 1d / 01 01 06 00 00 00 / 03 0b 25 00 c4 ef bb cd c2 57 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0c 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
         data: 52 43
     Boot0003* EFI PXE 0 for IPv6 (C4-EF-BB-CD-C2-57) 	PciRoot(0x0)/Pci(0x1d,0x1)/Pci(0x0,0x0)/MAC(c4efbbcdc257,0)/IPv6([::],0,Static,[::],[::],64)RC
           dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 01 1d / 01 01 06 00 00 00 / 03 0b 25 00 c4 ef bb cd c2 57 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0d 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
         data: 52 43
     Boot0004* Windows Boot Manager	HD(1,GPT,8acb7f79-25be-4c5f-a845-87c77c703cd1,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000030000100000010000000040000007fff0400
           dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 79 7f cb 8a be 25 5f 4c a8 45 87 c7 7c 70 3c d1 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
         data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 30 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
     Boot2001* EFI USB Device	RC
           dp: 7f ff 04 00
         data: 52 43
     Boot2002* EFI DVD/CDROM	RC
           dp: 7f ff 04 00
         data: 52 43
     Boot2003* EFI Network	RC
           dp: 7f ff 04 00
         data: 52 43
2 Likes
5

OK - I see you had crashes on the -2 and -3 boots. Can you please post the output from journalctl --no-hostname --no-pager -k -b -2 which should be your boot from 11:48 this morning.

If you have rebooted again before you do this you’ll need to make that -2 into -3 and so on. -b means “show me a previous boot” and the negative number means “this many reboots ago”… 0 is the current boot, -1 is the previous and so on.

If the output is too long paste in here as pre-formatted text, then amend the command to journalctl --no-hostname --no-pager -k -b -2 | fpaste and post the URL it gives you. It would be nice to have it in here for indexing purposes, but there’s a 32KB limit I believe, and you may well be larger than that!

6

Thanks for the quick answer!

Heres the log for journalctl ... -4 (matches time correctly, had a crash inbetween): UNTITLED - Pastebin Service

also looked through some of the other boots,
heres what it showed at the end for -1:

...
Oct 20 15:11:41 kernel: evm: overlay not supported
Oct 20 15:17:27 kernel: rfkill: input handler enabled
Oct 20 15:17:27 kernel: fbcon: Taking over console
Oct 20 15:17:27 kernel: Console: switching to colour frame buffer device 240x67
Oct 20 15:19:11 kernel: rfkill: input handler disabled
Oct 20 15:20:04 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0._Q38.PNOT], AE_NOT_FOUND (20250404/psargs-332)
Oct 20 15:20:04 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0._Q38 due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
Oct 20 15:20:13 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0._Q37.PNOT], AE_NOT_FOUND (20250404/psargs-332)
Oct 20 15:20:13 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0._Q37 due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
Oct 20 15:24:51 kernel: wlp2s0: disconnect from AP 9c:8c:d8:16:95:02 for new auth to 9c:8c:d8:12:fc:f1
Oct 20 15:24:51 kernel: wlp2s0: VHT information is missing, disabling VHT
Oct 20 15:24:52 kernel: wlp2s0: authenticate with 9c:8c:d8:12:fc:f1 (local address=a2:09:b6:0d:2d:22)
Oct 20 15:24:52 kernel: wlp2s0: send auth to 9c:8c:d8:12:fc:f1 (try 1/3)
Oct 20 15:24:52 kernel: wlp2s0: authenticated
Oct 20 15:24:52 kernel: wlp2s0: associate with 9c:8c:d8:12:fc:f1 (try 1/3)
Oct 20 15:24:52 kernel: wlp2s0: RX ReassocResp from 9c:8c:d8:12:fc:f1 (capab=0x1 status=0 aid=3)
Oct 20 15:24:52 kernel: wlp2s0: associated

and for -2:

Oct 20 13:46:47 kernel: rfkill: input handler enabled
Oct 20 13:46:47 kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Oct 20 13:46:48 kernel: wlp2s0: deauthenticating from 9c:8c:d8:13:0e:f1 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 20 13:46:49 kernel: kauditd_printk_skb: 5 callbacks suppressed
Oct 20 13:46:49 kernel: audit: type=1305 audit(1760960809.522:343): op=set audit_pid=0 old=866 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.525:344): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=auditd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.525:345): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.553:346): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-36C3\x2d33D7 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: EXT4-fs (nvme0n1p5): unmounting filesystem 8771e262-279f-4cb2-a742-fa3202946155.
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.575:347): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-8771e262\x2d279f\x2d4cb2\x2da742\x2dfa3202946155 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.576:348): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.577:349): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.577:350): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: zram0: detected capacity change from 16777216 to 0
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.611:351): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 20 13:46:49 kernel: audit: type=1131 audit(1760960809.617:352): 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'
Oct 20 13:46:49 kernel: watchdog: watchdog0: watchdog did not stop!
Oct 20 13:46:49 systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 6, device /dev/watchdog0
Oct 20 13:46:49 systemd-shutdown[1]: Watchdog running with a hardware timeout of 10min.
Oct 20 13:46:49 systemd-shutdown[1]: Syncing filesystems and block devices.
Oct 20 13:46:49 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Oct 20 13:46:49 systemd-journald[616]: Received SIGTERM from PID 1 (systemd-shutdow).
7

Had me a little confused there - the journal log starts at 12:23 today and then jumps back to 10:23 on line 838… so when I looked at the bottom of the file, that was not the most recent output…

OK - the next time this happens (and from your description it won’t be long) can you see if you can switch to another terminal using Ctrl-Alt+F3 (or F4, F5, F6 etc - they should all give you a new login prompt).

If you CAN do this, it probably means the i915 display driver has gone bang - your machine has not entirely crashed but it’s no longer updating the GUI so it looks like everything is frozen.

In this case, you can log in using your usual username and password and issue the command sudo shutdown -r which will reboot the machine.

When it comes back up we want to see that journal again, so do another journalctl --no-hostname --no-pager -k -b -1 | fpaste to send the previous boot (the one we just shutdown ourselves after it appeared to lock up) off to the pastebin. Hopefully, that should let us see what is causing the i915 driver to soil itself.

2 Likes
8

Okay, system completely froze again

first, one application after another stopped responding, where i get shown the dialoge “not responding, want to force quit” except force quitting doesnt work. First you cant click any buttons, then even text input fails. eventually i couldnt use system shortcuts anymore, like alt tabbing, and cursor movement stopped working last.

i could not use ctrl+alt+F3 (tried that previously, when my system didnt act up, worked fine), but i could not switch to the TTY only interface thing. had to force reboot using the power button again

heres the log: UNTITLED - Pastebin Service

Edit: about the weird timestamps: for some reason the clock on my system doesnt really work either… it sometimes jumps two hours into the future, sometimes it shows the correct time…

9

Curious about the battery – only 80 charging cycles and 101% capacity. Is this a recently installed replacement battery? Is it a real Lenovo battery from a reputable supplier?

10

not quite sure, got the laptop ~6 months ago from a reseller. didnt replace anything myself. but the battery life aint too great :smiley:

11

There’s no evidence of a crash in that journal, but that just means something crashed hard enough that any dumps and failure output didn’t make it to the disk before everything locked solidly.

I also can’t see a newer BIOS for your machine, although the version you have installed is pretty new. You could always ensure that you have the latest firmware installed anyway with sudo fwupdmgr refresh --force && sudo fwupdmgr update

If you can, I’d get into the BIOS and set the clock correctly in there if it’s not already - there are several mentions of timers and clocks being somewhat unreliable in the log, plus the “I’ll just change the time by 2 hours” looks somewhat weird at best. Set the date and time in the BIOS and if these messages still appear we’ll dig into why.

If you’d be agreeable to a little test, you can do the following:

  • Boot your machine and when grub appears select your kernel, and hit e
  • Scroll to the end of the line of parameters - you will see rhgb quiet in there. Move the cursor to the end of that line and enter acpi_osi='Windows 2017'
  • Press Ctrl-X to boo that kernel with all the power management stuff disabled. This is a one shot deal - the next reboot/start you perform will be back to normal.

Try using it like that - if you still get a crash we can try a few other options before going the for thermonuclear option of turning acpi entirely off, which will be awful but will rule power management in or out of the usual suspects.

I’m suggesting this because there’s nothing inherently obvious in these logs, mainly because whatever is exploding it doing so hard enough to prevent logging from capturing the cause. From where I sit, nothing fails, but I can see that you’re having to force reboot so it evidently is.

1 Like
12

I was about to write a quick heads-up just now on my laptop, in which I wanted to report that everything seems to be fine with those additional boot settings, but…
nope, system randomly froze again (but hey this time it rebooted on its own fairly quickly!)
…so guess those settings didn’t help either :C

A few hours ago I also did your suggested updates. Checked the windows side for firmware updates too and installed those.

An idea which struck me earlier… might a dying or broken CMOS battery cause issues like an unreliable clock, or something else, which then might lead to system instability/crashes later down the line? Or a dual boot conflict with windows?
Its not me who randomly changes the clock between the actual time or something 2 hours ahead haha. It was set correctly in the BIOS though.

On popOS I didn’t have any issues (and i ran that setup for around 4 months), but perhaps it deals with the clock or whatever else a little differently?

Thanks for your help so far though, really appreciated!
Im about to go to bed now so I wont be able to reply or test anything for the next hours…

13

A failing CMOS battery will likely show itself as the machine forgetting the date and time when powered off.

If you have the means to change it, I would do so as something evidently is not happy with the date and time on this machine and it’ll cost pennies to do. Rules it out of the issue of nothing else. Can’t hurt.

I don’t think it’ll be the root cause of your issue but I’ve spent months changing stuff out of a weirdly flaky PC only to find it was a cracked SATA cable which only failed when it got slightly warm by the machine writing to as specific drive. Sometimes weird stuff happens!

If telling the BIOS that it’s running Windows doesn’t help, you could try the opposite approach - set that kernel parameter to ‘Linux’ (the kernel tells the BIOS that it really is Windows by default, because most manufacturer only bother to write, or test code within the bios for Windows… so if you announce yourself to be Windows you’re probably running code paths to control power and so on, that has been heavily tested. It’s literally easier to pretend you’re something else than it is to rely on BIOS manufacturers to write decent code for Linux!)

Given that announcing that your machine is running windows for BIOS purposes, doesn’t make any difference, lets try the other side of the coin and wave a Linux flagf and see what happens. Can’t be any worse.

If THAT makes no difference, we can turn all acpi off entirely by passing acpi=off to the kernel. Don’t really want to do this permanently because it’ll balls up all kinds of things - battery life will be even worse, your CPU’s might be locked at a low clock-speed, sleep won’t work etc.

If that helps we can then selectively start turning back on parts of the ACPI subsystem in an effrot to at least get to the point where there’s something useful written to the end of the journal, which gives an actual clue what the root cause might be.

14

This is troubling me - this sounds like the kernel or the entire system is aware that stuff is failing/timing out/not responding, and it’s gracefully trying to sort things out and so on.

When this happens again (and it will because the boot that you’re on right now as you read this will be back to a perfectly normal start up), run the usual journalctl command but remove the -k, as in journalctl --no-hostname --no-pager -b -1 | fpaste.

No point in trying to post it here directly as it will undoubtedly be too large.

2 Likes
15

You need to check vendor documentation to see if it is OK to run the system without a battery. Poor battery life from a lightly used battery may well be a cheap low-quality battery or a well-used battery that has been reprogrammed to claim it is new. You may be experiencing effects of unstable power.

You appear to have Windows partitions. If you can boot Windows, try Lenovo Vantage battery diagnostics.

16

sorry, forgot to test the “linux” boot argument, had work on my mind today.
I managed to fix the weird clock time jumping issue though by setting both windows and fedora to use UTC instead of local time.

Unfortunately my system crashed again: UNTITLED - Pastebin Service

One of my colleagues experiences similar issues on their dualboot system. Since he has a Dell laptop I suspect its less a hardware and more a dualboot issue perhaps? He mentioned he experiences the crashes only after waking his laptop from sleep. I havent paid attention to that on my system, but at least for todays crash this seems to be true for me too. Might be a hint to solve this weird issue.

On the windows side i ran the Lenovo diagnostics, but they havent found any issues. did a full CPU and RAM check, and the battery too but everything seems fine.

1 Like
17

There’s nothing in the log that indicates anything is particularly amiss I’m afraid.

It sleeps at 13:30, it wakes up again when you open the lid at 14:24. Everything appears to wake up normally and network connectivity is resumed.

“code.desktop” (VS Code) crashes a few times - is that something which is consistent in being active when this all falls apart, as there’s nothing else in this log which looks like it’s having any issues, never mind taking out the entire machine with it.

18

Good news. If Lenovo says the system can be run without a battery present, I would still try that. A 3rd party battery is very likely designed to pass the Lenovo Vantage tests using cheap, barely good enough, parts. If the “not great” battery life is a problem, there are reputable 3rd party battery suppliers. Lenovo provides Battery Replacement Instructions.

This has 4 instances of fileWatcher, pid: PID]: crashed with code 15 reason 'killed' and differing PID’s. Visual Studio Code uses fileWatcher. This VSCode Issue sounds like what you have experienced. Does your issue ever occur when VSCode is not running?

19

hooked up my laptop via ethernet to my mac and sent kernel logs via netconsole. For the most part the logs seem fairly uninteresting but this is the part where the system crashed:

[ 9034.990848] nvme nvme0: I/O tag 643 (4283) opcode 0x9 (I/O Cmd) QID 2 timeout, aborting req_op:DISCARD(3) size:189440
[ 9060.078788] nvme nvme0: I/O tag 832 (b340) opcode 0x1 (I/O Cmd) QID 1 timeout, aborting req_op:WRITE(1) size:16384
[ 9060.078854] nvme nvme0: I/O tag 833 (6341) opcode 0x1 (I/O Cmd) QID 1 timeout, aborting req_op:WRITE(1) size:16384
[ 9065.202636] nvme nvme0: I/O tag 643 (4283) opcode 0x9 (I/O Cmd) QID 2 timeout, reset controller
[ 9256.682532] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[ 9256.688470] nvme nvme0: Abort status: 0x371
[ 9256.688489] nvme nvme0: Abort status: 0x371
[ 9256.688505] nvme nvme0: Abort status: 0x371
[ 9384.697217] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[ 9400.441991] mce: CPUs not responding to MCE broadcast (may include false positives): 2-3
[ 9400.441991] mce: CPUs not responding to MCE broadcast (may include false positives): 2-3
[ 9400.441997] Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
[ 9401.510496] Shutting down cpus with NMI
[ 9401.521202] Kernel Offset: 0x6800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

Can you maybe read into whats happening here?
Edit: i think im cooked

1 Like
20

It would appear that your nvme drive is failing - I’m not an expert (on anything really, but especially not on nvme drives!) so I had to look some of the error codes up.

The nvme0 drive stops responding, hence the timeout messages for the DISCARD and the WRITE operations.

Eventually the kernel entirely gives up talking to the drive and tries to reset the drive controller. The controller is AWOL also, and so you get the kernel panic as it can’t sync and it shuts down.

It tries to shut down all of the CPU’s but two of them aren’t responding (probably because they a pinned, waiting on a response from the nvme drive)

This would explain why there’s nothing in the logs about the crash - it was quite possibly the “I’m trying to log something” which caused the nvme drive to fall over which in turn eventually caused the kernel to shut down.

The cause of the failure actually seems to happen about 400 seconds before the lock-up/reboot/crash.

Smells like imminent hardware failure from this output - kudos for actually getting it in the first place!

  • I’d check the Smart status on the drive - see if it’s actually reporting issues with itself (smartmontools and smartctl)
  • I’d also force a check on the entire drive (boot from live USB and run a btrfs scrub on the drive).
  • Assuming the scrub is ok, I’d make sure I had a backup of anything which would cause you pain if you lost it.
  • I also not trust this drive any more - hopefully it wasn’t expensive, speaking as someone who had a barely used 1TB Samsung Evo 970 die on him last year with about 60 hours of use on it but also out of warranty.

Addendum - yep - I’d agree with cooked.