Problem with Intel 7260 | Kernel 3.11

Hi, I’m having problem with my wireless connection. It manages to get connected, but from time to time it gets disconnected. Also sometimes it fails to connect to a wireless-n. I have not managed to figure out what triggers this disconnection. These are the outputs I thought could help clarify what happens:

uname -a

Linux linux-suse 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) x86_64 x86_64 x86_64 GNU/Linux

lspci

06:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
06:00.0 0280: 8086:08b1 (rev 73)

dmesg


 1857.763144] ------------ cut here ]------------
 1857.763157] WARNING: CPU: 0 PID: 727 at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.10/linux-3.11/drivers/net/wireless/iwlwifi/mvm/mac80211.c:1047 iwl_mvm_mac_sta_state+0x221/0x280 [iwlmvm]()
 1857.763159] Modules linked in: fuse rfcomm vboxpci(O) vboxnetadp(O) vboxnetflt(O) af_packet xt_pkttype xt_LOG xt_limit ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables vboxdrv(O) xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables bnep arc4 nls_iso8859_1 nls_cp437 vfat fat tpm_infineon snd_hda_codec_realtek snd_hda_codec_hdmi uvcvideo videobuf2_core x86_pkg_temp_thermal videodev coretemp videobuf2_vmalloc videobuf2_memops kvm_intel snd_hda_intel snd_hda_codec kvm iwlmvm snd_hwdep crc32_pclmul ghash_clmulni_intel mac80211 snd_pcm aesni_intel ablk_helper iTCO_wdt cryptd snd_seq iTCO_vendor_support rtsx_pci_sdmmc rtsx_pci_ms
 1857.763187]  mmc_core memstick lrw gf128mul snd_timer glue_helper aes_x86_64 iwlwifi r8169 snd_seq_device btusb cfg80211 firewire_ohci sr_mod i2c_i801 serio_raw joydev pcspkr cdrom mii bluetooth snd firewire_core rtsx_pci lpc_ich crc_itu_t mfd_core rfkill mei_me mei soundcore snd_page_alloc shpchp battery tpm_tis tpm tpm_bios acpi_cpufreq ac mperf sg dm_mod autofs4 efivarfs btrfs raid6_pq zlib_deflate xor libcrc32c crc32c_intel nouveau i915 ttm drm_kms_helper drm xhci_hcd mxm_wmi i2c_algo_bit thermal wmi video button processor thermal_sys scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw scsi_dh
 1857.763220] CPU: 0 PID: 727 Comm: wpa_supplicant Tainted: G        W  O 3.11.10-21-desktop #1
 1857.763222] Hardware name: Notebook                         P15SM-A/SM1-A                    /P15SM-A/SM1-A                    , BIOS 4.6.5 02/14/2014
 1857.763223]  0000000000000009 ffffffff815a0392 0000000000000000 ffffffff81050eb2
 1857.763227]  0000000000000000 0000000000000004 0000000000000003 ffff88041a28b1c0
 1857.763230]  ffff88041931d7c0 ffffffffa06d4841 ffffffff00000004 0000000000000003
 1857.763234] Call Trace:
 1857.763243]  <ffffffff81004a28>] dump_trace+0x88/0x310
 1857.763247]  <ffffffff81004d80>] show_stack_log_lvl+0xd0/0x1d0
 1857.763250]  <ffffffff810061bc>] show_stack+0x1c/0x50
 1857.763255]  <ffffffff815a0392>] dump_stack+0x50/0x89
 1857.763261]  <ffffffff81050eb2>] warn_slowpath_common+0x72/0x90
 1857.763266]  <ffffffffa06d4841>] iwl_mvm_mac_sta_state+0x221/0x280 [iwlmvm]
 1857.763289]  <ffffffffa079d7eb>] sta_info_move_state+0xcb/0x780 [mac80211]
 1857.763300]  <ffffffffa079df7b>] __sta_info_destroy+0xdb/0x390 [mac80211]
 1857.763312]  <ffffffffa079e345>] sta_info_flush_defer+0x75/0xa0 [mac80211]
 1857.763328]  <ffffffffa07d5b45>] ieee80211_set_disassoc+0xa5/0x3c0 [mac80211]
 1857.763374]  <ffffffffa07d9084>] ieee80211_mgd_deauth+0x244/0x2b0 [mac80211]
 1857.763422]  <ffffffffa056fe76>] cfg80211_mlme_deauth+0x96/0x1b0 [cfg80211]
 1857.763450]  <ffffffffa0558bfc>] nl80211_deauthenticate+0xcc/0x120 [cfg80211]
 1857.763460]  <ffffffff814e8249>] genl_family_rcv_msg+0x179/0x360
 1857.763464]  <ffffffff814e84a9>] genl_rcv_msg+0x79/0xc0
 1857.763467]  <ffffffff814e7c89>] netlink_rcv_skb+0xa9/0xc0
 1857.763470]  <ffffffff814e80bf>] genl_rcv+0x1f/0x30
 1857.763473]  <ffffffff814e72d4>] netlink_unicast+0xd4/0x180
 1857.763476]  <ffffffff814e769c>] netlink_sendmsg+0x31c/0x750
 1857.763481]  <ffffffff814a7754>] sock_sendmsg+0x94/0xd0
 1857.763485]  <ffffffff814a7b88>] ___sys_sendmsg+0x3b8/0x3d0
 1857.763489]  <ffffffff814a85e9>] __sys_sendmsg+0x39/0x70
 1857.763493]  <ffffffff815adfed>] system_call_fastpath+0x1a/0x1f
 1857.763499]  <00007f3c411c19c0>] 0x7f3c411c19bf
 1857.763500] --- end trace a3052239fec6d6e5 ]---
 1859.765465] iwlwifi 0000:06:00.0: Error sending TXPATH_FLUSH: time out after 2000ms.
 1859.765469] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 85
 1859.765471] iwlwifi 0000:06:00.0: Failed to send flush command (-110)
 1859.765474] ------------ cut here ]------------
 1859.765493] WARNING: CPU: 1 PID: 727 at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.10/linux-3.11/net/mac80211/sta_info.c:839 __sta_info_destroy+0x20b/0x390 [mac80211]()
 1859.765495] Modules linked in: fuse rfcomm vboxpci(O) vboxnetadp(O) vboxnetflt(O) af_packet xt_pkttype xt_LOG xt_limit ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables vboxdrv(O) xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables bnep arc4 nls_iso8859_1 nls_cp437 vfat fat tpm_infineon snd_hda_codec_realtek snd_hda_codec_hdmi uvcvideo videobuf2_core x86_pkg_temp_thermal videodev coretemp videobuf2_vmalloc videobuf2_memops kvm_intel snd_hda_intel snd_hda_codec kvm iwlmvm snd_hwdep crc32_pclmul ghash_clmulni_intel mac80211 snd_pcm aesni_intel ablk_helper iTCO_wdt cryptd snd_seq iTCO_vendor_support rtsx_pci_sdmmc rtsx_pci_ms
 1859.765524]  mmc_core memstick lrw gf128mul snd_timer glue_helper aes_x86_64 iwlwifi r8169 snd_seq_device btusb cfg80211 firewire_ohci sr_mod i2c_i801 serio_raw joydev pcspkr cdrom mii bluetooth snd firewire_core rtsx_pci lpc_ich crc_itu_t mfd_core rfkill mei_me mei soundcore snd_page_alloc shpchp battery tpm_tis tpm tpm_bios acpi_cpufreq ac mperf sg dm_mod autofs4 efivarfs btrfs raid6_pq zlib_deflate xor libcrc32c crc32c_intel nouveau i915 ttm drm_kms_helper drm xhci_hcd mxm_wmi i2c_algo_bit thermal wmi video button processor thermal_sys scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw scsi_dh
 1859.765560] CPU: 1 PID: 727 Comm: wpa_supplicant Tainted: G        W  O 3.11.10-21-desktop #1
 1859.765561] Hardware name: Notebook                         P15SM-A/SM1-A                    /P15SM-A/SM1-A                    , BIOS 4.6.5 02/14/2014
 1859.765562]  0000000000000009 ffffffff815a0392 0000000000000000 ffffffff81050eb2
 1859.765565]  ffff8803ee109000 ffff88041931c5e0 ffff88041a28a800 00000000ffffff92
 1859.765568]  ffff88041a28a800 ffffffffa079e0ab ffff88041931c838 ffff88041931c838
 1859.765570] Call Trace:
 1859.765580]  <ffffffff81004a28>] dump_trace+0x88/0x310
 1859.765584]  <ffffffff81004d80>] show_stack_log_lvl+0xd0/0x1d0
 1859.765587]  <ffffffff810061bc>] show_stack+0x1c/0x50
 1859.765592]  <ffffffff815a0392>] dump_stack+0x50/0x89
 1859.765598]  <ffffffff81050eb2>] warn_slowpath_common+0x72/0x90
 1859.765607]  <ffffffffa079e0ab>] __sta_info_destroy+0x20b/0x390 [mac80211]
 1859.765627]  <ffffffffa079e345>] sta_info_flush_defer+0x75/0xa0 [mac80211]
 1859.765645]  <ffffffffa07d5b45>] ieee80211_set_disassoc+0xa5/0x3c0 [mac80211]
 1859.765701]  <ffffffffa07d9084>] ieee80211_mgd_deauth+0x244/0x2b0 [mac80211]
 1859.765753]  <ffffffffa056fe76>] cfg80211_mlme_deauth+0x96/0x1b0 [cfg80211]
 1859.765781]  <ffffffffa0558bfc>] nl80211_deauthenticate+0xcc/0x120 [cfg80211]
 1859.765792]  <ffffffff814e8249>] genl_family_rcv_msg+0x179/0x360
 1859.765796]  <ffffffff814e84a9>] genl_rcv_msg+0x79/0xc0
 1859.765799]  <ffffffff814e7c89>] netlink_rcv_skb+0xa9/0xc0
 1859.765802]  <ffffffff814e80bf>] genl_rcv+0x1f/0x30
 1859.765805]  <ffffffff814e72d4>] netlink_unicast+0xd4/0x180
 1859.765808]  <ffffffff814e769c>] netlink_sendmsg+0x31c/0x750
 1859.765813]  <ffffffff814a7754>] sock_sendmsg+0x94/0xd0
 1859.765817]  <ffffffff814a7b88>] ___sys_sendmsg+0x3b8/0x3d0
 1859.765821]  <ffffffff814a85e9>] __sys_sendmsg+0x39/0x70
 1859.765825]  <ffffffff815adfed>] system_call_fastpath+0x1a/0x1f
 1859.765831]  <00007f3c411c19c0>] 0x7f3c411c19bf
 1859.765833] --- end trace a3052239fec6d6e6 ]---
 1861.767841] iwlwifi 0000:06:00.0: Error sending MAC_CONTEXT_CMD: time out after 2000ms.
 1861.767851] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 86
 1861.767857] iwlwifi 0000:06:00.0: Failed to send MAC context (action:2): -110
 1861.767862] iwlwifi 0000:06:00.0: failed to update MAC 0c:8b:fd:6c:87:66
 1863.770169] iwlwifi 0000:06:00.0: Error sending REMOVE_STA: time out after 2000ms.
 1863.770179] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 87
 1863.770185] iwlwifi 0000:06:00.0: Failed to remove station. Id=1
 1863.770190] iwlwifi 0000:06:00.0: failed to remove AP station
 1865.772430] iwlwifi 0000:06:00.0: Error sending TIME_QUOTA_CMD: time out after 2000ms.
 1865.772441] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 88
 1865.772447] iwlwifi 0000:06:00.0: Failed to send quota: -110
 1865.772451] iwlwifi 0000:06:00.0: failed to update quotas
 1867.774820] iwlwifi 0000:06:00.0: Error sending POWER_TABLE_CMD: time out after 2000ms.
 1867.774830] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 89
 1867.774836] iwlwifi 0000:06:00.0: failed to update power mode
 1869.777053] iwlwifi 0000:06:00.0: Error sending MAC_CONTEXT_CMD: time out after 2000ms.
 1869.777057] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 90
 1869.777059] iwlwifi 0000:06:00.0: Failed to send MAC context (action:2): -110
 1869.777060] iwlwifi 0000:06:00.0: failed to update MAC 0c:8b:fd:6c:87:66
 1871.779480] iwlwifi 0000:06:00.0: Error sending BINDING_CONTEXT_CMD: time out after 2000ms.
 1871.779488] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 91
 1871.779495] iwlwifi 0000:06:00.0: Failed to send binding (action:3): -110
 1871.781684] cfg80211: Calling CRDA to update world regulatory domain
 1871.786431] cfg80211: World regulatory domain updated:
 1871.786433] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
 1871.786435] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
 1871.786436] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
 1871.786437] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
 1871.786437] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
 1871.786438] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
 1873.792743] iwlwifi 0000:06:00.0: Error sending SCAN_REQUEST_CMD: time out after 2000ms.
 1873.792752] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 92
 1873.792758] iwlwifi 0000:06:00.0: Scan failed! status 0x1 ret -110
 1877.190721] iwlwifi 0000:06:00.0: Error sending SCAN_REQUEST_CMD: time out after 2000ms.
 1877.190735] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 93
 1877.190745] iwlwifi 0000:06:00.0: Scan failed! status 0x1 ret -110
 1900.218471] iwlwifi 0000:06:00.0: Error sending SCAN_REQUEST_CMD: time out after 2000ms.
 1900.218480] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 94
 1900.218486] iwlwifi 0000:06:00.0: Scan failed! status 0x1 ret -110
 1933.259928] iwlwifi 0000:06:00.0: Error sending SCAN_REQUEST_CMD: time out after 2000ms.
 1933.259934] iwlwifi 0000:06:00.0: Current CMD queue read_ptr 75 write_ptr 95
 1933.259938] iwlwifi 0000:06:00.0: Scan failed! status 0x1 ret -110

