I suffer from this bug too, with this card in access point mode:
02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070]
And kernel 4.15.0-33-generic on Ubuntu 16.04 Xenial, though I encountered it with previous versions too, and I think with 4.4 kernels too.
It seems to happen when the load on the network is high.
But luckily, according to https://www.spinics.net/lists/linux-wireless/msg169581.html it seems to be fixed in Intel by https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/commit/?id=b8e2a319df8cc60626ab7dcabbbab64ff56be41e in their release/core35.
I think the resulting bug is probably in iwlwifi.ko (linux-image-extra package) (I don't think it is in iwlwifi.ucode). Is there any way to track which release/coreXX is in a kernel version?
I suffer from this bug too, with this card in access point mode:
02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070]
And kernel 4.15.0-33-generic on Ubuntu 16.04 Xenial, though I encountered it with previous versions too, and I think with 4.4 kernels too.
It seems to happen when the load on the network is high.
But luckily, according to https:/ /www.spinics. net/lists/ linux-wireless/ msg169581. html it seems to be fixed in Intel by https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/iwlwifi/ backport- iwlwifi. git/commit/ ?id=b8e2a319df8 cc60626ab7dcabb bab64ff56be41e in their release/core35.
I think the resulting bug is probably in iwlwifi.ko (linux-image-extra package) (I don't think it is in iwlwifi.ucode).
Is there any way to track which release/coreXX is in a kernel version?