Bug 201853 - Broadcom wireless stops working
Summary: Broadcom wireless stops working
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-03 13:10 UTC by Richard van der Hoff
Modified: 2019-04-09 14:57 UTC (History)
16 users (show)

See Also:
Kernel Version: 4.19.0
Tree: Mainline
Regression: No


Attachments
attachment-1187-0.html (515 bytes, text/html)
2019-01-23 10:27 UTC, Wouter Depypere
Details

Description Richard van der Hoff 2018-12-03 13:10:05 UTC
I recently upgraded from a 4.15.0 kernel to 4.19.0. Since then, after a few hours, my wireless network drops out.

dmesg shows the following:

Dec  3 12:49:23 fred kernel: [10268.516684] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
Dec  3 12:49:23 fred kernel: [10268.516716] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5

(repeated every few seconds)

Later:

Dec  3 12:51:34 fred kernel: [10399.586711] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Dec  3 12:51:34 fred kernel: [10399.586818] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Dec  3 12:51:34 fred kernel: [10399.586830] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -12
Dec  3 12:51:34 fred kernel: [10399.586924] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Dec  3 12:51:34 fred kernel: [10399.586934] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -12
Dec  3 12:51:34 fred kernel: [10399.587027] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Dec  3 12:51:34 fred kernel: [10399.587038] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -12
Dec  3 12:51:34 fred kernel: [10399.587132] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring


lspci:

3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless Network Adapter (rev 08)
	Subsystem: Dell BCM4350 802.11ac Wireless Network Adapter
	Flags: bus master, fast devsel, latency 0, IRQ 133
	Memory at dc400000 (64-bit, non-prefetchable) [size=32K]
	Memory at dc000000 (64-bit, non-prefetchable) [size=4M]
	Capabilities: [48] Power Management version 3
	Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+
	Capabilities: [68] Vendor Specific Information: Len=44 <?>
	Capabilities: [ac] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Device Serial Number 00-00-cb-ff-ff-e8-30-52
	Capabilities: [150] Power Budgeting <?>
	Capabilities: [160] Virtual Channel
	Capabilities: [1b0] Latency Tolerance Reporting
	Capabilities: [220] #15
	Capabilities: [240] L1 PM Substates
	Kernel driver in use: brcmfmac
	Kernel modules: brcmfmac
Comment 1 Daniel Dunbar 2018-12-03 20:09:33 UTC
Can confirm issue with same controller on 4.19.x.
Comment 2 elParaguayo 2018-12-11 20:13:34 UTC
Upgraded to 4.19.8 and issue is still present. Same controller.


First reported on Arch forums: https://bbs.archlinux.org/viewtopic.php?id=242382


Happy to post more info if needed.
Comment 3 Wesley Kerfoot 2018-12-12 02:39:11 UTC
Crossposting this from the Arch Linux bug tracker https://bugs.archlinux.org/task/60899

Hey, I also have this issue (same model, XPS 13 9350).

Also, I am running 4.19.8 and I still have the issue.

I see some messages related to brcmfmac at boot as well

```
[ 12.763094] usbcore: registered new interface driver brcmfmac
[ 12.763168] brcmfmac 0000:3a:00.0: enabling device (0000 -> 0002)
[ 12.869720] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4350-pcie for chip BCM4350/8
[ 12.875052] brcmfmac 0000:3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.txt failed with error -2
[ 13.301077] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4350-pcie for chip BCM4350/8
[ 13.302049] brcmfmac 0000:3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.clm_blob failed with error -2
[ 13.302051] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 13.303678] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4350/8 wl0: Oct 22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
[ 13.328643] brcmfmac 0000:3a:00.0 wlp58s0: renamed from wlan0
```

The errors don't prevent wifi from working (at first), but maybe this could be related to the issue.

I will attempt to find a way to reproduce it consistently.
Comment 4 Wesley Kerfoot 2018-12-12 03:52:53 UTC
Currently I've turned power management off to see if it crashes again