I have also NetworkManager log, wpaSupplicant.log, and the complete dmesg. Let me know if they are needed.

Thanks in advance for any hint you can give me.

I posted a really long and eloquent reply that seems to have been eaten! SUffice to say I am having the exact same issue and would appreciate any info about it. I can also supply log dumps and so on.

For me, it’s only started to happen from about a week ago (before that was fine) - how about you?

OK, a bit of an update:

] I still get the issue on my previous kernel of 3.11.10-17-desktop (handily available from “Advanced options” on the Grub boot screen)

] “iwconfig” command reports a LOT of “Tx excessive retries” and “invalid misc” when WiFi is working

] Looking here http://www.intel.com/support/wireless/wlan/sb/CS-034398.htm I see that kernel 3.13+ loads a different driver. I’ve had a look at these two drivers and it looks like the one for kernel 3.10+ isn’t technically for the 7260 hardware. Hmmm…

] In theory, the hardware could be loose / fried which is something I haven’t yet looked at

So I guess we have to wait for the 3.13 kernel, or somehow load the newer driver instead.

:-/

To clarify it looks like iwlwifi-7260-7.ucode in /lib/firmware has been updated very recently by the kernel-firmware package. I am sure this is the culprit due to the timing of that updating and then my WiFi going bad. Though I have tried downgrading both the kernel and the firmware (individually and together) but the problem still persists.

