Created attachment 283091 [details] dmesg Intel 8265 firmware 36.9f0a2d68.0 crashing regularly w/ "Error sending STATISTICS_CMD: time out after 2000ms". bssid=bc:26:c7:xx:xx:xx freq=5260 ssid=xxxxxxx id=0 mode=station pairwise_cipher=CCMP group_cipher=CCMP key_mgmt=WPA2-PSK wpa_state=COMPLETED ip_address=10.191.40.19 p2p_device_address=d0:c6:37:xx:xx:xx address=d0:c6:37:xx:xx:xx ieee80211ac=1 VHT 20MHz channels. Mixed 2.4/5GHz Strangely no "devcoredump" directory: >> ls /sys/devices/virtual/ bdi block dmi graphics input mem misc net powercap pps sound thermal tty vc vtconsole workqueue >> ls /sys/kernel/debug/iwl* ls: cannot access '/sys/kernel/debug/iwl*': No such file or directory I also tried debug-fw from here (but also no dump available): https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging
please provide the output of tracing: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#tracing
What is the value of the d0i3_disable module parameter? cat /sys/module/iwlwifi/parameters/d0i3_disable
Me again, looks like you have it enabled... Strange. Should be disabled by default. Can you check /etc/modprobe.d/iwlwifi.conf ? From what I see, in the BAT mode, runtime PM is enabled, and then we fall on our nose because we don't get the interrupts anymore.
Ok, thanks. Actually I try figuring out if I can enable tracing stuff remotely at the customers site. >> /etc/modprobe.d/iwlwifi.conf options iwlwifi lar_disable=1 swcrypto=1 >> grep [[:alnum:]] /sys/module/iwl*/parameters/* /sys/module/iwlmvm/parameters/init_dbg:N /sys/module/iwlmvm/parameters/power_scheme:2 /sys/module/iwlmvm/parameters/tfd_q_hang_detect:Y /sys/module/iwlwifi/parameters/11n_disable:0 /sys/module/iwlwifi/parameters/amsdu_size:0 /sys/module/iwlwifi/parameters/antenna_coupling:0 /sys/module/iwlwifi/parameters/bt_coex_active:Y /sys/module/iwlwifi/parameters/d0i3_disable:Y /sys/module/iwlwifi/parameters/d0i3_timeout:1000 /sys/module/iwlwifi/parameters/disable_11ac:N /sys/module/iwlwifi/parameters/disable_11ax:N /sys/module/iwlwifi/parameters/enable_ini:N /sys/module/iwlwifi/parameters/fw_monitor:N /sys/module/iwlwifi/parameters/fw_restart:Y /sys/module/iwlwifi/parameters/lar_disable:Y /sys/module/iwlwifi/parameters/led_mode:0 /sys/module/iwlwifi/parameters/nvm_file:(null) /sys/module/iwlwifi/parameters/power_level:0 /sys/module/iwlwifi/parameters/power_save:N /sys/module/iwlwifi/parameters/remove_when_gone:N /sys/module/iwlwifi/parameters/swcrypto:1 /sys/module/iwlwifi/parameters/uapsd_disable:3 I execute "iw dev wlp1s0 set power_save off" on startup of our software. Historically we have "intel_idle.max_cstate=1" in grub commandline. CPU is a Intel(R) Core(TM) i5-6300U CPU, but the system is AC powered, not running on a battery. P.S. "PM" == power management. But what is "BAT mode"? Battery? Batch?
Sorry, I commented on the wrong bug. I'll need the tracing output. D0i3 is disabled, this is good.
>> trace-cmd: No such file or directory >> No events enabled with iwlwifi Do I need to compile the module on my own, or is there any module option I need to activate?!
you compiled iwlwifi w/o TRACING. So yes, please recompile with tracing enabled.
Sorry to bother again. I compiled this https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/log/?h=release/core33 When I try to load it, I get this: [ 1844.283780] iwlwifi: loading out-of-tree module taints kernel. [ 1844.284048] iwlwifi: module verification failed: signature and/or required key missing - tainting kernel [ 1844.284499] iwlwifi: Unknown symbol backport_dependency_symbol (err -2)
Created attachment 283111 [details] backport_iwlwifi config
Take the master branch of the backport tree. Not sure what is the error you're seeing.
Created attachment 283113 [details] dmesg with self compiled iwlwifi I'm a little stuck here :-( >>Kernel: linux-image-5.0.0-trunk-amd64 >>Headers: linux-headers-5.0.0-trunk-amd64 git clone https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git make defconfig-iwlwifi-public make -j4 Result is: >>version: iwlwifi-stack-public:master:7815:8c5dd2fa >>vermagic: 5.0.0-trunk-amd64 SMP mod_unload modversions make install & reboot. --- My dev-system now is connected BUT >>iwconfig wlp1s0 no wireless extensions. >>wavemon -i wlp1s0 wavemon: no supported wireless interfaces found! --- I cannot use it at the customer (where the problem happens) in this state :-( Any ideas? P.S. "trace-cmd" now works (but no crashes here in my office) :-) P.P.S. my realtek wifi dongle doesn't work any more - see demsg. This would be ok for tracing...
yes, to use backport, you can't have any other device connected to the system. You use wireless extensions?! This is super old interface. Select "cfg80211 wireless extensions compatibility" in menuconfig.
To be honest - till now I was simply using "Debian" and did not care about such details. This radically changes right now ;-) I had to update parts of my software avoid using "iwconfig" (at least the version of iwconfig in my Debian does not work w/o wireless-extensions). I'll update customer's PC within the next hour and then start the trace. Fingers crossed this will work remotely via LTE connection ^^
Strange - it's now recording since 2 hours but not crashing. Once I got "Got an HT rate (flags:0x8a/mcs:10) for a non data frame", but that's already in another bug report: https://bugzilla.kernel.org/show_bug.cgi?id=203663 So I guess my bug is fixed in a new version of iwlwifi/iwlmvm? If so - can I simply build a fully working module for the 8265?
(In reply to lukas.redlinger from comment #14) > Strange - it's now recording since 2 hours but not crashing. > > Once I got "Got an HT rate (flags:0x8a/mcs:10) for a non data frame", but > that's already in another bug report: > https://bugzilla.kernel.org/show_bug.cgi?id=203663 > > > So I guess my bug is fixed in a new version of iwlwifi/iwlmvm? If so - can I > simply build a fully working module for the 8265? What does that mean?
(In reply to Emmanuel Grumbach from comment #15) > What does that mean? ??? It was crashing at least once every hour with the iwlwifi module shipped with Debian kernel 4.19/5.0.0-exp. Now i compiled the backport-thing only to enable tracing ("trace-cmd record -e iwlwifi") - but not only it enables tracing, but it also seems to fix the issue. Is this to be expected?
well... have you tried to run tracing? Tracing should be changing anything. the backport tree is our latest driver, so it may be that the bug was fixed there and not sent upstream yet. But that would be surprising.
(In reply to Emmanuel Grumbach from comment #17) >> well... have you tried to run tracing? >> Tracing should be changing anything. yes, trace-cmd is running and recording about ~300MB/hour to my disk. But since I'm using the backport-module, it did not crash at all. root@xxxxxxxx:~# trace-cmd record -e iwlwifi Hit Ctrl^C to stop recording >> the backport tree is our latest driver, so it may be that the bug was fixed >> there and not sent upstream yet. But that would be surprising. The question is, which version of the module the debian guys ship?! It crashed with the module in 4.19 as well as with the module from their 5.0.0-experimental kernel. # modinfo iwlwifi doesn't give any hint which version it could be on my debian system... P.S. I have 3 systems at this customer. 2 are still crashing the driver regularely. The other one got the backport-module and stopped crashing (but the module prevents me using a realtek-usb-wifi dongle + is only using US regom; so cannot be used productive).
You don't really understand what the backport tree is it seems. The backport tree is our driver as we develop internally. Then the patches are sent to the upstream kernel and debian just takes the upstream kernel. The process of sending the patches from our backport tree to the kernel is manual. If you can reproduce the problem easily, you can try to bisect the backport tree to try to see which patch fixed it. It may not be easy because if you go back in time, you may face problems compiling the old backport on a newer kernel. Regarding the fact that you can't ship the backport-module because of the realtek devive, I can understand, this is a limitation of the backport tree.
Ok - so my only chance of having a recent version of iwlwifi is have a recent kernel. So debian cannot be the distribution of my choice any longer. And for this very bug, it seems that it was fixed after "5.0.0-trunk-amd64 #1 SMP Debian 5.0.2-1~exp1" as: - The two mentioned systems running that very kernel (with the iwlwifi module that came with it) still crash regularly (11:41am, 12:32pm, 1:06pm, 1:26pm, 2:33pm). - The other one with the backport iwlwifi stopped crashing.
I just pushed a fix for our backport tree that you probably want. We had a bug in the d0i3 setting.
How do we make progress here?
I just set up a system in the office using "5.1.9-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 11 16:18:09 UTC 2019 x86_64 GNU/Linux". I hope I can record a useful trace for you. At least tracing is enabled in arch, so I can start recording immediately!
[12121.124871] / [Mon Jun 17 13:43:37 2019] iwlwifi 0000:01:00.0: Error sending STATISTICS_CMD: time out after 2000ms. 5.1.9-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 11 16:18:09 UTC 2019 x86_64 GNU/Linux dmesg updated trace: https://drive.google.com/open?id=1gmPlm39Eg-BkJSIDyOoXfOeJRNC4PoPU sorry - huge file. It took some hours before it happened.
Created attachment 283301 [details] dmesg
(In reply to lukas.redlinger from comment #24) > [12121.124871] / [Mon Jun 17 13:43:37 2019] iwlwifi 0000:01:00.0: Error > sending STATISTICS_CMD: time out after 2000ms. > > 5.1.9-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 11 16:18:09 UTC 2019 x86_64 > GNU/Linux > > dmesg updated > > trace: https://drive.google.com/open?id=1gmPlm39Eg-BkJSIDyOoXfOeJRNC4PoPU > sorry - huge file. It took some hours before it happened. no access to this.
sry - try again please
can you please enable record with iwlwifi_msg... ?
started again with "trace-cmd record -e iwlwifi -e iwlwifi_msg"
Created attachment 283315 [details] dmesg
[ 858.508629] iwlwifi 0000:01:00.0: Error sending STATISTICS_CMD: time out after 2000ms. [ 858.508635] iwlwifi 0000:01:00.0: Current CMD queue read_ptr 190 write_ptr 191 next trace. with iwlwifi + iwlwifi_msg https://drive.google.com/file/d/1iA9X_ipTEk8UHpTdmQCh9wD9FYS1zgJJ/view?usp=sharing
What platform is that? We just stop getting any interrupts. Are
Sorry, hit the button too early. What happens here is that we stop getting interrupts and we blow up on timeout. We could try to look at the RxFIFO to see if the firmware replied to our commands. For this, you'd need to configure the FW debug infra: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging I hope / guess you have udev on your system. Then you can install the udev rule to dump the data that will be collected upon FW crash.
Created attachment 283317 [details] iwl.dump I guess the file might be useless as I actived "fw_dbg_collect" _after_ the crash, but the devcoredump-structure appeared and I could fetch this file.
so a file should have have been created upon the: Error sending STATISTICS_CMD: time out after 2000ms. error. When that happens, the driver trigger a firmware dump as well.
The driver crashed half an hour ago, but /sys/devices/virtual/devcoredump did not exist at all. It appeared after echoing "1" to /sys/kernel/.../fw_dbg_collect". So automatic dumping apperently doesn't work in this case :-( >What platform is that? Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz http://www.cincoze.com/data/files/201803/Datasheet_DI-1000_20180109.pdf Anything else we can do? Disabling some PCIe power saving stuff? Of is this a major hardware issue of our box?! Thanks in advance!
Created attachment 283411 [details] iwl-fw-error.dump It stopped happening on our vehicles, but heavily occurs at a customer's site today. Kernel version is a little different - 5.1.2-arch1-1-ARCH #1 SMP PREEMPT kernel: iwlwifi 0000:01:00.0: Error sending STATISTICS_CMD: time out after 2000ms. kernel: iwlwifi 0000:01:00.0: Current CMD queue read_ptr 73 write_ptr 74 Hope this dump helps?
Created attachment 283423 [details] iwl-fw-dump linux 5.1.8 Over night it again occured at one of our vehicles: 2019-06-24_23-49-00.dump 2019-06-25_01-55-12.dump 2019-06-25_02-09-09.dump 2019-06-25_02-25-45.dump 2019-06-25_02-36-21.dump 2019-06-25_04-12-36.dump 2019-06-25_06-40-44.dump 5.1.8-arch1-1-ARCH #1 SMP PREEMPT Jun 25 06:40:44 kernel: iwlwifi 0000:01:00.0: Error sending STATISTICS_CMD: time out after 2000ms. Jun 25 06:40:44 kernel: iwlwifi 0000:01:00.0: Current CMD queue read_ptr 242 write_ptr 243 I'm attaching the last one
New dumps + dmesg from today on gdrive. Happened 7 times from 07:55 - 09:23. Arch Linux 5.1.9 Loaded firmware version: 36.8fd77bb3.0 (should be the one with TDLS disabled). Download here: https://drive.google.com/drive/folders/1cohzLBbWAOowZJVIT5HoC0pt0dr8PY6M?usp=sharing
Crashes still happen within temperature of card in spec (<75°C). In the meantime the kernel was upgraded to 5.1.16-arch1-1-ARCH. Are there any investigations going on, or are we out of luck now? Thank you, Thomas (as substitute of Lukas)
On systems that have been brought to temperature that higher than the spec? If so, I consider them damaged. Also, how did you configure ASPM? How did you run the PCI integration? You can't just plug the NIC and assume all will work because it's PCI.
Its affecting brand new and cool cards also. ASPM is set to "default", which refers to BIOS defaults. But we have no BIOS ASPM setting to be modified. We will try with pcie_aspm=off. We don't know, how the manufacturer has done the PCI integration. We buy ready to use industrial pc's.
Ok, so please reproduce on brand new system under normal conditions. Then please produce the dmesg / trace-cmd / fwdump of a run (all those should be from the same run) then I'll take a look.
New logs from a customers site equipped w/ Cisco infrastructure. trace-cmd was running w/ "record -e iwlwifi -e iwlwifi_msg". > industrial PCs equipped with heatsink connecting the wifi card to it's > housing > running 5.2.3-arch1-1-ARCH #1 SMP PREEMPT Fri Jul 26 08:13:47 UTC 2019 x86_64 > brand new Intel 8265 cards > firmware 36.8fd77bb3.0 > temperatures of wifi cards around 60°C but always within spec (<80°C). IPC Cincoze DI-1000: https://solutionsdirectory.intel.com/member-roster/Cincoze_Co_Ltd All logs from the same run (last one in dmesg: 245530.502044 after boot). Download here: https://drive.google.com/open?id=1wZnyl2lAaiRoPepFK84KtHO4vGKgwfkM
This could be related to TX-AMSDU, which we unfortunately had to disable for older devices. Can you try this and see if it helps you with stability? https://patchwork.kernel.org/patch/11029027/
I tried linux-5.2.11-arch1 (https://git.archlinux.org/linux.git/log/?h=v5.2.11-arch1) which includes this patch. After 15 minutes it crashed again - so no changes: [Wed Sep 4 15:48:05 2019] iwlwifi 0000:01:00.0: Error sending STATISTICS_CMD: time out after 2000ms. [Wed Sep 4 15:48:05 2019] iwlwifi 0000:01:00.0: Current CMD queue read_ptr 122 write_ptr 123 I've just now set up the fwdump udev rule. So next time I'll have a fw dump too.
Created attachment 284847 [details] dmesg 36.77d01142.0 + disable TX-AMSDU I updated the firmware too. Now using 36.77d01142.0. I took some hours, but crashes still happening.
Created attachment 284849 [details] fw dump linux 5.2.11, disable TX-AMSDU
Created attachment 285113 [details] dmesg with call trace I have this issue on Arch with kernel 5.3.1. My config: description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@0000:05:00.0 logical name: wlp5s0 version: 29 serial: 0c:54:15:96:15:c7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.3.1-arch1-1-ARCH firmware=46.93e59cf4.0 ip=192.168.1.63 latency=0 link=yes multicast=yes wireless=IEEE 802.11
I have to add 9260 and AX200 to the list of affected cards :-(
I must say I don't observe the problem with LTS 4.19.75 on Arch. Since it uses the same firmware on Arch as 5.3.1, I guess it is not a firmware problem.
Created attachment 285123 [details] LTS dmesg No, LTS is affected too but it took several hours.
Exactly this just started happening to me after updating Manjaro Linux and installing kernel 5.3 coming from 5.2.20 My hardware is: 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) If dmesg is needed or if I can help with anything please just ask, however my dmesg is *exactly* the same as OP's. I have heard in some places that it can be caused by PCIe RTPM however I have always had Runtime Power Management enabled for all my devices and it has never caused an issue until now. I also have set iwlwifi.power_Save=Y iwldvm.force_cam=N parameters set to enable powersaving mode on the adapter but again, this has never caused any issues in any of the previous kernels since 4.18 to 5.2, all the problems just started now with kernel 5.3.
Just downgraded to 5.2.20 again, bug is completely gone. Kernel 5.3 generates that bug OP posted, and kernel 5.4rc2 generates a totally different bug saying a hardware start was requested out of nowhere, but under exactly the same conditions as the "Error sending STATISTICS_CMD: time out after 2000ms" bug was happening under 5.2, as if the only thing that changed was the error message. Ill wait in kernel 5.2 meanwhile. If you need any other logs or anything, im willing to change kernel and provide them. Thanks in advance.
I am facing the same issue with 9260 since updating to Ubuntu 19.10 (with kernel 5.3). Everything was working fine previoulsy with Ubuntu 19.04 (except some rare freezes) and working perfectly fine with win10 (I have a dual boot). firmware version 46.6bf1df06.0 op_mode iwlmvm I have attached my log.
Created attachment 285699 [details] iwlwifi crash on ubuntu 19.10 with 9260
I am affected by this bug as well. I'm running Fedora 31, and my entire desktop freezes for several seconds whenever this happens. $ uname -a Linux dhcp-9-27-81-84 5.3.7-301.fc31.x86_64 #1 SMP Mon Oct 21 19:18:58 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lspci | rg Wire 03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) I'm going to upload my dmesg as well. Do you still need traces or other diagnostics? I'm happy to provide them, just let me know what would be useful!
Created attachment 285833 [details] Fedora 31 dmesg This log contains the crash information twice.
Don't know if it will work for you, but in my case I moved back to kernel 5.0.0-32 and since then it works perfectly (even better than when I was on ubuntu 19.04 with, I don't know which kernel). kernel 5.2 was buggy also on my side.
I can confirm this is happening on Arch Linux with kernel 5.3.11 and Intel AC 9260. The whole system freezes for about 5-10 seconds, and the following error is raised: [16430.615642] iwlwifi 0000:3b:00.0: Microcode SW error detected. Restarting 0x0. [16430.617447] iwlwifi 0000:3b:00.0: Start IWL Error Log Dump: [16430.617449] iwlwifi 0000:3b:00.0: Status: 0x00000080, count: 6 [16430.617450] iwlwifi 0000:3b:00.0: Loaded firmware version: 46.6bf1df06.0 [16430.617451] iwlwifi 0000:3b:00.0: 0x000022CE | ADVANCED_SYSASSERT [16430.617452] iwlwifi 0000:3b:00.0: 0x0590A2F0 | trm_hw_status0 [16430.617452] iwlwifi 0000:3b:00.0: 0x00000000 | trm_hw_status1 [16430.617453] iwlwifi 0000:3b:00.0: 0x0048853E | branchlink2 [16430.617454] iwlwifi 0000:3b:00.0: 0x00479392 | interruptlink1 [16430.617455] iwlwifi 0000:3b:00.0: 0x00000000 | interruptlink2 [16430.617455] iwlwifi 0000:3b:00.0: 0x0000012C | data1 [16430.617456] iwlwifi 0000:3b:00.0: 0x00000000 | data2 [16430.617457] iwlwifi 0000:3b:00.0: 0x04000000 | data3 [16430.617458] iwlwifi 0000:3b:00.0: 0x8E813025 | beacon time [16430.617458] iwlwifi 0000:3b:00.0: 0xD4C4AFDF | tsf low [16430.617459] iwlwifi 0000:3b:00.0: 0x00000020 | tsf hi [16430.617460] iwlwifi 0000:3b:00.0: 0x00000000 | time gp1 [16430.617460] iwlwifi 0000:3b:00.0: 0x487FD075 | time gp2 [16430.617461] iwlwifi 0000:3b:00.0: 0x00000001 | uCode revision type [16430.617462] iwlwifi 0000:3b:00.0: 0x0000002E | uCode version major [16430.617463] iwlwifi 0000:3b:00.0: 0x6BF1DF06 | uCode version minor [16430.617463] iwlwifi 0000:3b:00.0: 0x00000321 | hw version [16430.617464] iwlwifi 0000:3b:00.0: 0x00C89004 | board version [16430.617465] iwlwifi 0000:3b:00.0: 0x0000001C | hcmd [16430.617466] iwlwifi 0000:3b:00.0: 0xA7F938C0 | isr0 [16430.617466] iwlwifi 0000:3b:00.0: 0x00040000 | isr1 [16430.617467] iwlwifi 0000:3b:00.0: 0x00281802 | isr2 [16430.617468] iwlwifi 0000:3b:00.0: 0x404151CD | isr3 [16430.617468] iwlwifi 0000:3b:00.0: 0x00000000 | isr4 [16430.617469] iwlwifi 0000:3b:00.0: 0x0A81001C | last cmd Id [16430.617470] iwlwifi 0000:3b:00.0: 0x00486880 | wait_event [16430.617471] iwlwifi 0000:3b:00.0: 0x00004288 | l2p_control [16430.617471] iwlwifi 0000:3b:00.0: 0x00000020 | l2p_duration [16430.617472] iwlwifi 0000:3b:00.0: 0x00000000 | l2p_mhvalid [16430.617473] iwlwifi 0000:3b:00.0: 0x000000E7 | l2p_addr_match [16430.617474] iwlwifi 0000:3b:00.0: 0x0000000D | lmpm_pmg_sel [16430.617474] iwlwifi 0000:3b:00.0: 0x08081424 | timestamp [16430.617475] iwlwifi 0000:3b:00.0: 0x13E43838 | flow_handler [16430.618436] iwlwifi 0000:3b:00.0: Start IWL Error Log Dump: [16430.618437] iwlwifi 0000:3b:00.0: Status: 0x00000080, count: 7 [16430.618438] iwlwifi 0000:3b:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL [16430.618439] iwlwifi 0000:3b:00.0: 0x00000000 | umac branchlink1 [16430.618439] iwlwifi 0000:3b:00.0: 0xC008888E | umac branchlink2 [16430.618440] iwlwifi 0000:3b:00.0: 0xC0084414 | umac interruptlink1 [16430.618441] iwlwifi 0000:3b:00.0: 0xC0084414 | umac interruptlink2 [16430.618442] iwlwifi 0000:3b:00.0: 0x00000800 | umac data1 [16430.618442] iwlwifi 0000:3b:00.0: 0xC0084414 | umac data2 [16430.618443] iwlwifi 0000:3b:00.0: 0xDEADBEEF | umac data3 [16430.618444] iwlwifi 0000:3b:00.0: 0x0000002E | umac major [16430.618444] iwlwifi 0000:3b:00.0: 0x6BF1DF06 | umac minor [16430.618445] iwlwifi 0000:3b:00.0: 0x487FD26C | frame pointer [16430.618446] iwlwifi 0000:3b:00.0: 0xC088627C | stack pointer [16430.618447] iwlwifi 0000:3b:00.0: 0x00F8019C | last host cmd [16430.618447] iwlwifi 0000:3b:00.0: 0x00000000 | isr status reg [16430.618703] iwlwifi 0000:3b:00.0: Fseq Registers: [16430.618755] iwlwifi 0000:3b:00.0: 0x29967359 | FSEQ_ERROR_CODE [16430.618806] iwlwifi 0000:3b:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION [16430.618858] iwlwifi 0000:3b:00.0: 0x83FBE5CB | FSEQ_CNVIO_INIT_VERSION [16430.618909] iwlwifi 0000:3b:00.0: 0x0000A371 | FSEQ_OTP_VERSION [16430.618962] iwlwifi 0000:3b:00.0: 0xF213EBA0 | FSEQ_TOP_CONTENT_VERSION [16430.619013] iwlwifi 0000:3b:00.0: 0xF0B1000E | FSEQ_ALIVE_TOKEN [16430.619065] iwlwifi 0000:3b:00.0: 0x7BD335E7 | FSEQ_CNVI_ID [16430.619116] iwlwifi 0000:3b:00.0: 0xF5DA80D2 | FSEQ_CNVR_ID [16430.619168] iwlwifi 0000:3b:00.0: 0x01000200 | CNVI_AUX_MISC_CHIP [16430.619222] iwlwifi 0000:3b:00.0: 0x01300202 | CNVR_AUX_MISC_CHIP [16430.619276] iwlwifi 0000:3b:00.0: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [16430.619408] iwlwifi 0000:3b:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [16430.619592] iwlwifi 0000:3b:00.0: Collecting data: trigger 2 fired. [16430.619594] ieee80211 phy0: Hardware restart was requested [16430.619721] iwlwifi 0000:3b:00.0: FW error in SYNC CMD STATISTICS_CMD [16430.619724] CPU: 1 PID: 631 Comm: NetworkManager Not tainted 5.3.11-arch1-1 #1 [16430.619725] Hardware name: Dell Inc. XPS 15 9570/02MJVY, BIOS 1.13.0 08/22/2019 [16430.619725] Call Trace: [16430.619730] dump_stack+0x66/0x90 [16430.619740] iwl_trans_pcie_send_hcmd+0x547/0x560 [iwlwifi] [16430.619743] ? wait_woken+0x70/0x70 [16430.619749] iwl_trans_send_cmd+0x59/0xb0 [iwlwifi] [16430.619756] iwl_mvm_send_cmd+0x2e/0x80 [iwlmvm] [16430.619782] iwl_mvm_request_statistics+0x72/0xd0 [iwlmvm] [16430.619787] iwl_mvm_mac_sta_statistics+0x92/0xe0 [iwlmvm] [16430.619818] sta_set_sinfo+0xbc/0xa30 [mac80211] [16430.619830] ieee80211_get_station+0x51/0x70 [mac80211] [16430.619846] nl80211_get_station+0x8e/0x260 [cfg80211] [16430.619850] genl_family_rcv_msg+0x1f3/0x470 [16430.619852] genl_rcv_msg+0x47/0x90 [16430.619854] ? __kmalloc_node_track_caller+0x1c5/0x330 [16430.619855] ? genl_family_rcv_msg+0x470/0x470 [16430.619856] netlink_rcv_skb+0x75/0x140 [16430.619858] genl_rcv+0x24/0x40 [16430.619859] netlink_unicast+0x177/0x1f0 [16430.619860] netlink_sendmsg+0x204/0x3d0 [16430.619862] sock_sendmsg+0x5e/0x60 [16430.619864] ___sys_sendmsg+0x304/0x390 [16430.619865] ? ___sys_recvmsg+0x17b/0x200 [16430.619867] __sys_sendmsg+0x81/0xd0 [16430.619870] do_syscall_64+0x4e/0x110 [16430.619872] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [16430.619873] RIP: 0033:0x7f65d369b7ed [16430.619875] Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 4a 53 f8 ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 48 89 44 24 08 e8 7e 53 f8 ff 48 [16430.619875] RSP: 002b:00007fffff63f000 EFLAGS: 00000293 ORIG_RAX: 000000000000002e [16430.619876] RAX: ffffffffffffffda RBX: 00007fffff63f0d0 RCX: 00007f65d369b7ed [16430.619877] RDX: 0000000000000000 RSI: 00007fffff63f040 RDI: 000000000000000b [16430.619877] RBP: 000055f4da0b9d00 R08: 0000000000000000 R09: 0000000000001000 [16430.619878] R10: 0000000000000000 R11: 0000000000000293 R12: 000055f4da0b9d00 [16430.619878] R13: 000055f4d9eda200 R14: 00007f65d3353300 R15: 000055f4da00f990 [16453.197132] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:48:pipe A] flip_done timed out
Created attachment 285965 [details] Arch Linux dmesg 5.3.11
Happening on Manjaro Linux Using Kernel 5.3.11. Didn't seem to happen on any 5.3.x prior to 5.3.11. {{HARDWARE MODEL}} 03:00.0 Network controller [0280]: Intel Corporation Wireless-AC 9260 [8086:2526] (rev 29) {{DMESG}} [ 7179.650362] iwlwifi 0000:03:00.0: Error sending STATISTICS_CMD: time out after 2000ms. [ 7179.650365] iwlwifi 0000:03:00.0: Current CMD queue read_ptr 111 write_ptr 112 [ 7179.901177] iwlwifi 0000:03:00.0: HW error, resetting before reading [ 7179.907668] iwlwifi 0000:03:00.0: Start IWL Error Log Dump: [ 7179.907670] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 1488576775 [ 7179.907671] iwlwifi 0000:03:00.0: Loaded firmware version: 46.6bf1df06.0 [ 7179.907672] iwlwifi 0000:03:00.0: 0x70BA0CE2 | ADVANCED_SYSASSERT [ 7179.907672] iwlwifi 0000:03:00.0: 0x6800537F | trm_hw_status0 [ 7179.907673] iwlwifi 0000:03:00.0: 0xCB3F8981 | trm_hw_status1 [ 7179.907674] iwlwifi 0000:03:00.0: 0xED441C89 | branchlink2 [ 7179.907674] iwlwifi 0000:03:00.0: 0x3ABAFF7F | interruptlink1 [ 7179.907675] iwlwifi 0000:03:00.0: 0x40A7FD7C | interruptlink2 [ 7179.907675] iwlwifi 0000:03:00.0: 0xD5FF6579 | data1 [ 7179.907676] iwlwifi 0000:03:00.0: 0xD1B9F3A7 | data2 [ 7179.907676] iwlwifi 0000:03:00.0: 0xEF44C73D | data3 [ 7179.907677] iwlwifi 0000:03:00.0: 0x937BFE6D | beacon time [ 7179.907677] iwlwifi 0000:03:00.0: 0xF6EAAEF0 | tsf low [ 7179.907678] iwlwifi 0000:03:00.0: 0x59AF909A | tsf hi [ 7179.907678] iwlwifi 0000:03:00.0: 0x7D389917 | time gp1 [ 7179.907679] iwlwifi 0000:03:00.0: 0x5867684E | time gp2 [ 7179.907679] iwlwifi 0000:03:00.0: 0x69C782EF | uCode revision type [ 7179.907680] iwlwifi 0000:03:00.0: 0xC97B0BD3 | uCode version major [ 7179.907681] iwlwifi 0000:03:00.0: 0xDF3D6541 | uCode version minor [ 7179.907681] iwlwifi 0000:03:00.0: 0xE14C52D7 | hw version [ 7179.907682] iwlwifi 0000:03:00.0: 0xCF69FAA7 | board version [ 7179.907682] iwlwifi 0000:03:00.0: 0x3C6BAEF7 | hcmd [ 7179.907683] iwlwifi 0000:03:00.0: 0x150B8A43 | isr0 [ 7179.907683] iwlwifi 0000:03:00.0: 0xE09BCCBC | isr1 [ 7179.907684] iwlwifi 0000:03:00.0: 0x2FFC048D | isr2 [ 7179.907684] iwlwifi 0000:03:00.0: 0x284ADDBB | isr3 [ 7179.907685] iwlwifi 0000:03:00.0: 0x22636040 | isr4 [ 7179.907685] iwlwifi 0000:03:00.0: 0x310C7C27 | last cmd Id [ 7179.907686] iwlwifi 0000:03:00.0: 0x87C7CE12 | wait_event [ 7179.907686] iwlwifi 0000:03:00.0: 0xE65BCCD2 | l2p_control [ 7179.907687] iwlwifi 0000:03:00.0: 0x4BB7FB9A | l2p_duration [ 7179.907688] iwlwifi 0000:03:00.0: 0x7B7FFFEE | l2p_mhvalid [ 7179.907688] iwlwifi 0000:03:00.0: 0x1CB28CED | l2p_addr_match [ 7179.907689] iwlwifi 0000:03:00.0: 0x797F95ED | lmpm_pmg_sel [ 7179.907689] iwlwifi 0000:03:00.0: 0xAAD7D7C1 | timestamp [ 7179.907690] iwlwifi 0000:03:00.0: 0xAFAABCFA | flow_handler [ 7179.907858] iwlwifi 0000:03:00.0: Start IWL Error Log Dump: [ 7179.907859] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 1031346875 [ 7179.907860] iwlwifi 0000:03:00.0: 0xA07A4CA0 | ADVANCED_SYSASSERT [ 7179.907860] iwlwifi 0000:03:00.0: 0xF976BA7B | umac branchlink1 [ 7179.907861] iwlwifi 0000:03:00.0: 0x02C48D2D | umac branchlink2 [ 7179.907861] iwlwifi 0000:03:00.0: 0x4977F71A | umac interruptlink1 [ 7179.907862] iwlwifi 0000:03:00.0: 0x489DCFA9 | umac interruptlink2 [ 7179.907863] iwlwifi 0000:03:00.0: 0xF3F6ABEF | umac data1 [ 7179.907863] iwlwifi 0000:03:00.0: 0x42B50FC8 | umac data2 [ 7179.907864] iwlwifi 0000:03:00.0: 0xFA953B61 | umac data3 [ 7179.907864] iwlwifi 0000:03:00.0: 0x71529684 | umac major [ 7179.907865] iwlwifi 0000:03:00.0: 0xE3F49B73 | umac minor [ 7179.907865] iwlwifi 0000:03:00.0: 0xFE7185D9 | frame pointer [ 7179.907866] iwlwifi 0000:03:00.0: 0xB0B05A32 | stack pointer [ 7179.907866] iwlwifi 0000:03:00.0: 0x75536150 | last host cmd [ 7179.907867] iwlwifi 0000:03:00.0: 0x8771B5F5 | isr status reg [ 7179.908013] iwlwifi 0000:03:00.0: Fseq Registers: [ 7179.908081] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE [ 7179.908215] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION [ 7179.908350] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION [ 7179.908484] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION [ 7179.908618] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_CONTENT_VERSION [ 7179.908752] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ALIVE_TOKEN [ 7179.908887] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVI_ID [ 7179.909021] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVR_ID [ 7179.909155] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVI_AUX_MISC_CHIP [ 7179.909289] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP [ 7179.909423] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 7179.909557] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 7179.909561] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired. [ 7179.909565] ieee80211 phy0: Hardware restart was requested After that a lot of lines like this one: [ 7209.122034] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=215698 end=215699) time 2943 us, min 1073, max 1079, scanline start 1008, end 76
Still happens on Arch with kernel 5.4.2.
(In reply to Henrique Barros from comment #62) > Happening on Manjaro Linux Using Kernel 5.3.11. Didn't seem to happen on any > 5.3.x prior to 5.3.11. > > > > {{HARDWARE MODEL}} > > 03:00.0 Network controller [0280]: Intel Corporation Wireless-AC 9260 > [8086:2526] (rev 29) > > > {{DMESG}} > > [ 7179.650362] iwlwifi 0000:03:00.0: Error sending STATISTICS_CMD: time out > after 2000ms. > [ 7179.650365] iwlwifi 0000:03:00.0: Current CMD queue read_ptr 111 > write_ptr 112 > [ 7179.901177] iwlwifi 0000:03:00.0: HW error, resetting before reading > [ 7179.907668] iwlwifi 0000:03:00.0: Start IWL Error Log Dump: > [ 7179.907670] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 1488576775 > [ 7179.907671] iwlwifi 0000:03:00.0: Loaded firmware version: 46.6bf1df06.0 > [ 7179.907672] iwlwifi 0000:03:00.0: 0x70BA0CE2 | ADVANCED_SYSASSERT > > [ 7179.907672] iwlwifi 0000:03:00.0: 0x6800537F | trm_hw_status0 > [ 7179.907673] iwlwifi 0000:03:00.0: 0xCB3F8981 | trm_hw_status1 > [ 7179.907674] iwlwifi 0000:03:00.0: 0xED441C89 | branchlink2 > [ 7179.907674] iwlwifi 0000:03:00.0: 0x3ABAFF7F | interruptlink1 > [ 7179.907675] iwlwifi 0000:03:00.0: 0x40A7FD7C | interruptlink2 > [ 7179.907675] iwlwifi 0000:03:00.0: 0xD5FF6579 | data1 > [ 7179.907676] iwlwifi 0000:03:00.0: 0xD1B9F3A7 | data2 > [ 7179.907676] iwlwifi 0000:03:00.0: 0xEF44C73D | data3 > [ 7179.907677] iwlwifi 0000:03:00.0: 0x937BFE6D | beacon time > [ 7179.907677] iwlwifi 0000:03:00.0: 0xF6EAAEF0 | tsf low > [ 7179.907678] iwlwifi 0000:03:00.0: 0x59AF909A | tsf hi > [ 7179.907678] iwlwifi 0000:03:00.0: 0x7D389917 | time gp1 > [ 7179.907679] iwlwifi 0000:03:00.0: 0x5867684E | time gp2 > [ 7179.907679] iwlwifi 0000:03:00.0: 0x69C782EF | uCode revision type > [ 7179.907680] iwlwifi 0000:03:00.0: 0xC97B0BD3 | uCode version major > [ 7179.907681] iwlwifi 0000:03:00.0: 0xDF3D6541 | uCode version minor > [ 7179.907681] iwlwifi 0000:03:00.0: 0xE14C52D7 | hw version > [ 7179.907682] iwlwifi 0000:03:00.0: 0xCF69FAA7 | board version > [ 7179.907682] iwlwifi 0000:03:00.0: 0x3C6BAEF7 | hcmd > [ 7179.907683] iwlwifi 0000:03:00.0: 0x150B8A43 | isr0 > [ 7179.907683] iwlwifi 0000:03:00.0: 0xE09BCCBC | isr1 > [ 7179.907684] iwlwifi 0000:03:00.0: 0x2FFC048D | isr2 > [ 7179.907684] iwlwifi 0000:03:00.0: 0x284ADDBB | isr3 > [ 7179.907685] iwlwifi 0000:03:00.0: 0x22636040 | isr4 > [ 7179.907685] iwlwifi 0000:03:00.0: 0x310C7C27 | last cmd Id > [ 7179.907686] iwlwifi 0000:03:00.0: 0x87C7CE12 | wait_event > [ 7179.907686] iwlwifi 0000:03:00.0: 0xE65BCCD2 | l2p_control > [ 7179.907687] iwlwifi 0000:03:00.0: 0x4BB7FB9A | l2p_duration > [ 7179.907688] iwlwifi 0000:03:00.0: 0x7B7FFFEE | l2p_mhvalid > [ 7179.907688] iwlwifi 0000:03:00.0: 0x1CB28CED | l2p_addr_match > [ 7179.907689] iwlwifi 0000:03:00.0: 0x797F95ED | lmpm_pmg_sel > [ 7179.907689] iwlwifi 0000:03:00.0: 0xAAD7D7C1 | timestamp > [ 7179.907690] iwlwifi 0000:03:00.0: 0xAFAABCFA | flow_handler > [ 7179.907858] iwlwifi 0000:03:00.0: Start IWL Error Log Dump: > [ 7179.907859] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 1031346875 > [ 7179.907860] iwlwifi 0000:03:00.0: 0xA07A4CA0 | ADVANCED_SYSASSERT > [ 7179.907860] iwlwifi 0000:03:00.0: 0xF976BA7B | umac branchlink1 > [ 7179.907861] iwlwifi 0000:03:00.0: 0x02C48D2D | umac branchlink2 > [ 7179.907861] iwlwifi 0000:03:00.0: 0x4977F71A | umac interruptlink1 > [ 7179.907862] iwlwifi 0000:03:00.0: 0x489DCFA9 | umac interruptlink2 > [ 7179.907863] iwlwifi 0000:03:00.0: 0xF3F6ABEF | umac data1 > [ 7179.907863] iwlwifi 0000:03:00.0: 0x42B50FC8 | umac data2 > [ 7179.907864] iwlwifi 0000:03:00.0: 0xFA953B61 | umac data3 > [ 7179.907864] iwlwifi 0000:03:00.0: 0x71529684 | umac major > [ 7179.907865] iwlwifi 0000:03:00.0: 0xE3F49B73 | umac minor > [ 7179.907865] iwlwifi 0000:03:00.0: 0xFE7185D9 | frame pointer > [ 7179.907866] iwlwifi 0000:03:00.0: 0xB0B05A32 | stack pointer > [ 7179.907866] iwlwifi 0000:03:00.0: 0x75536150 | last host cmd > [ 7179.907867] iwlwifi 0000:03:00.0: 0x8771B5F5 | isr status reg > [ 7179.908013] iwlwifi 0000:03:00.0: Fseq Registers: > [ 7179.908081] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE > [ 7179.908215] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION > [ 7179.908350] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION > [ 7179.908484] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION > [ 7179.908618] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_CONTENT_VERSION > [ 7179.908752] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ALIVE_TOKEN > [ 7179.908887] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVI_ID > [ 7179.909021] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVR_ID > [ 7179.909155] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVI_AUX_MISC_CHIP > [ 7179.909289] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP > [ 7179.909423] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | > CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM > [ 7179.909557] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | > CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR > [ 7179.909561] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired. > [ 7179.909565] ieee80211 phy0: Hardware restart was requested > > > After that a lot of lines like this one: > > [ 7209.122034] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update > failure on pipe A (start=215698 end=215699) time 2943 us, min 1073, max > 1079, scanline start 1008, end 76 I have the same issue and error messages in dmesg. The system freeze for a few seconds without any response. - I am running Fedora 31 with kernel 5.3.16-300.fc31.x86_64, with firmware version: 46.6bf1df06.0 - the machine is a Laptop Lenovo Y540 with wireless card 'Wireless-AC 9560',
I am still seeing this after fedora 31 kernel upgrade. the kernel 5.4.8-200.fc31.x86_64 is still affected. (In reply to ruijiang li from comment #64) > I have the same issue and error messages in dmesg. The system freeze for a > few seconds without any response. > - I am running Fedora 31 with kernel 5.3.16-300.fc31.x86_64, with firmware > version: 46.6bf1df06.0 > - the machine is a Laptop Lenovo Y540 with wireless card 'Wireless-AC 9560',
Created attachment 286785 [details] dmesg from iwlwifi failure (patched kernel) I've been happily running kernel 5.3.11 with the patch https://bugzilla.kernel.org/attachment.cgi?id=285983&action=diff for a while, but recently I've noticed the wifi having troubles again. Maybe due to updates I made the intel drivers or linux-firmware? I attached a trace and different messages this time.
Looks like 5.5 has finally fixed this.
Created attachment 287045 [details] Fedora 31 Kernel 5.5 (compiled manually) dmesg I still have iwlwifi crashing on kernel 5.5, though the error is different now.
I am on Arch with default kernel 5.5 and firmware 20191220. For me everything is ok now. I will test firmware 20200122. My chip is 9260.
Created attachment 287087 [details] Kernel 5.5.0, AX200 48.4fa0041f.0 I have a similar issue with Intel AX200 WiFi firmware crashing. 5.5.0 kernel and firmware 48.4fa0041f.0
the decision to remove lar_disable functionality means LAR incorrectly detects which regulatory domain is used. without lar_disable the iwlwifi driver detects 2 separate regulatory domains (US and Indonesia). i live in the US, never been to ID nor have any of my devices. because LAR fails to function properly it disables all 5ghz channels except for 4 channels 149-163 IIRC and only at 20mhz making for a terrible link speed. with `lar_disable=Y` the correct regdom is used (US-FCC) and all the appropriate channels are enabled and no Indonesia regdom. this is the same on 9260 dual band 160mhz, 8265 dual band, and 3165. on windows im forced to use 2.4ghz because lar_disable is not an option but on linux i was at least able to fix this with lar_disable. LAR if/when it actually works is a feature, when it fails as it often does, a way to disable it is the only fix for it.
I should have mentioned that I have this device: 03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
I had a Intel 8265 crashing at a customer very often (once in 30minutes). Moved from AC to N and the problem is gone. I was suspecting 80Mhz would be the problem so I asked the customer to set the APs to 40MHz. Tried AC again but the crash was back again soon. Linux Helena 5.5.4-arch1-1 firmware version: 36.952d9faa.0 wpa_supplicant 2.9 CISCO AC 40Mhz, EAP-TLS, 802.11r/k/v, 5GHz only ---- Feb 26 07:51:29 Helena kernel: iwlwifi 0000:05:00.0: Error sending STATISTICS_CMD: time out after 2000ms. Feb 26 07:51:29 Helena kernel: iwlwifi 0000:05:00.0: Current CMD queue read_ptr 8 write_ptr 9 Feb 26 07:51:30 Helena kernel: iwlwifi 0000:05:00.0: HW error, resetting before reading Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: Start IWL Error Log Dump: Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: Status: 0x00000040, count: 1637961839 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: Loaded firmware version: 36.952d9faa.0 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x63BF5193 | ADVANCED_SYSASSERT Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xFD8D09DE | trm_hw_status0 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x9B4DA8F6 | trm_hw_status1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x17707E6A | branchlink2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x4AC85D5B | interruptlink1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x687CA977 | interruptlink2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA6FC5503 | data1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xF26AE79F | data2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA3B91C05 | data3 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xFAAB9F24 | beacon time Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xD7DED1A9 | tsf low Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x9BDE895A | tsf hi Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x3C031839 | time gp1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x37680C77 | time gp2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xC9E29B36 | uCode revision type Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x58F3581B | uCode version major Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x5B5153CE | uCode version minor Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xBB6FEA3A | hw version Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xBBA3EFAD | board version Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x9C20DAA1 | hcmd Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xD84209DA | isr0 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x7ADFFA57 | isr1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xD3BE17DE | isr2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x92E2EFFB | isr3 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xF8077516 | isr4 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x7928005C | last cmd Id Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xECD3F539 | wait_event Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x4474CEF9 | l2p_control Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x667D16A4 | l2p_duration Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x6F7137BA | l2p_mhvalid Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA380310E | l2p_addr_match Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x356303C8 | lmpm_pmg_sel Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x9A39BA67 | timestamp Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x5B8C9D72 | flow_handler Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: Start IWL Error Log Dump: Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: Status: 0x00000040, count: -224527348 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x3BBB75FE | ADVANCED_SYSASSERT Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x27FFFFFC | umac branchlink1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x8E79C13F | umac branchlink2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x6EF717B6 | umac interruptlink1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA8BEF639 | umac interruptlink2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xAED55CBF | umac data1 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xE3FC7DC9 | umac data2 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA7BDA588 | umac data3 Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x0D85A74A | umac major Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x33E7E2D4 | umac minor Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x5F29CDDB | frame pointer Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xD9E0FB75 | stack pointer Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xDF676B57 | last host cmd Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0x3E36C83C | isr status reg Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: Fseq Registers: Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_TOP_CONTENT_VERSION Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_ALIVE_TOKEN Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_CNVI_ID Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | FSEQ_CNVR_ID Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | CNVI_AUX_MISC_CHIP Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR Feb 26 07:51:31 Helena kernel: iwlwifi 0000:05:00.0: Collecting data: trigger 2 fired. Feb 26 07:51:31 Helena kernel: ieee80211 phy0: Hardware restart was requested Feb 26 07:51:32 Helena kernel: perf: interrupt took too long (3453 > 3140), lowering kernel.perf_event_max_sample_rate to 57900 Feb 26 07:51:37 Helena kernel: iwlwifi 0000:05:00.0: Queue 0 is inactive on fifo 2 and stuck for 2500 ms. SW [8, 9] HW [162, 162] FH TRB=0x0a5> Feb 26 07:51:37 Helena kernel: iwlwifi 0000:05:00.0: Queue 4 is inactive on fifo 2 and stuck for 10000 ms. SW [85, 112] HW [162, 162] FH TRB=0> Feb 26 07:51:37 Helena kernel: iwlwifi 0000:05:00.0: Failing on timeout while stopping DMA channel 8 [0xa5a5a5a2] Feb 26 07:51:37 Helena kernel: iwlwifi 0000:05:00.0: Applying debug destination EXTERNAL_DRAM Feb 26 07:51:37 Helena kernel: iwlwifi 0000:05:00.0: Applying debug destination EXTERNAL_DRAM Feb 26 07:51:37 Helena kernel: iwlwifi 0000:05:00.0: FW already configured (0) - re-configuring
I have an Intel 9260 wireless card and I've been running into a similar issue really recently under kernel 5.12.15, I've reverted to kernel 5.12.13, I'll update if it is stable or not. I'll attach the logs I've had, it could be more complicated than this issue, I saw an Ethernet port also mentioning errors in my dmesg.
Created attachment 297887 [details] IWL-Error-Log-Dump-Enp4s0-kernel-5-12-15 IWL Error logs dump along enp4s0 errors/cmd under Kernel 5.12.15.
Since this is really old now, checking if it's still relevant to anyone here? If yes, any chance anyone could capture firmware debug data per https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging The assert should trigger a dump already, but the udev rule/script would be required to capture it.
Created attachment 304017 [details] statistics_cmd err 2023
Comment on attachment 304017 [details] statistics_cmd err 2023 Just want to add that I am still receiving this on Intel NUC11ATKC4 (uses Intel® Wireless-AC 9462). Have ~8 computers running, so will try to enable and capture firmware debug information next week on those computers.
I am experiencing almost the same on my ThinkPad X1 Carbon 3rd gen; 04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 99) I have noticed weird disconnections only recently and now I may have a clue since it has been mentioned before in this report. It may happen since I replaced my old access point with a newer one (a ZTE MC801A), which my laptop connects to, according to wavemon the wifi channel width used is indeed 80Mhz I can easily reproduce the issue by making a lot of traffic like when I use Miracast via Gnome Network Displays, or remote play via Steam Even more easily by just doing a simple speedtest. I have an internet bandwidth of about 150Mbps in Down and 50Mbps in up I'll try to dump the attachments, made 2 dumps after a clean reboot, let me now if they are good or no. Also kernel logs iwlwifi.dmesg.1 iwlwifi.dmesg.2 iwlwifi.dump.1 iwlwifi.dump.2
Created attachment 304266 [details] iwlwifi firmware debug dump 1 After triggering the issue, refers to iwlwifi.dmesg.1
Created attachment 304267 [details] iwlwifi kernel log issue 1 Refers to iwlwifi.dump.1
Created attachment 304268 [details] iwlwifi firmware debug dump 2 refers to iwlwifi.dmesg.2
Created attachment 304269 [details] iwlwifi kernel log issue 2 refers to iwlwifi.dump.2
me too have that problem