Comment 6 for bug 1627474

Although not using Ubuntu, I'm also experiencing this issue on both 4.9.27 and 4.10.15. I have been experiencing this issue since I first setup my machine a few weeks ago.

This is the pattern that happens often when I leave my machine on:

```
[ 1008.043987] wlp2s0: AP 14:cc:20:da:1e:e5 changed bandwidth, new config is 2412 MHz, width 2 (2422/0 MHz)
[ 1037.415409] ath10k_pci 0000:02:00.0: firmware crashed! (uuid n/a)
[ 1037.415424] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1028:0310
[ 1037.415428] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
[ 1037.416312] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[ 1037.416748] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 19644295
[ 1037.416753] ath10k_pci 0000:02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 1037.418802] ath10k_pci 0000:02:00.0: firmware register dump:
[ 1037.418808] ath10k_pci 0000:02:00.0: [00]: 0x05030000 0x000015B3 0x009860FA 0x00955B31
[ 1037.418812] ath10k_pci 0000:02:00.0: [04]: 0x009860FA 0x00060730 0x00000004 0x0040E8A0
[ 1037.418815] ath10k_pci 0000:02:00.0: [08]: 0x004980AC 0x00955A00 0x0000000B 0x00400000
[ 1037.418819] ath10k_pci 0000:02:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
[ 1037.418822] ath10k_pci 0000:02:00.0: [16]: 0x00952CC4 0x00910712 0x00000000 0x00000000
[ 1037.418826] ath10k_pci 0000:02:00.0: [20]: 0x409860FA 0x0040E7E8 0x00000000 0x0041E0DC
[ 1037.418830] ath10k_pci 0000:02:00.0: [24]: 0x800B5A1D 0x0040E848 0x000FFFFF 0xC09860FA
[ 1037.418833] ath10k_pci 0000:02:00.0: [28]: 0x809B3230 0x0040E948 0x00000018 0x004313B8
[ 1037.418837] ath10k_pci 0000:02:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9BC 0x00429548
[ 1037.418840] ath10k_pci 0000:02:00.0: [36]: 0x8091D252 0x0040E9B8 0x00000000 0x00000001
[ 1037.418844] ath10k_pci 0000:02:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10
[ 1037.418847] ath10k_pci 0000:02:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x00000001
[ 1037.418851] ath10k_pci 0000:02:00.0: [48]: 0x80911210 0x0040EAD8 0x00000010 0x004041D0
[ 1037.418855] ath10k_pci 0000:02:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[ 1037.418859] ath10k_pci 0000:02:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[ 1037.502646] ieee80211 phy0: Hardware restart was requested
[ 1039.891557] ath10k_pci 0000:02:00.0: device successfully recovered
[ 2122.645627] wlp2s0: AP 14:cc:20:da:1e:e5 changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
```

After that happens (by the time I notice it, after 2122.645627) the network seems down, even though it reports as connected. It all comes back after a power off and power on of the card (either soft or hard works).

Since this happens on a vanilla kernel it is an upstream bug. I'd be glad to report to upstream if anyone can point to an existing bug or specific tracker. I just happen to find this issue here and thought it would be useful to report.