Some of my testing might have been flawed however (too tired and confused to concentrate!).

The saga continues…

I have had this problem for over a month :confused: . What is a high number of Tx excessive retries? After an hour of use, I have 10000 retries, and 2000 invalid misc.
Do you have any kind of problem connecting to wireless nets which broadcast in N at 5ghz?

I’m getting even higher retry and invalid misc numbers :frowning:

Yes, even Windows heads are having problems with this card and driver. One of the things they mention is to try it at 5GHz. I won’t be able to do that very quickly, but I will give it a shot.

About a month ago is when the kernel updated. And the “kernel-firmware” package updated about a week after that. I wonder what is the date and filesize of your /lib/firmware/iwlwifi-7260-7.ucode file?

Although I’ve tried a couple of rollbacks of kernel-firmware and I still get the issue. I’m starting to think my hardware is fried.

In the short term I’m going to have to use cabled LAN (which is a pain) and in the long term I’m going to replace my laptop’s 7260 with a more reliable Atheros card.

I don’t see a quick or easy solution to this issue unfortunately :frowning: :frowning:

683236 Aug 18 05:20 /lib/firmware/iwlwifi-7260-7.ucode

I have a dual boot with windows 8 and from time to time it has problems to connect as well. Some other times it connects fine. I have tried to connect to a 5GHz network and it is even more unreliable than a 2.4GHz network.

