Sometimes can't connect to wifi and even freezes the desktop

I am running OpenSUSE Tumbleweed with LXQt desktop environment. I get some issues with my desktop, which sometimes is not able to activate wifi connections. On the other time, it either connects but will freeze after booting for a while or will keep disconnecting and reconnecting.

Here is some information that I provide:

inxi -MNxx
  Type: Laptop System: ASUSTeK product: VivoBook 14_ASUS Laptop X441UBR v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X441UBR v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X441UBR.310 date: 09/16/2019
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: ASUSTeK
    driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 02:00.0 chip-ID: 10ec:8136
  Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
    vendor: Lite-On driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 168c:0036
uname -r

Any help on how to diagnose the problem would be nice, especially the freeze issue and wifi problem are quite annoying.

Hi and welcome to the forums :smile:

Could you provide the outputs of:

sudo journalctl  --no-pager -p3 -b
systemd-analyze blame | head
systemd-analyze --user blame | head
sudo coredumpctl list
sudo journalctl --no-pager -b | grep -E 'wireless|wifi'
1 Like

Thank you for welcoming me.
Here are the outputs:
Note: the output of journalctl is too long, hence I paste it in Privatebin

systemd-analyze blame | head
28.332s prime-select.service
19.798s polkit.service
19.007s avahi-daemon.service
18.982s dbus.service
17.710s apparmor.service
16.800s systemd-journal-flush.service
16.250s dev-sda1.device
16.250s dev-disk-by\x2dpartuuid-240f658f\x2d1a68\x2d43b0\x2d8e88\x2d31196197b34a.device
16.250s dev-disk-by\x2did-scsi\x2d350000398e278234a\x2dpart1.device
16.250s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
systemd-analyze --user blame | head
3.800s gvfs-goa-volume-monitor.service
2.344s xdg-desktop-portal.service
1.438s org.freedesktop.IBus.session.generic.service
 781ms xdg-desktop-portal-gtk.service
 316ms gvfs-gphoto2-volume-monitor.service
 283ms gvfs-daemon.service
 281ms gvfs-mtp-volume-monitor.service
 209ms gvfs-afc-volume-monitor.service
 198ms gvfs-udisks2-volume-monitor.service
 166ms dconf.service
sudo coredumpctl list
TIME                          PID  UID  GID SIG     COREFILE EXE                                         SIZE
Thu 2024-03-28 11:37:06 WIB  2789    0    0 SIGSEGV none     /usr/bin/zypper                                -
Thu 2024-03-28 20:31:23 WIB  6229 1000 1000 SIGTRAP present  /tmp/.mount_JoplinlJw53b/@joplinapp-desktop 5.1M
Sun 2024-03-31 17:27:41 WIB  2853 1000 1000 SIGTRAP present  /usr/lib64/electron/electron                5.8M
Sun 2024-03-31 20:02:41 WIB  2837    0    0 SIGSEGV none     /usr/bin/zypper                                -
Tue 2024-04-02 13:41:39 WIB 24888 1000 1000 SIGTRAP present  /tmp/.mount_JoplinbMnRs4/@joplinapp-desktop 5.0M
Tue 2024-04-02 20:35:22 WIB  2387 1000 1000 SIGSEGV present  /usr/libexec/ibus/ibus-ui-gtk3              1.2M

Thanks, the journalctl output for priority 3 errors should’ve been small!
There are a lot of these entries which points to a kernel bug:

kernel: BUG: workqueue leaked lock or atomic: kworker/2:1/0x7fffffff/57
                                                   last function: ata_scsi_dev_rescan [libata]

Could you guess around when this problem started to happen?
Try booting from an older kernel, there is option to choose the kernel in grub menu → advanced options.

1 Like

The bug seems to happen with kernel 6.8.4-rc1-1-default, which I updated to after filing a post here.
I followed your instruction and booted with 6.8.2-1-default and then run:

sudo journalctl --no-pager -p3 -b
Apr 09 13:56:27 localhost kernel: x86/cpu: SGX disabled by BIOS.
Apr 09 13:57:33 localhost kernel: usb 1-8: device descriptor read/all, error -110
Apr 09 13:58:18 localhost.localdomain systemd[2292]: Failed to start Portal service (GTK/GNOME implementation).
Apr 09 13:58:27 localhost.localdomain sddm-helper[2380]: gkr-pam: unable to locate daemon control file
Apr 09 13:58:32 localhost.localdomain systemd[2385]: Failed to start IBus Daemon for generic sessions.
Apr 09 13:58:32 localhost.localdomain jackdbus[2608]: default: failed to stat "/home/fbgoestojkt/.config/jack/conf.xml", error is 2 (No such file or directory)
Apr 09 13:58:32 localhost.localdomain jackdbus[2608]: default: open() failed to open conf filename.

Great, hopefully there were no issues in the last hour since you posted the reply :crossed_fingers:

You can configure zypp to keep specific kernel versions:

pavin@suse-pc:~> grep ^multiversion.kernels /etc/zypp/zypp.conf 
multiversion.kernels = latest,latest-1,running,6.6.11-1-default,6.7.4-1-default

The default kernel in Grub menu can be chosen from Yast bootloader:

To bisect the kernel for regression reporting:—%20The%20Linux%20Kernel%20documentation.html

1 Like

Just booting after charging it for a while and the network starts to disconnect by itself. Hence, I re-run the command once again and this is the output:

sudo journalctl --no-pager -p3 -b
Apr 09 19:44:13 localhost.localdomain kernel: ath: phy0: Chip reset failed
Apr 09 19:44:13 localhost.localdomain kernel: ath: phy0: Unable to reset channel, reset status -22
Apr 09 19:44:13 localhost.localdomain kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff 

Can someone help me please? The problem still occurs.

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