sudo iw dev wlp58s0 set power_save off

I will report back if it's still working after leaving it on overnight (usually results in a crash when I check it the next morning)
Comment 5 Wesley Kerfoot 2018-12-12 16:14:17 UTC
The issue does not occur with power management turned off (using the method mentioned before)
Comment 6 Alex Georgopoulos 2018-12-13 06:01:10 UTC
I'm seeing this as well on 4.19.8


[76650.729106] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[76650.729116] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[76650.729119] brcmfmac: brcmf_cfg80211_get_tx_power: error (-12)
[76650.761139] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[76650.761145] brcmfmac: brcmf_link_down: WLC_DISASSOC failed (-5)
[76651.020936] brcmfmac: brcmf_netdev_start_xmit: xmit rejected state=0
[76651.281127] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[76651.281863] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[76651.285481] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[76651.285486] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5)
[76651.313397] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
[76651.313400] PGD 0 P4D 0 

lspci:

03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01)
	Subsystem: Apple Inc. BCM43602 802.11ac Wireless LAN SoC
	Flags: bus master, fast devsel, latency 0, IRQ 56
	Memory at a0800000 (64-bit, non-prefetchable) [size=32K]
	Memory at a0400000 (64-bit, non-prefetchable) [size=4M]
	Capabilities: [48] Power Management version 3
	Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+
	Capabilities: [68] Vendor Specific Information: Len=44 <?>
	Capabilities: [ac] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Device Serial Number bb-bb-a7-ff-ff-b5-98-01
	Capabilities: [150] Power Budgeting <?>
	Capabilities: [160] Virtual Channel
	Capabilities: [1b0] Latency Tolerance Reporting
	Capabilities: [220] #15
	Capabilities: [240] L1 PM Substates
	Kernel driver in use: brcmfmac
	Kernel modules: brcmfmac
Comment 7 Artem Silenkov 2018-12-15 17:05:42 UTC
Looks like we hit this bug in Fedora 29 too. 
With update to 4.19.7 and higher wifi goes broken. 

https://bugzilla.redhat.com/show_bug.cgi?id=1658178
Comment 8 ramnes 2019-01-23 10:21:25 UTC
I also hit this bug with 4.20.3 on a XPS 13 9350.
Comment 9 Wouter Depypere 2019-01-23 10:27:26 UTC
Created attachment 280695 [details]
attachment-1187-0.html

Hello,

Thank you for your message. I am currently out of the office, with no email access. I will be returning on Tuesday February 5th.

Kind regards,

Wouter Depypere
Comment 10 Tom 2019-02-03 11:52:12 UTC
I have also been dealing with this bug since December on my XPS 9350. Seems to only happy when on battery power.
Comment 11 Neoh 2019-02-05 05:55:43 UTC
Hit with same issue with my dell xps 13 9350.

sudo journalctl -k | grep -i brcmfmac:

Feb 05 12:19:30 archlinux kernel: usbcore: registered new interface driver brcmfmac
Feb 05 12:19:30 archlinux kernel: brcmfmac 0000:3a:00.0: enabling device (0000 -> 0002)
Feb 05 12:19:30 archlinux kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4350-pcie for chip BCM4350/8
Feb 05 12:19:30 archlinux kernel: brcmfmac 0000:3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.txt failed with error -2
Feb 05 12:19:30 archlinux kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4350-pcie for chip BCM4350/8
Feb 05 12:19:30 archlinux kernel: brcmfmac 0000:3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.clm_blob failed with error -2
Feb 05 12:19:30 archlinux kernel: brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Feb 05 12:19:30 archlinux kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4350/8 wl0: Oct 22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
Feb 05 12:19:30 archlinux kernel: brcmfmac 0000:3a:00.0 wlp58s0: renamed from wlan0
Feb 05 14:27:48 archlinux kernel: brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
Feb 05 14:27:48 archlinux kernel: brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
Feb 05 14:27:54 archlinux kernel: brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
Feb 05 14:27:56 archlinux kernel: brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
...(many repeated)