What makes you think that it is a hardware problem?

Thanks, I’m on the same firmware. Older firmwares haven’t fixed the issue though.

Another avenue I’m looking at is it might be interference from my Chromecast…

Sorry for the delay, here’s an update blast:

] Chromecast (which can only use the 2.4GHz band) was not causing a problem
] Switching to 5GHz worked better but the issue was still present
] I see that my 2.4GHz band is VERY congested with stuff from neighbours, but I was the only thing on the 5GHz band…
] …Which made me think it was to do with noisy / weak signals (my laptop is upstairs but the router is downstairs)…
] …so I’ve started using a more powerful dual band router which gives me a much stronger signal
] Using the 5Ghz band on the new router seems to have fixed things! I’ve been streaming music for nearly 24 hours uninterrupted!
] I still get quite high “excessive retries” accumulating, but a much smaller amount of “invalid misc”

How about you? Is your laptop quite far from your router? A congested network?

PS. I still think the kernel driver or firmware is dodgy because when the issue does happen, restarting NetworkManager (systemctl restart NetworkManager) often - but not always - gets the network back online.

Good to hear that it is working for you!
Sadly it does not work for me yet. I’m pretty near the router, and with 5ghz the connection works even worse. Right now I could not scan the 5ghz networks (I even tried restarting). I switched to windows 8 and I could connect without a problem. I’ve signed back to openSuse and then I could see the 5ghz network but I could not connect. This makes me think that it is a problem with the firmware and not with the card.
I’m going to try with a newer kernel because I saw somewhere (I can’t find the link right now) that some fixes were made for this NIC.

