Comment 4 for bug 1627474

On Tue, Oct 4, 2016 at 6:25 AM Joseph Salisbury <
<email address hidden>> wrote:

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

No - it's a new machine on which I've installed Yakkety.

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

Yes, though I did already try the upstream firmwares directly, which didn't
fix it. I've updated and tested with the latest 4.8 in yakkety first:

michael@hpmor2:~$ dmesg | grep ath10k.*crashed
[ 274.052266] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
80f6a701-8aa3-4f34-8d20-49e478f9020a)
[ 276.900284] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
55e52555-0bfb-42b8-b612-579a9188b642)
[ 1247.381606] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
6f45c6af-33a0-4c5d-a65c-785a97c2ea3a)
michael@hpmor2:~$ uname -a
Linux hpmor2 4.8.0-21-generic #23-Ubuntu SMP Tue Oct 4 18:27:25 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

Then, given that you wrote your comment before the mainline/4.8.1 was
created, I've also tested with that:

michael@hpmor2:~$ dmesg | grep ath10k.*crashed
[ 652.277650] ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
[ 655.127699] ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
michael@hpmor2:~$ uname -a
Linux hpmor2 4.8.1-040801-generic #201610071031 SMP Fri Oct 7 14:34:10 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux

Updating ... thanks Joseph.