ath10k_pci crash leading to unstable wifi on 18.04

[Mitch]

Ubuntu 18.04.
mitch@mitch-YOGA:~$ uname -a
Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Same laptop, device, working fine on 17.10. No crashes, stable wifi.

Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci 0000:01:00.0: failed to set 5g txpower 20: -11
Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci 0000:01:00.0: failed to setup tx power 20: -11
Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci 0000:01:00.0: failed to recalc tx power: -11
Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci 0000:01:00.0: failed to set inactivity time for vdev 0: -11
Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci 0000:01:00.0: failed to setup powersave: -11
Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci 0000:01:00.0: failed to set inactivity time for vdev 0: -11
Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci 0000:01:00.0: failed to setup powersave: -11
Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci 0000:01:00.0: failed to set PS Mode 0 for vdev 0: -11
Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci 0000:01:00.0: failed to setup powersave: -11
Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci 0000:01:00.0: failed to setup ps on vdev 0: -11
Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci 0000:01:00.0: failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11
Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove key (0, 54:a0:50:d8:ca:00) from hardware (-11)
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci 0000:01:00.0: failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci 0000:01:00.0: found sta peer 54:a0:50:d8:ca:00 (ptr 0000000000000000 id 133) entry on vdev 0 after it was supposedly removed
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at /build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 __sta_info_destroy_part2+0x169/0x170 [mac80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core kvm_intel
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566] ath kvm mac80211 irqbypass snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_seq_device snd_timer wmi_bmof serio_raw intel_wmi_thunderbolt snd idma64 virt_dma soundcore mei_me mei processor_thermal_device shpchp int340x_thermal_zone intel_lpss_pci intel_pch_thermal intel_lpss intel_soc_dts_iosf ideapad_laptop sparse_keymap mac_hid int3400_thermal acpi_thermal_rel acpi_pad tpm_crb sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm nvme_core i2c_hid wmi hid video
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644694] CPU: 0 PID: 757 Comm: NetworkManager Tainted: G W OE 4.15.0-20-generic #21-Ubuntu
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644697] Hardware name: LENOVO 80VF/LNVNB161216, BIOS 2JCN39WW 05/31/2017
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644741] RIP: 0010:__sta_info_destroy_part2+0x169/0x170 [mac80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644745] RSP: 0018:ffffa90881817978 EFLAGS: 00010286
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644751] RAX: 00000000fffffff5 RBX: ffff9056ddea8000 RCX: 0000000000000000
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644754] RDX: ffff9056e6c09780 RSI: 0000000000000000 RDI: 0000000000000000
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644757] RBP: ffffa90881817998 R08: ffff9056e67bde00 R09: 0000000100100008
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644761] R10: ffffa90881817880 R11: 0000000000000000 R12: ffff9056e6b80760
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644764] R13: ffff9056e28568c0 R14: ffff9056e28568c0 R15: ffff9056e6b80cb0
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644770] FS: 00007fc2745d1fc0(0000) GS:ffff9056f1c00000(0000) knlGS:0000000000000000
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644773] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644777] CR2: 00003b224e65b4d0 CR3: 000000026047c006 CR4: 00000000003606f0
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644780] Call Trace:
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644825] __sta_info_flush+0x12b/0x180 [mac80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644884] ieee80211_set_disassoc+0xba/0x3d0 [mac80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644936] ieee80211_mgd_deauth+0x287/0x440 [mac80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.644985] ieee80211_deauth+0x18/0x20 [mac80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645041] cfg80211_mlme_deauth+0xaf/0x1c0 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645081] cfg80211_mlme_down+0x66/0x80 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645120] cfg80211_disconnect+0x12a/0x1e0 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645154] __cfg80211_leave+0x13c/0x170 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645186] cfg80211_leave+0x2b/0x40 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645216] cfg80211_netdev_notifier_call+0x340/0x610 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645242] ? ath10k_monitor_recalc+0x11c/0x570 [ath10k_core]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645254] ? addrconf_notify+0x77/0xa40
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645273] ? ath10k_config_ps+0x52/0x70 [ath10k_core]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645281] ? inetdev_event+0x76/0x4d0
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645291] ? skb_dequeue+0x59/0x70
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645304] notifier_call_chain+0x4c/0x70
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645313] raw_notifier_call_chain+0x16/0x20
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645319] call_netdevice_notifiers_info+0x2d/0x60
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645325] __dev_close_many+0x63/0x110
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645331] dev_close_many+0x8c/0x140
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645338] dev_close.part.90+0x4a/0x70
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645344] dev_close+0x19/0x20
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645378] cfg80211_shutdown_all_interfaces+0x77/0xc0 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645408] cfg80211_rfkill_set_block+0x26/0x30 [cfg80211]
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645419] rfkill_set_block+0x99/0x160
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645427] rfkill_fop_write+0xef/0x1d0
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645438] __vfs_write+0x1b/0x40
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645446] vfs_write+0xb1/0x1a0
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645454] SyS_write+0x55/0xc0
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645463] ? SyS_fcntl+0x5d/0xb0
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645472] do_syscall_64+0x73/0x130
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645480] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645485] RIP: 0033:0x7fc271db12b7
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645489] RSP: 002b:00007fff05da85e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645495] RAX: ffffffffffffffda RBX: 0000000000000015 RCX: 00007fc271db12b7
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645498] RDX: 0000000000000008 RSI: 00007fff05da8618 RDI: 0000000000000015
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645501] RBP: 00007fff05da8618 R08: 0000000000000000 R09: 0000000000000016
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645504] R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000008
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645507] R13: 00005650f26df060 R14: 00005650f1d80421 R15: 0000000000000000
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645512] Code: 80 bb 0c 01 00 00 00 0f 84 33 ff ff ff 45 31 c0 b9 01 00 00 00 48 89 da 4c 89 ee 4c 89 e7 e8 5f aa ff ff 85 c0 0f 84 15 ff ff ff <0f> 0b e9 0e ff ff ff 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb 48
Apr 28 12:12:25 mitch-YOGA kernel: [12379.645640] ---[ end trace 782f24261b98d20d ]---
Apr 28 12:12:28 mitch-YOGA kernel: [12382.716159] ath10k_pci 0000:01:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Apr 28 12:12:31 mitch-YOGA kernel: [12385.787982] ath10k_pci 0000:01:00.0: failed to set cts protection for vdev 0: -11
Apr 28 12:12:34 mitch-YOGA kernel: [12388.860052] ath10k_pci 0000:01:00.0: failed to set erp slot for vdev 0: -11
Apr 28 12:12:37 mitch-YOGA kernel: [12391.931821] ath10k_pci 0000:01:00.0: failed to set preamble for vdev 0: -11
Apr 28 12:12:40 mitch-YOGA kernel: [12395.003730] ath10k_pci 0000:01:00.0: failed to down vdev 0: -11
Apr 28 12:12:43 mitch-YOGA kernel: [12398.075637] ath10k_pci 0000:01:00.0: failed to submit vdev param txbf 0x0: -11
Apr 28 12:12:43 mitch-YOGA kernel: [12398.075641] ath10k_pci 0000:01:00.0: failed to recalc txbf for vdev 0: -11
Apr 28 12:12:46 mitch-YOGA kernel: [12401.147697] ath10k_pci 0000:01:00.0: failed to set vdev wmm params on vdev 0: -11
Apr 28 12:12:49 mitch-YOGA kernel: [12404.219433] ath10k_pci 0000:01:00.0: failed to set vdev wmm params on vdev 0: -11
Apr 28 12:12:53 mitch-YOGA kernel: [12407.291482] ath10k_pci 0000:01:00.0: failed to set vdev wmm params on vdev 0: -11
Apr 28 12:12:56 mitch-YOGA kernel: [12410.363365] ath10k_pci 0000:01:00.0: failed to set vdev wmm params on vdev 0: -11
Apr 28 12:12:59 mitch-YOGA kernel: [12413.435161] ath10k_pci 0000:01:00.0: failed to stop WMI vdev 0: -11
Apr 28 12:12:59 mitch-YOGA kernel: [12413.435163] ath10k_pci 0000:01:00.0: failed to stop vdev 0: -11
Apr 28 12:13:04 mitch-YOGA kernel: [12418.555036] ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
Apr 28 12:13:07 mitch-YOGA kernel: [12421.626809] ath10k_pci 0000:01:00.0: failed to delete WMI vdev 0: -11
Apr 28 12:13:07 mitch-YOGA kernel: [12421.638968] ath10k_pci 0000:01:00.0: failed to read hi_board_data address: -16
Apr 28 12:13:13 mitch-YOGA kernel: [12427.770548] ath10k_pci 0000:01:00.0: could not suspend target (-11)
Apr 28 12:13:16 mitch-YOGA kernel: [12430.819484] ath10k_pci 0000:01:00.0: failed to receive initialized event from target: 00000000
Apr 28 12:13:19 mitch-YOGA kernel: [12433.847391] ath10k_pci 0000:01:00.0: failed to receive initialized event from target: 00000000
Apr 28 12:13:19 mitch-YOGA kernel: [12433.847394] ath10k_pci 0000:01:00.0: failed to wait for target init: -110
Apr 28 12:14:01 mitch-YOGA kernel: [12475.586961] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Apr 28 12:14:01 mitch-YOGA kernel: [12475.908185] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
Apr 28 12:14:01 mitch-YOGA kernel: [12475.908197] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
Apr 28 12:14:01 mitch-YOGA kernel: [12475.911016] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 17aa:0827
Apr 28 12:14:01 mitch-YOGA kernel: [12475.911019] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
Apr 28 12:14:01 mitch-YOGA kernel: [12475.911789] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
Apr 28 12:14:01 mitch-YOGA kernel: [12475.977530] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
Apr 28 12:14:02 mitch-YOGA kernel: [12476.567547] ath10k_pci 0000:01:00.0: Unknown eventid: 118809
Apr 28 12:14:02 mitch-YOGA kernel: [12476.570494] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
Apr 28 12:14:02 mitch-YOGA kernel: [12476.571154] ath10k_pci 0000:01:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Apr 28 12:14:02 mitch-YOGA kernel: [12476.679209] ath: EEPROM regdomain: 0x6c
Apr 28 12:14:02 mitch-YOGA kernel: [12476.679210] ath: EEPROM indicates we should expect a direct regpair map
Apr 28 12:14:02 mitch-YOGA kernel: [12476.679213] ath: Country alpha2 being used: 00
Apr 28 12:14:02 mitch-YOGA kernel: [12476.679214] ath: Regpair used: 0x6c
Apr 28 12:14:02 mitch-YOGA kernel: [12476.683642] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
Apr 28 12:14:02 mitch-YOGA kernel: [12476.711534] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
Apr 28 12:14:26 mitch-YOGA kernel: [12500.261822] ath10k_pci 0000:01:00.0: Unknown eventid: 118809
Apr 28 12:14:26 mitch-YOGA kernel: [12500.266089] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
Apr 28 12:14:26 mitch-YOGA kernel: [12500.323488] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
Apr 28 12:14:26 mitch-YOGA kernel: [12500.380304] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
Apr 28 12:14:31 mitch-YOGA kernel: [12505.295032] wlp1s0: authenticate with 54:a0:50:d8:ca:00
Apr 28 12:14:31 mitch-YOGA kernel: [12505.350087] wlp1s0: send auth to 54:a0:50:d8:ca:00 (try 1/3)
Apr 28 12:14:31 mitch-YOGA kernel: [12505.351582] wlp1s0: authenticated
Apr 28 12:14:31 mitch-YOGA kernel: [12505.355292] wlp1s0: associate with 54:a0:50:d8:ca:00 (try 1/3)
Apr 28 12:14:31 mitch-YOGA kernel: [12505.357791] wlp1s0: RX AssocResp from 54:a0:50:d8:ca:00 (capab=0x1411 status=0 aid=2)
Apr 28 12:14:31 mitch-YOGA kernel: [12505.360208] wlp1s0: associated

