Created attachment 1736958 [details] kernel logs as requested 1. Please describe the problem: I just upgraded my laptop from Fedora 29 to Fedora 33 via dnf system-update from 29->30, 30->31, 31->32, and 32->33. I didn't run the laptop for any length of time at any intermediary point. Since I've been on F33 (as of yesterday), running the most recent code, I've noticed that my WiFi seems to drop out every 1-2 hours. Here you can see 3 instances from dmesg output: [56862.574124] wlp3s0: deauthenticated from b4:fb:e4:d2:5e:51 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA) [56862.609553] wlp3s0: authenticate with b4:fb:e4:d2:5e:51 [56862.617739] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 1/3) [56862.725080] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 2/3) [56862.742724] wlp3s0: authenticated [56862.744134] wlp3s0: associate with b4:fb:e4:d2:5e:51 (try 1/3) [56862.764747] wlp3s0: RX AssocResp from b4:fb:e4:d2:5e:51 (capab=0x11 status=0 aid=2) [56862.767652] wlp3s0: associated [60462.406041] wlp3s0: deauthenticated from b4:fb:e4:d2:5e:51 (Reason: 2=PREV_AUTH_NOT_VALID) [60463.117877] wlp3s0: authenticate with 18:e8:29:49:cf:fe [60463.127662] wlp3s0: send auth to 18:e8:29:49:cf:fe (try 1/3) [60463.133838] wlp3s0: authenticated [60463.136003] wlp3s0: associate with 18:e8:29:49:cf:fe (try 1/3) [60463.139058] wlp3s0: RX AssocResp from 18:e8:29:49:cf:fe (capab=0x11 status=0 aid=1) [60463.140395] wlp3s0: associated [60496.987713] wlp3s0: disconnect from AP 18:e8:29:49:cf:fe for new auth to b4:fb:e4:d2:5e:51 [60496.999071] wlp3s0: authenticate with b4:fb:e4:d2:5e:51 [60497.008523] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 1/3) [60497.151309] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 2/3) [60497.166776] wlp3s0: authenticated [60497.167269] wlp3s0: associate with b4:fb:e4:d2:5e:51 (try 1/3) [60497.188972] wlp3s0: RX ReassocResp from b4:fb:e4:d2:5e:51 (capab=0x11 status=0 aid=2) [60497.191889] wlp3s0: associated [67662.689992] wlp3s0: deauthenticated from b4:fb:e4:d2:5e:51 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA) [67662.841100] wlp3s0: authenticate with b4:fb:e4:d2:5e:51 [67662.849302] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 1/3) [67662.865578] wlp3s0: authenticated [67662.866631] wlp3s0: associate with b4:fb:e4:d2:5e:51 (try 1/3) [67662.910872] wlp3s0: RX AssocResp from b4:fb:e4:d2:5e:51 (capab=0x11 status=0 aid=2) [67662.913189] wlp3s0: associated [71262.686918] wlp3s0: deauthenticated from b4:fb:e4:d2:5e:51 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA) [71262.737414] wlp3s0: authenticate with b4:fb:e4:d2:5e:51 [71262.745182] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 1/3) [71262.867882] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 2/3) [71262.884367] wlp3s0: authenticated [71262.884877] wlp3s0: associate with b4:fb:e4:d2:5e:51 (try 1/3) [71262.906830] wlp3s0: RX AssocResp from b4:fb:e4:d2:5e:51 (capab=0x11 status=0 aid=2) [71262.908999] wlp3s0: associated [78462.038654] wlp3s0: deauthenticated from b4:fb:e4:d2:5e:51 (Reason: 2=PREV_AUTH_NOT_VALID) [78462.945195] wlp3s0: authenticate with 18:e8:29:49:cf:fe [78462.953915] wlp3s0: send auth to 18:e8:29:49:cf:fe (try 1/3) [78462.962070] wlp3s0: authenticated [78462.963545] wlp3s0: associate with 18:e8:29:49:cf:fe (try 1/3) [78462.966085] wlp3s0: RX AssocResp from 18:e8:29:49:cf:fe (capab=0x11 status=0 aid=1) [78462.967174] wlp3s0: associated [78494.639198] wlp3s0: disconnect from AP 18:e8:29:49:cf:fe for new auth to b4:fb:e4:d2:5e:51 [78494.647859] wlp3s0: authenticate with b4:fb:e4:d2:5e:51 [78494.655622] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 1/3) [78494.785930] wlp3s0: send auth to b4:fb:e4:d2:5e:51 (try 2/3) [78494.803134] wlp3s0: authenticated [78494.803930] wlp3s0: associate with b4:fb:e4:d2:5e:51 (try 1/3) [78494.825950] wlp3s0: RX ReassocResp from b4:fb:e4:d2:5e:51 (capab=0x11 status=0 aid=2) [78494.831504] wlp3s0: associated 2. What is the Version-Release number of the kernel: kernel-5.9.11-200.fc33.x86_64 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 : It was working just fine in Fedora 29 using kernel-5.3.11-100.fc29.x86_64 I have not really used any kernels between there and here. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: All I have to do is step away from my laptop for a few hours and when I come back it will have disconnected (and usually reconnected). 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 have not tried. 6. Are you running any modules that not shipped with directly Fedora's kernel?: Not that I am aware of. I do have an older version of "vmware" installed on the system, however I did not update it or try to configure it, so I am fairly sure the modules were not built as part of the update to F33. 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.
Just a quick update.. I was doing more research on this issue, and got pointed to https://bugzilla.kernel.org/show_bug.cgi?id=203709 which LOOKS similar, but I was getting different errors. The fact that it was only occurring when the screen blanked led me to think that it might be a power saver issue. Specifically, I have not seen this issue at all during the day while I am at my laptop the whole time. Yesterday I was never away from the laptop for more than 10 minutes and didn't have this failure, except for one time where I was away for about 20-30 minutes (and at that point it did have an issue). After a bit MORE research I found a site that recommended during off power management: iwconfig wlp3s0 power off I did this yesterday, and I have NOT seen this issue overnight! So this workaround seems to have helped. I'll keep an eye out over the next few days (and nights). But considering it's failed so much so frequently since I started, this is a great sign (I've not had a single night where the machine stayed connected). I don't recall if power management was an option in F29? If it continues to help, I'll turn this into a NetworkManager dispatch script to reset PM, unless there is some other way to turn it off permanently? Is there some other side effect that turning this off will have?
I had the same issues with connection. Until I run 'iwconfig wlp3s0 power off' from then it works flawlessly. There seems to be more people with this problem. Could bug 1892468 be duplicate of this (or the other way)?
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.