Bug 2264249 - WiFi regularly dropping connection / deauthenticating with 6.7.z kernel
Summary: WiFi regularly dropping connection / deauthenticating with 6.7.z kernel
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 39
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-14 19:22 UTC by Gerard Ryan
Modified: 2024-02-15 11:53 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg.txt for kernel-6.7.3-200.fc39.x86_64 (110.39 KB, text/plain)
2024-02-14 19:23 UTC, Gerard Ryan
no flags Details
dmesg.txt for kernel-6.7.4-200.fc39.x86_64 (119.19 KB, text/plain)
2024-02-14 19:24 UTC, Gerard Ryan
no flags Details

Description Gerard Ryan 2024-02-14 19:22:32 UTC
1. Please describe the problem:
Connection dropping very frequently, which never happened on older kernels. I need to turn off my WiFi in GNOME settings, then turn it back on again to succeed, but it'll happen in a short couple of minutes again. If I don't do that, then I'll be prompted for the connection password but when I hit the connect button it will still fail. Here's what's printed to dmesg when it occurs (full logs will be attached):

Feb 14 17:59:07 kernel: wlp4s0: AP is in CSA process, reject auth
Feb 14 17:59:08 kernel: wlp4s0: deauthenticating from a4:2b:b0:02:1c:00 by local choice (Reason: 2=PREV_AUTH_NOT_VALID)
Feb 14 17:59:08 kernel: wlp4s0: 80 MHz not supported, disabling VHT
Feb 14 17:59:08 kernel: wlp4s0: authenticate with a4:2b:b0:02:1c:00 (local address=50:76:af:46:a9:d3)
Feb 14 17:59:08 kernel: wlp4s0: send auth to a4:2b:b0:02:1c:00 (try 1/3)
Feb 14 17:59:08 kernel: wlp4s0: authenticated
Feb 14 17:59:08 kernel: wlp4s0: associate with a4:2b:b0:02:1c:00 (try 1/3)
Feb 14 17:59:08 kernel: wlp4s0: RX AssocResp from a4:2b:b0:02:1c:00 (capab=0x1c11 status=0 aid=1)
Feb 14 17:59:08 kernel: wlp4s0: associated
Feb 14 17:59:08 kernel: wlp4s0: deauthenticating from a4:2b:b0:02:1c:00 by local choice (Reason: 1=UNSPECIFIED)


2. What is the Version-Release number of the kernel:
kernel-6.7.4-200.fc39

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
kernel-6.7.3-200.fc39

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
a. Install either 6.7.3 or 6.7.4 kernel-{,modules,modules-core,modules-extra,core}
b. Boot into system
c. Notice that after a short period of time (or immediately), the wifi connection will drop, and (in GNOME at least), a password prompt will appear to enter the connection password.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
I installed kernel-{,modules,modules-core,modules-extra,core}6.8.0-0.rc4.20240212git716f4aaa7b48.35.fc40.x86_64 from Koji (rather than adding the rawhide repo using the steps above). The good news is that it _doesn't_ appear to be happening with this version. So as per the title of this bug, it's specific to the 6.7.z versions that are built in Fedora so far (6.7.3, 6.7.4).

6. Are you running any modules that not shipped with directly Fedora's kernel?:
Now

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Reproducible: Always

Comment 1 Gerard Ryan 2024-02-14 19:23:48 UTC
Created attachment 2016732 [details]
dmesg.txt for kernel-6.7.3-200.fc39.x86_64

Comment 2 Gerard Ryan 2024-02-14 19:24:18 UTC
Created attachment 2016733 [details]
dmesg.txt for kernel-6.7.4-200.fc39.x86_64


Note You need to log in before you can comment on or make changes to this bug.