WiFi disconnects continually (goes "down" in NetworkManager)

[Bryan J Smalley]

Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager:

                                                         '
Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875204.3945] device (wlo1): Activation: successful, device activated.
Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <warn> [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1)
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9527] dhcp4 (wlo1): state changed bound -> done
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9544] manager: NetworkManager state is now CONNECTING
Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected
Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning
Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875349.6408] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875349.6409] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
Dec 01 21:16:42 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875402.0156] device (wlo1): supplicant interface state: inactive -> scanning
Dec 01 21:16:42 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875402.0157] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
Dec 01 21:16:42 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875402.9557] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:16:42 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875402.9558] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
Dec 01 21:16:42 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875402.9980] device (wlo1): supplicant interface state: inactive -> scanning
Dec 01 21:16:42 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875402.9981] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
Dec 01 21:16:43 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875403.9472] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:16:43 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875403.9473] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
Dec 01 21:16:45 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875405.4449] device (wlo1): supplicant interface state: inactive -> scanning
Dec 01 21:16:45 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875405.4450] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
Dec 01 21:16:46 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875406.4023] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:16:46 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875406.4028] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
Dec 01 21:16:47 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875407.4040] device (wlo1): supplicant interface state: inactive -> scanning
Dec 01 21:16:47 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875407.4041] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
Dec 01 21:16:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875408.3604] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:16:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875408.3611] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
Dec 01 21:16:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875408.9993] device (wlo1): supplicant interface state: inactive -> scanning
Dec 01 21:16:48 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875408.9994] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
Dec 01 21:16:50 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875410.3518] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:16:50 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875410.3519] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
Dec 01 21:16:50 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875410.4086] device (wlo1): supplicant interface state: inactive -> scanning
Dec 01 21:16:50 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875410.4087] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
Dec 01 21:16:51 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875411.3514] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:16:51 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875411.3515] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive
Dec 01 21:16:52 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875412.4453] device (wlo1): supplicant interface state: inactive -> scanning
Dec 01 21:16:52 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875412.4454] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
Dec 01 21:16:53 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875413.4255] device (wlo1): supplicant interface state: scanning -> inactive
Dec 01 21:16:53 bryan-HP-Notebook NetworkManager[22616]: <info> [1606875413.4255] device (p2p-dev-wlo1): supplicant management interface state: scanning -> inactive

My Wireless NIC is (I think):
bryan@bryan-HP-Notebook:~$ lspci | grep -i wireless
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)

Are there any other logs that I may provide that would be useful to the community for this issue? Are there other items I should look at besides NetworkManager as a cause? Any help is certainly appreciated.

ps. The wired network still functions flawlessly so I am not sure that this has anything to do with NetworkManager at all.