WORKAROUND: Turn off bluetooth mouse before suspending.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1767611/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Mitch (mitch-hasbox)]

I cannot find a package to log it against. THIS IS A KERNEL DRIVER ISSUE

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3

[Maikeu (maikramer)]

QCA6174 - The most groundbreaking problem to me is the fact that suspend doesnt work well, when we return from suspend, wifi and bluetooth, same board, are not working, a restart wont fix, even if selecting a older working kernel. Looks like the only fix is shutdown, then there is no more power in the board, i guess the kernel is breaking the board in a way that it needs a full reastart, i guess the board doesnt restart completely if you just restart the computer.

I can confirm that the problems started after 4.14, the last one that was really working is 4.13, i tried now with 4.17-rc3 and didnt help, tried also with the latest ath10k_pci modules from github ( https://github.com/kvalo/ath10k-firmware), no changes.

I can confirm also the problem is with the kernel, because just booting with 4.13, same packages and even same lib/firmware/ath10k_pci,

If i can help with something i would be happy to do, i already tried everthing i can do, thanks. Close everything i'm doing is not something great.

[Maikeu (maikramer)]

Found another information, if i turn off my bluetooth mouse before suspention. The crash in the module seems to be related to suspending with something connected.

[Maikeu (maikramer)]

Sorry.. If i turn off my bluetooth mouse before suspention, the problem doesnt happen. The crash in the module seems to be related to suspending with something connected.

[penalvch (penalvch)]

Mitch, please address all of the following:

1) To gather system debugging information, could you please execute the following via a terminal:
apport-collect 1767611

