Created attachment 192391 [details] Intel 7260 crash error System info: - Lenovo Ideapad U330 touch - Slackware 14.1 64 bit - vanilla linux kernel 4.3.0 from kernel.org Problem: The integrated wireless network adapter (intel 7260) randomly crashes with the attached dmesg output. The loaded firmware is version 17: iwlwifi 0000:02:00.0: loaded firmware version 17.228510.0 op_mode iwlmvm If you need any other info, just ask.
Created attachment 192401 [details] Dmesg output
Created attachment 192701 [details] Core14 FW with uSniffer Please reproduce with the firmware attached. Please run with fw_restart=0 This means that we won't recover after the first failure. This will allow me to correlate between the different logs. 1) Tracing 2) The dump file that will be created when the FW crashes Information on how to collect this is available here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging please read the note about privacy.
Sent debug files using modified firmware and with fw_restart=0. Let me know if you need more info.
Can you try to disable Bluetooth?
I received your data. Thank you. We will look at it shortly.
(In reply to Emmanuel Grumbach from comment #4) > Can you try to disable Bluetooth? The notebook doesn't have a physical switch to turn off the bluetooth, but "rfkill list" return this: 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no I can try to block the bluetooth through "rfkill block 1" and/or "rfkill block 3", are they the same?
I can't tell...
Blocked the bluetooth through rfkill: 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: yes Hard blocked: no Can't see any notable difference (firmware crashes still there).
Thanks. Can you please let me know if 11n_disable=1 as a module parameter helps? I have analyzed the data but I need the firmware team to look at it. It may take a bit of time. Thank you for your patience.
Even with "11n_disable=1" parameter, the firmware still crash.
Can you please try to disable power save? sudo iw wlan0 set power_save off If that helps, I'd like to provide a firmware with more probes to debug this a bit further. Thank you.
I already tried that some time ago without any success, but I will retry during the weekend. One more question: do you need any trace/log/dump after disabling power save?
Ok thanks. No need, I have a another user in another bug who is providing logs. It may be a different issue, but for now, I prefer to work with one person at a time. I really appreciate your readiness / willingness to help. Thank you.
Even disabling power save, the firmware still crash.
Created attachment 195801 [details] Core14 FW with uSniffer with TX_MNG probes Hi, can you please create another dump with the firmware attached? Thanks.
Sorry for the late reply, but I have been very busy these days. I will try to send you the new dump this week end.
Sent dump file as requested. I also noticed a strange "iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7260-exp.ucode' failed." in dmesg after copying the modified firmware.
Thanks - I'll take a look tonight. the print you saw is not a problem.
Ok - your environment seems extremely noisy. Do other client work successfully in the same environment? What happens here is that we try to transmit data, but constantly feel energy in the air, so we stop the transmission. This pattern happens over and over. I am forwarding the data to the firmware team. Thanks for your cooperation!
*** Bug 108271 has been marked as a duplicate of this bug. ***
*** Bug 107861 has been marked as a duplicate of this bug. ***
> Do other client work successfully in the same environment? Yes, tested with some smartphones, an xbox-one and an ath9k chipset card (all connected simultaneously). All these clients are working as expected in this environment. > What happens here is that we try to transmit data, but constantly feel > energy in the air, so we stop the transmission. This pattern happens over > and over. I can't really know what to say here. In the area there aren't much other wireless networks, there aren't microwaves ovens or other devices known to create electromagnetic fields. Last note: I can't remember if someone was playing some online FPS games on the xbox while I was collecting the dump; however I can say the other devices listed above was working as expected. > I am forwarding the data to the firmware team. Thanks for the support.
Upgraded to kernel 4.3.3, but the problem still there.
This is a firmware bug. Upgrading the kernel without firmware upgrade won't help. I just released -19.ucode, with giving it a try, but I doubt it will solve your problems.
> I just released -19.ucode, with giving it a try, but I doubt it will solve > your problems. The most recent firmware I can see is "iwlwifi-7260-17.ucode", the -19 might be the "iwlwifi-7265-19.ucode", but for what I can understand it's for 7265 cards (while mine is 7260). Am I missing something? Moreover I think the maximum firmware version supported by the kernel 4.3.x is -17. > This is a firmware bug. Upgrading the kernel without firmware upgrade won't > help. Yes, I know. Take the previous message as "I want to let you know that now I'm using kernel 4.3.3.". I will add other messages like this one when I upgrade important parts of my system to keep you informed.
You are right twice. I forgot that there is no 19.ucode for 7260. Thanks for letting me know you upgraded you're kernel.
*** This bug has been marked as a duplicate of bug 103531 ***