Cheers!
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bryan 3380 F.... pulseaudio
 /dev/snd/controlC0: bryan 3380 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-07-31 (491 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IpRoute:
 default via 192.168.10.1 dev enp3s0 proto dhcp metric 100
 default via 192.168.10.1 dev wlo1 proto dhcp metric 600
 169.254.0.0/16 dev enp3s0 scope link metric 1000
 192.168.10.0/24 dev enp3s0 proto kernel scope link src 192.168.10.88 metric 100
 192.168.10.0/24 dev wlo1 proto kernel scope link src 192.168.10.180 metric 600
MachineType: HP HP Notebook
Package: network-manager 1.22.10-1ubuntu2.2
PackageArchitecture: amd64
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=553742e0-94bb-402b-866b-634620d8ed27 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-56-generic N/A
 linux-backports-modules-5.4.0-56-generic N/A
 linux-firmware 1.187.4
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-56-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-06-01 (186 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/28/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 82F6
dmi.board.vendor: HP
dmi.board.version: 40.39
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.22:bd12/28/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.39:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.sku: X7T78UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.22.10 connected started full enabled enabled enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bryan 3380 F.... pulseaudio
 /dev/snd/controlC0: bryan 3380 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-07-31 (491 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IpRoute:
 default via 192.168.10.1 dev enp3s0 proto dhcp metric 100
 default via 192.168.10.1 dev wlo1 proto dhcp metric 600
 169.254.0.0/16 dev enp3s0 scope link metric 1000
 192.168.10.0/24 dev enp3s0 proto kernel scope link src 192.168.10.88 metric 100
 192.168.10.0/24 dev wlo1 proto kernel scope link src 192.168.10.180 metric 600
MachineType: HP HP Notebook
Package: network-manager 1.22.10-1ubuntu2.2
PackageArchitecture: amd64
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=553742e0-94bb-402b-866b-634620d8ed27 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-56-generic N/A
 linux-backports-modules-5.4.0-56-generic N/A
 linux-firmware 1.187.4
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-56-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-06-01 (186 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/28/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 82F6
dmi.board.vendor: HP
dmi.board.version: 40.39
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.22:bd12/28/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.39:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.sku: X7T78UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.22.10 connected started full enabled enabled enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bryan 3403 F.... pulseaudio
 /dev/snd/controlC0: bryan 3403 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-07-31 (503 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: HP HP Notebook
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=553742e0-94bb-402b-866b-634620d8ed27 ro quiet splash
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-58-generic N/A
 linux-backports-modules-5.4.0-58-generic N/A
 linux-firmware 1.187.6
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-58-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-06-01 (197 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/28/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 82F6
dmi.board.vendor: HP
dmi.board.version: 40.39
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.22:bd12/28/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.39:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.sku: X7T78UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1906600

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Allan Yaklin (allan-yaklin)]

I'm having a similar errors, I think it has something to do with the latest kernel updates. In my case, the kernel modules were updated on Dec 1. From the apt history.log:

Start-Date: 2020-12-01 07:41:57
Commandline: aptdaemon role='role-commit-packages' sender=':1.297'
Install: linux-image-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56:amd64 (5.4.0-56.62, automatic), linux-modules-extra-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-modules-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic)
Upgrade: linux-headers-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), linux-libc-dev:amd64 (5.4.0-54.60, 5.4.0-56.62), linux-image-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), snapd:amd64 (2.47.1+20.04, 2.48+20.04), linux-generic:amd64 (5.4.0.54.57, 5.4.0.56.59)
End-Date: 2020-12-01 07:43:16

I didn't restart my computer at the time, but shut it down overnight and restarted in the morning of December 2, and that's when I started having very similar issues as described in the original submission. The biggest difference is that the time period of WiFi network disconnects is longer - normally it'll work for a half hour or more, but eventually I'll get disconnected and prompted for a password on a network that I've been connecting to for years.

Might have something to do with Realtek wireless adapters:

allan ~ $ lspci | grep -i WiFi
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

I think I was supposed to mark each item in the affects column as confirmed, but I neglected to do that on 'linux (ubuntu)'. I've now marked that as confirmed as well. Apologies if this was not what I was supposed to do. Thanks again to all!

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10-rc6/amd64/

[Allan Yaklin (allan-yaklin)]

I have been running the mainline kernel since Saturday and have not seen any of the network disconnect notifications or password prompts since. I had been seeing several of them a day since the kernel update described in my original comment, so it appears the problem has been fixed for me.

[Bryan J Smalley (bryansmalley)]

If I have done this correctly, and that is truly questionable, I just installed one of the generic kernels from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10-rc6/amd64/ then restarted the PC and was connected for 8 - 10 minutes, but then the connection dropped again. I had installed: linux-modules-5.10.0-051000rc6-generic_5.10.0-051000rc6.202011291930_amd64.deb. Here is what it shows I am running:

bryan@bryan-HP-Notebook:~$ uname -r
5.4.0-58-generic

I will run the apport again to upload immediately after posting this message. As always, I thank you for your help. Cheers!

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Bryan J Smalley (bryansmalley)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Ok, so it's likely a kernel regression. What was the last kernel version doesn't have this issue?

[Bryan J Smalley (bryansmalley)]

Hello Feng Kai-Heng. I'm sorry, but I do not know what the last kernel version was running before the problem began. I never gave it a thought. After looking at it, I would imagine it was 5.4.0-54.60 but that could be wrong. Should I attempt to install that older version? Just in case it is useful I will post the full list of Kernels on the machine below. Thanks again for your help and Happy New Year!

rc linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.0.0-25-generic 5.0.0-25.26~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.0.0-29-generic 5.0.0-29.31~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.0.0-31-generic 5.0.0-31.33~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 amd64 Signed kernel image generic
rc linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.0.0-37-generic 5.0.0-37.40~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.3.0-28-generic 5.3.0-28.30~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.3.0-45-generic 5.3.0-45.37~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.3.0-46-generic 5.3.0-46.38~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.3.0-51-generic 5.3.0-51.44~18.04.2 amd64 Signed kernel image generic
rc linux-image-5.3.0-53-generic 5.3.0-53.47~18.04.1 amd64 Signed kernel image generic
rc linux-image-5.4.0-33-generic 5.4.0-33.37 amd64 Signed kernel image generic
rc linux-image-5.4.0-37-generic 5.4.0-37.41 amd64 Signed kernel image generic
rc linux-image-5.4.0-39-generic 5.4.0-39.43 amd64 Signed kernel image generic
rc linux-image-5.4.0-40-generic 5.4.0-40.44 amd64 Signed kernel image generic
rc linux-image-5.4.0-42-generic 5.4.0-42.46 amd64 Signed kernel image generic
rc linux-image-5.4.0-52-generic 5.4.0-52.57 ...

[Bryan J Smalley (bryansmalley)]

Hello all! I wanted to come back in to report that today I took an automatic update and this issue appears to be resolved. I've had the machine up for about seven hours and have maintained a wireless connection the entire time. I am running kernel 5.4.0-60-generic after the update. So, I am going to try to close this issue. If I am not able (permitted) to do so, please feel free to close it as resolved. Thank you all very much for the responses, troubleshooting, and all around support.

Cheers!

[Bryan J Smalley (bryansmalley)]

Sorry for this, but because this bug shows as affecting others then myself, I am not going to try closing it after all. It does still appear to be resolved for me, but I cannot speak for others.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]