This bug affects me too. Hardware is exactly the same. Dell XPS 13 9350

We have two places to fail here, linux-firmware and kernel. Tried different version combinations upgraded\downgraded.

Last working kernel for me is 4.18.16-300.fc29.x86_64 #1 SMP Sat Oct 20 23:24:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
No issues with this kernel with any linux-firmware package. 

Kernels greater than this one break my wifi on regular basis.

```[14553.667734] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14553.667742] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
[14555.715751] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14557.763741] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14557.763748] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
[14559.811660] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14561.859709] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14561.859716] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
[14563.908605] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14565.955611] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14565.955623] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
[14568.003577] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14570.051608] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[14570.051614] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -5
```
Workaround is to stick to 4.18.16-300.fc29.x86_64 kernel.

(In reply to Artem Silenkov from comment #1)
> Workaround is to stick to 4.18.16-300.fc29.x86_64 kernel.

So this first breaks with 4.18.17?  :
https://koji.fedoraproject.org/koji/buildinfo?buildID=1160572

Or did you not test that one ?

If this broke between 4.18.16 and 4.18.17 it should be relatively easy
to figure out what broke it.

Nope didn't test this one.

/ ❯❯❯ dnf list installed "kernel-core"
Installed Packages
kernel-core.x86_64                                                                     4.18.16-300.fc29                                                                      @anaconda
kernel-core.x86_64                                                                     4.19.7-300.fc29                                                                       @updates
kernel-core.x86_64                                                                     4.19.8-300.fc29                                                                       @updates

Fedora installer ships 4.18.16-300 <- good one
And updates repo goes directly to 4.19.7-300 <- broken.

The problem is this thing is hard to reproduce. It is just happening randomly even when laptop is completely idle.

Will do testing with 4.18.17 tomorrow.

(In reply to Hans de Goede from comment #2)
> (In reply to Artem Silenkov from comment #1)

> So this first breaks with 4.18.17?  :
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1160572
> 
> Or did you not test that one ?
> 
> If this broke between 4.18.16 and 4.18.17 it should be relatively easy
> to figure out what broke it.

Kernel v4.18.17 works for me, no wifi issues. Further switching to 4.19.7 triggers errors. 

I'm trying to bisect kernel sources to figure out offending commit but there are so many changes I feel lost already.

Created attachment 1514631 [details]
Full dmesg from boot to wifi fail

kernel 4.19.8-300.fc29.x86_64
full dmesg from fresh boot to wifi fail.

Comment on attachment 1514631 [details]
Full dmesg from boot to wifi fail

Crosspost from kernel.org bugzilla 
https://bugzilla.kernel.org/show_bug.cgi?id=201853

New update kernel=4.19.10-300.fc29.x86_64 is still bugged. 

Sadly I need fresh kernel for development tasks and this bug breaks core functionality for me. 

 iw dev wlp58s0 set power_save off

Could do the workaround but not good for battery which is terrible when travelling.

Thank you for the bug report, I've send an email to the upstream brcmfmac maintainers asking them for help with this.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Still present under F29 kernel 4.20.5-200.fc29.x86_64.

Same here.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 5.2.9-100.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30.

If you experience different issues, please open a new bug report for those.

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.