After 6.10.9-200 update, workstation has stopped working

Ask Fedora
,
1

Hi

Two days ago, I updated my Workstation to 6.10.200.fc40.x86_64. During the update I noticed things beginning to slow down, until they nearly came to a halt.

I saw errors being thrown, but I was unable to capture them. I do believe there was a systemd error among them.

When I boot the desktop, it sort of works until I try to use it.

One noteworthy thing is this: Options to shut down or reboot disappear from the menu. Only Log out… is left, and it doesn’t work.

There’s no internet connection either.

I can’t reboot or do anything from the command line - I can type a single command and then it hangs. The only way to leave Fedora is by hitting the Off button on my laptop.

I have tried booting every other version I have available, including safe mode. Same thing.

For the record, it’s a dual boot Fedora Workstation / Windows 11 Pro

Hope someone has an idea of what to do?
Thanks!

2

Slow-downs are often symptom of a mass storage device issue: either running low on space or a failing device. If you don’t have current backup, that should be your first step.

We can’t help without more details of your hardware and the errors.

  • Hardware details: start by posting the output from running inxi -Fxzz in a terminal as pre-formatted text (use the </> button from the top line of the text entry panel). We may have more questions, but this may help others with similar hardware and issues find this topic.
  • Disk space: in a terminal, run df -lH and post the output as pre-formatted text.
  • Error messages: journalctl captures enormous detail, so it can be hard to find a “filter” that selects relevant details. Please look over man journalctl to see what is available. For starters, try journalctl --no-hostname -b -p 3 |cat (we don’t need to see the hostname, -b is for the current boot, -p 3 selects messages with priority 1, 2, & 3, and |cat wraps the very long lines journalctl often produces. Again, the command should be run in a terminal and the output provided as pre-formatted text.
3

I manged to boot up 6.10.8 and it appears to be running normally, for now.

\[lmss@fedora \~\]$ inxi -Fxzz
System:
Kernel: 6.10.8-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.41-37.fc40
Desktop: GNOME v: 46.4 Distro: Fedora Linux 40 (Workstation Edition)
Machine:
Type: Laptop System: LENOVO product: 20Q7CTO1WW v: ThinkPad L590
serial: <superuser required>
Mobo: LENOVO model: 20Q7CTO1WW v: SDK0J40697 WIN
serial: <superuser required> UEFI: LENOVO v: R0ZET53W (1.31 )
date: 11/14/2022
Battery:
ID-1: BAT0 charge: 32.6 Wh (100.0%) condition: 32.6/45.7 Wh (71.3%)
volts: 12.2 min: 11.1 model: Celxpert 01AV466 status: full
Device-1: hidpp_battery_0 model: Logitech Wireless Solar Keyboard K750
charge: 100% status: full
Device-2: hidpp_battery_1 model: Logitech Marathon Mouse/Performance Plus
M705 charge: 55% (should be ignored) status: discharging
CPU:
Info: quad core model: Intel Core i7-8565U bits: 64 type: MT MCP
arch: Comet/Whiskey Lake note: check rev: C cache: L1: 256 KiB L2: 1024 KiB
L3: 8 MiB
Speed (MHz): avg: 1247 high: 4600 min/max: 400/4600 cores: 1: 2980 2: 400
3: 400 4: 400 5: 400 6: 400 7: 4600 8: 400 bogomips: 31999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel WhiskeyLake-U GT2 \[UHD Graphics 620\] vendor: Lenovo
driver: i915 v: kernel arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Bison SunplusIT Integrated Camera driver: uvcvideo type: USB
bus-ID: 1-7:6
Display: wayland server: X.Org v: 24.1.2 with: Xwayland v: 24.1.2
compositor: gnome-shell driver: dri: iris gpu: i915 resolution:
1: 1920x1080\~75Hz 2: 1920x1080\~75Hz
API: OpenGL v: 4.6 vendor: intel mesa v: 24.1.7 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
Device-2: Lenovo ThinkPad Dock USB Audio
driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 1-4.2.4:10
API: ALSA v: k6.10.8-200.fc40.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.7 status: active
Network:
Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6
IF: enp0s31f6 state: down mac: <filter>
Device-2: Intel Wi-Fi 5 Wireless-AC 9x6x \[Thunder Peak\] driver: iwlwifi
v: kernel bus-ID: 05:00.0
IF: wlp5s0 state: up mac: <filter>
Bluetooth:
Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb v: 0.8
type: USB bus-ID: 1-6:11
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 5.1
lmp-v: 10
Drives:
Local Storage: total: 2.75 TiB used: 745.84 GiB (26.5%)
ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW010T8 size: 953.87 GiB
temp: 30.9 C
ID-2: /dev/sda vendor: Western Digital model: WD20JDRW-11C7VS0
size: 1.82 TiB type: USB
Partition:
ID-1: / size: 292.96 GiB used: 246.88 GiB (84.3%) fs: btrfs
dev: /dev/nvme0n1p6
ID-2: /boot size: 973.4 MiB used: 260.9 MiB (26.8%) fs: ext4
dev: /dev/nvme0n1p4
ID-3: /boot/efi size: 96 MiB used: 45.5 MiB (47.4%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 292.96 GiB used: 246.88 GiB (84.3%) fs: btrfs
dev: /dev/nvme0n1p6
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 68.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.29 GiB used: 4.15 GiB (27.2%)
Processes: 413 Uptime: 3m Init: systemd target: graphical (5)
Packages: 33 Compilers: N/A Shell: Bash v: 5.2.26 inxi: 3.3.34

lmss@fedora \~\]$ df -lH
Filsystem      Størr Brugt  Tilb Brug% Monteret på
/dev/nvme0n1p6  315G  266G   47G   86% /
devtmpfs        4,2M     0  4,2M    0% /dev
tmpfs           8,3G     0  8,3G    0% /dev/shm
efivarfs        252k  185k   63k   75% /sys/firmware/efi/efivars
tmpfs           3,3G  2,4M  3,3G    1% /run
/dev/nvme0n1p6  315G  266G   47G   86% /home
tmpfs           8,3G   17k  8,3G    1% /tmp
/dev/nvme0n1p4  1,1G  274M  677M   29% /boot
/dev/nvme0n1p1  101M   48M   53M   48% /boot/efi
tmpfs           1,7G  213k  1,7G    1% /run/user/1000
/dev/sda1       2,1T  536G  1,5T   27% /run/media/lmss/WD Backup 2

journalctl:

\[lmss@fedora \~\]$ journalctl --no-hostname -b -p 3 |cat
sep 18 14:00:12 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
sep 18 14:00:17 kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-5)
sep 18 14:00:20 kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-5)
sep 18 14:00:21 dbus-broker-launch\[1458\]: Ignoring duplicate name 'org.gnome.Epiphany.WebAppProvider' in service file '/usr/share//dbus-1/services/org.gnome.Epiphany.WebAppProvider.service'
sep 18 14:00:22 kernel: Bluetooth: hci0: Reading supported features failed (-110)
sep 18 14:00:22 kernel: Bluetooth: hci0: sending frame failed (-19)
sep 18 14:00:22 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
sep 18 14:00:24 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
sep 18 14:01:07 gdm-password\]\[2127\]: gkr-pam: unable to locate daemon control file
sep 18 14:01:08 gdm\[1362\]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
sep 18 14:01:08 dbus-broker-launch\[2232\]: Ignoring duplicate name 'org.gnome.Epiphany.WebAppProvider' in service file '/usr/share//dbus-1/services/org.gnome.Epiphany.WebAppProvider.service'
sep 18 14:01:08 systemd\[2147\]: Failed to start app-gnome-gnome\\x2dkeyring\\x2dpkcs11-2435.scope - Application launched by gnome-session-binary.
sep 18 14:01:08 systemd\[2147\]: Failed to start app-gnome-xdg\\x2duser\\x2ddirs-2456.scope - Application launched by gnome-session-binary.
sep 18 14:01:13 gdm\[1362\]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
sep 18 14:01:34 kernel: ucsi_acpi USBC000:00: GET_CONNECTOR_STATUS failed (-110)
sep 18 14:02:38 dbus-broker-launch\[2232\]: Ignoring duplicate name 'org.gnome.Epiphany.WebAppProvider' in service file '/usr/share//dbus-1/services/org.gnome.Epiphany.WebAppProvider.service'
sep 18 14:02:41 kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-5)
sep 18 14:03:28 abrt-notification\[4956\]: System encountered a non-fatal error in \__queue_work()
sep 18 14:03:52 sudo\[5158\]:     lmss : a password is required ; TTY=pts/0 ; PWD=/home/lmss ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda

Thanks for taking your time. Let me know, if you need any further

4

The inxi output is good, but we need to see the journalctl output for the boot that failed. To do that you need to supply a “boot number” after the -b, so if you haven only rebooted once since the failure, you would use -b -1 to see entries for the previous boot.

Your nvme disk has /dev/nvme0n1p6 315G 266G 47G 86% / does not have a lot of headroom. Btrfs needs extra space, and requires periodic maintenance, but we need to see the journalctl -b -1 details.

5

I would have thought that 47G is ample space, it’s like two Fedora Workstation installs :-o

Unfortunately, this is as close as I can get. When I boot into 6.10.9 Grub throws an error:

../../grub-core/fs/fshelp.c:257:file 'initramfs-6.10.9-200.fc40.x86_64.img' not found. Press any key to continue... and freezes so I have to use the off-button.

6

df predates btrfs. See BTRFS and free space. BTRFS makes tradeoff between protection from the need to repair “bitrot” damage and a need for periodic maintenance. A corrollary of Murphy’s Law is that bitrot will be discovered in an urgently needed data. It is much better to spend time on routine maintenance. Fedora has:

Description : Btrfs Assistant is a GUI management tool to make managing a Btrfs filesystem
: easier.
:
: The primary features it offers are:
:
: * An easy to read overview of Btrfs metadata
: * A simple view of subvolumes with or without Snapper/Timeshift snapshots
: * Run and monitor scrub and balance operations
: * A pushbutton method for removing subvolumes
: * A management front-end for Snapper with enhanced restore functionality
: * View, create and delete snapshots
: * Restore snapshots in a variety of situations
: * When the filesystem is mounted in a different distro
: * When booted off a snapshot
: * From a live ISO
: * View, create, edit, remove Snapper configurations
: * Browse snapshots and restore individual files
: * Browse diffs of a single file across snapshot versions
: * Manage Snapper systemd units
: * A front-end for Btrfs Maintenance
: * Manage systemd units
: * Easily manage configuration for defrag, balance and srub settings

journalctl has an option -b <N> to select records from previous boots – please read about the -b option in man journalctl.

1 Like
7

I guess I’ll make BTRFS my next weekend project! :smiley:

6.10.10 just dropped, and it works like a charm. So I’m closing this ticket.

Thank you for taking your time, I really do appreciate it.