Feb 05 14:29:28 archlinux kernel: brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
...

Feb 05 14:37:05 archlinux kernel: brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -12
Feb 05 14:37:11 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:37:11 archlinux kernel: brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -12
Feb 05 14:37:11 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:37:11 archlinux kernel: brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -12
Feb 05 14:37:11 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:37:11 archlinux kernel: brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -12
...

Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_delete_flowring: FW unaware, flowring will be removed !!
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_delete_flowring: FW unaware, flowring will be removed !!
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_link_down: WLC_DISASSOC failed (-12)
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:42:16 archlinux kernel: brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -12
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:42:16 archlinux kernel: brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -12
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:42:16 archlinux kernel: brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -12
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_run_escan: error (-12)
Feb 05 14:42:16 archlinux kernel: brcmfmac: brcmf_cfg80211_scan: scan error (-12)
...
Comment 12 jcreixell 2019-02-10 10:06:01 UTC
I am also affected by this both with battery power and plugged in, XPS 13 9350.



[39602.607232] brcmfmac: brcmf_cfg80211_get_tx_power: error (-12)
[39602.620010] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.631605] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.631609] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.631611] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.631613] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.631616] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.631617] brcmfmac: brcmf_p2p_set_firmware: failed to update device address ret -12
[39602.631620] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.631620] brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc error
[39602.631622] brcmfmac: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp58s0 type 10 failed: err=-12
[39602.657232] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39602.657235] brcmfmac: brcmf_run_escan: error (-12)
[39602.657236] brcmfmac: brcmf_cfg80211_scan: scan error (-12)
[39605.994893] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39605.994901] brcmfmac: brcmf_run_escan: error (-12)
[39605.994906] brcmfmac: brcmf_cfg80211_scan: scan error (-12)
[39621.753446] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39621.754196] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39621.754205] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-12)
[39625.737011] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.737147] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.737154] brcmfmac: brcmf_cfg80211_set_power_mgmt: error (-12)
[39625.738301] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.738307] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -12
[39625.738345] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.738349] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -12
[39625.738391] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.738395] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -12
[39625.738433] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.738439] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.754018] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[39625.754024] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-12)
[39625.754062] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
...
Comment 13 Mikael 2019-02-16 16:43:33 UTC
Same here. I didn't notice this was happening only when on AC power before i got on this thread.

Here's the full dmesg :