I’ll post here if it works better.

Oh dear. I haven’t been able to replicate that glorious first 24 hours of perfect 5Ghz connection. My laptop is now struggling to connect to the 5GHz band at all! It doesn’t have any errors or fails in the log, but it doesn’t seem to actually connect to the 5Ghz band.

I can connect to 2.4Ghz but I presume that will have the same issues as before.

This bloody card!

By the way, how are you updating the kernel? The “Factory” thing of openSUSE or just switching to a different distro?

Either way, please let me know how you get on with the updated firmware :-/

Hello folks,
I’ve been watching this with great curiosity. Ubuntu 14.04 doesn’t seem to have this problem for me and the wireless works great. I do prefer the “YAST” lifestyle though.:wink:

My uptime was 15mins and had Tx excessive retries:2722. All the same firmware appears to be there, as far as I know. Curious to know the difference, I assume it is the kernel? Could a kernel update via the software center be the way to go? Or is it something more than that?

Thanks,

Dave

Hi Cuttlefish,

Glad you like our curious problem!

You make me wonder (even more than I already was) about a couple of things:

] If it’s the kernel driver - on the same firmware - causing problems rather than the firmware itself

] If it’s NetworkManager causing problems

I’ve had another good day on 5Ghz yesterday, but my testing time is quite reduced now due to starting a new job.