2) To clarify, this issue only happens after resuming from suspend (i.e. after booting from a shutdown, performing subsequent power ups from shutdown or restarts without suspending don't cause the issue)?

3) The next step is to fully commit bisect from kernel 4.13 to 4.15 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

[Mitch (mitch-hasbox)]

Hi,

I can't reproduce this anymore. I think perhaps recent updates have fixed this issue (for me at least).

Marking this closed.
Mitch

[penalvch (penalvch)]

Mitch, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767611/comments/8 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Chris Klosowski (cklosowski)]

I know this got marked as 'invalid' but I'm experiencing this now on 18.10 with this driver after updating to 18.0.4.1 (I was not experiencing it previously). It doesn't take a suspend for me. I can be actively using the system and have the issue arise.

Kernal: Ubuntu 4.18.0-10.11-generic 4.18.12

Oddly enough it's only when I'm connected to my home network. I've been on two other networks without issue.

Not working (Home): 5gHz Linksys WRT 1200 AC

Other working networks:
Nighthawk Router
WiFi Tether on my mobile device

It seems to be inconsistent for me as well. Usually, if I catch it early enough, I can simply turn off the WiFi and turn it back on and things resolve out. However, if it sits in this state too long, the system overall is less responsive and I can't get the WiFi to recover.

Is there anything else I can supply?

[penalvch (penalvch)]

Chris Klosowski (cklosowski), as this report is closed, if you would like your issue reviewed, please use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Nikolaj Løbner Sheller (nikolaj-l)]

I believe I am seeing the same issue on 20.04:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767611

[penalvch (penalvch)]

Nikolaj Løbner Sheller (nikolaj-l), this report is closed as it was reported resolved by the original reporter. Hence, it has nothing to do with your problem.

However, if you would like your issue resolved, please use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.