https://pastebin.com/CavehFgt
Comment 14 Rafał Miłecki 2019-02-22 08:29:10 UTC
What you are all seeing is a FullMAC firmware (running on wireless card's ARM CPU) crash. It crashes and your host driver brcmfmac cannot communicate with it anymore. It results in timeouts & running out of resources.

Since many suggest it's a regression, it seems some brcmfmac change has affected FullMAC firmware stability.

I've started with checking 4.19 changes and I don't see anything fishy there:
# git log --no-merges --oneline v4.18..v4.19 drivers/net/wireless/broadcom/brcm80211/brcmfmac/
27a8aea13053 brcmfmac: fix brcmf_wiphy_wowl_params() NULL pointer dereference
1e591c56a65f brcmfmac: specify some features per firmware version
07b1ae468749 brcmfmac: update STA info struct to the v5
4b4a8d808c58 brcmfmac: define more bits for the flags of struct brcmf_sta_info_le
a8d7631858af brcmfmac: handle msgbuf packets marked with monitor mode flag
e63410ac65e0 brcmfmac: detect firmware support for radiotap monitor frames
01f69dfafdbe brcmfmac: detect firmware support for monitor interface
22d0d2fafca9 wireless-drivers: use BIT_ULL for NL80211_STA_INFO_ attribute types

Still it seems that regression has been introduced somewhere between 4.15 and 4.19. Can someone perform a kernel bisection and see which commit is there to blame? That will be very helpful in debugging & fixing this problem.

This should work:
git bisect start drivers/net/wireless/broadcom/brcm80211/brcmfmac/
git bisect good v4.15
git bisect bad v4.19
and take only ~7 steps.
Comment 15 Richard van der Hoff 2019-02-22 11:02:37 UTC
Thanks for the insights, Rafał. I've been trying to figure out where this got introduced, but it's sufficiently intermittent that I find I need to run with each version for at least a few days to be sure that the issue isn't occurring.

Currently I'm running 4.18.17 (2237effd7edc201d9d6bed6bef8ada3cb1499d7b), which *seems* to be fine.

I'll try a bisection from there, limited as you suggest to the brcmfmac driver changes.
Comment 16 Wesley Kerfoot 2019-02-22 16:41:47 UTC
The most reliable way I've found to reproduce this is to put your laptop into suspend mode, bring it out, and then leave it for 2 to 3 hours. I'm guessing (depending on the number of commits between 4.15 and 4.19) that it would take a long time to try and narrow it down. Does anyone have any suggestions for how we might more reliably reproduce the problem, or detect whether it exists?
Comment 17 Mikael 2019-02-23 07:09:46 UTC
So far i can recall, i'm having this issue for around 6 months. This leads to 4.15, 4.16 or 4.17. I'm reasonably sure this was not happening with 4.18...unfortunately i don't remember about having the issue or not on the other versions. So...that won't help you much :(.

I couldn't find a reliable way to replicate (other than what Wesley already told : going into sleep mode, wake up, and wait). Still trying to find something.
Comment 18 Mikael 2019-02-23 07:15:59 UTC
Sorry for the spam, I mispelled :
"I'm reasonably sure this was not happening with 4.18"
Should be
"I'm reasonably sure this was happening *before* 4.18"
Comment 19 Richard van der Hoff 2019-03-11 12:26:40 UTC
> "I'm reasonably sure this was happening *before* 4.18"

I guess it's possible there's more than one issue happening here. Certainly things seem stable for me on 4.18.

Conclusions of my bisection so far:

- 4b4a8d808c58fc0defc32a26b2fea35d66692c45: seems stable
- a527d3f728bfdb6c30c8ecc0b58e695d05d42fc8: failed fairly quickly (without even having suspened). dmesg snippets:

[ 1981.206446] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 1981.206461] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
[ 1987.190378] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command


(repeats many times)

[ 2106.132978] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 2106.133001] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
[ 2108.152876] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 2110.164851] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 2110.164867] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
[ 2112.180838] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 2112.180946] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[ 2112.180958] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -12
[ 2112.181572] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[ 2112.181670] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[ 2112.181680] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -12
[ 2112.181901] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[ 2112.181996] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
[ 2112.182005] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -12
[ 2118.182036] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring

(repeats many times)

Since this happened only a few minutes after reboot, and the messages are different, perhaps this is a different problem? If so, it makes the bisection even harder :/.
Comment 20 Wesley Kerfoot 2019-03-19 23:21:01 UTC
I replaced my card with an Intel Wireless-AC 8265 card and it seems to be working perfectly. Obviously not recommended as a solution for most people, but Dell does support these chips.
Comment 21 Richard van der Hoff 2019-03-25 09:48:44 UTC
So as far as I can tell, 07b1ae468749 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=07b1ae46874949252625c96f309f96ca0f337020) exhibits this bug (at least, I definitely saw symptoms matching this report with that kernel), whereas 4b4a8d808c58, its immediate parent, appears stable.

Given what changed in that commit, that seems a bit surprising. I'm now running 4b4a8d808c58 to try to confirm.
Comment 22 Richard van der Hoff 2019-04-09 14:57:43 UTC
I can confirm that 4b4a8d808c58 seems stable, so this seems to have been introduced by 07b1ae468749.

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