It’s disappointing not to see any official openSUSE replies about this issue as, in the short term, scrapping openSUSE and installing Ubuntu seems to solve the issue :-/

PS. Yast for the win!

Well, I upgraded my kernel via the web.

http://software.opensuse.org/package/kernel-desktop

and chose 3.13.6 to no avail, but then tried Alsbz 3.16.2 and observed: Tx excessive retries:2 Invalid misc:42 Missed beacon:0 in about 45 mins. as far as I’m concerned, so far so good.

Any new developments and I’ll post here.

Dave

Aha~, Package Search - I should have known! Good to know you’ve got some improvement. Myself I’m a bit conservative and don’t really want to change my kernel version yet.

Well I suspect now that this is a lot to do with something in the chain (router, firmware, driver) not liking congested networks / low power signals.

I’ve been having a stable connection so far on my new router using 5GHz and with “Protected Mode” switched to ON. My router’s Protected Mode is something to do with improving stability in congested networks. (Though my 5Ghz space is not at all congested - unlike my 2.4GHz space!)

So I’m in the situation now where things appear to have corrected themselves but I don’t really know why! I still get more excessive retries than I would like, though I’m not sure anymore that measuring those things is helpful!

**fsuzacq, you said you had the same issue on 5Ghz. Is your 5GHz space congested or not? Would love to know…

**

danielrhodes: I’m glad you seem to be getting things sorted out.

I’m battling a few things right now on my new laptop (Lenovo T440P 20AW004JUS) and I’m trying to isolate my issues. Even with the new kernel and it’s SSD (INTEL SSDSC2BF18) optimised I began to experience an extreme slowdown on 13.1, mostly on firefox rendering. It was gradual. It may be due to how I tried to tweak it. There were two options that I tried to limit the write actions of Firefox, but that is another topic. :slight_smile: I only tried one of them on 13.1, and that might be the difference…still learning.

Back to the wireless thing. I’ve had much better success with Fedora 20 than with Ubuntu 14.04. That also may be because I’m a Gnome 3 user. I also don’t readily connect to the 5 GHz signal from my wireless. I don’t know if that is related to my router set up or 7260 AC wireless card itself or that is to be expected.

Right now I’m “playing” with 13.2 Live USB and things are improving. I think that 13.2 will be a fine release and looking forward to it and will probably jump back onto that after testing it. I will need to install it soon to test it properly, once I have the time. :wink:

Dave

UPDATE:

This thread may be too old to be replying to, but I wanted to mention that i have installed kernel 3.19.0.3-desktop via Package Search, to my 13.2 gnome install and my wireless seems to be behaving as it should. Both my 2.4 and 5 GHz band are good.

Thanks for the update Cuttlefish, that’s good to know.

I was a bit to early to report that everything had started working on the 5GHz band. After heavy use, things started to bork again. I’ve had to run a LAN cable from my router downstairs to my laptop upstairs!

So I will definitely check your information out :wink:

Managed to have a very quick play on the 13.2 live GNOME variant over the weekend. That had kernel 3.16 (I’m still on 13.1 with kernel 3.11) and my 2.4GHz wifi seemed to work quite well! I didn’t see any “excessive retries” at all! Though I didn’t stay using it for very long. Nor did I try 5GHz wifi.

In fact, 13.2 on the whole looks VERY nice and I’ll probably upgrade! I was sticking with 13.1 arbitrarily for the long-term support…

Kernels, you can’t live with 'em, can’t live without 'em :wink: