Created attachment 278373 [details] dmesg output There are small freezes in several Ubuntu distributions (16.04.5 LTS, 18.04) with error [35714.735364] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. General information: ~ lspci | grep Network 00:14.3 Network controller: Intel Corporation Device a370 (rev 10) ~ ethtool -i wlp0s20f3 | grep firmware firmware-version: 34.0.0 Linux laptop2 4.15.0-33-generic #36~16.04.1-Ubuntu SMP Wed Aug 15 17:21:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ~ sudo dmidecode -s bios-version 1.3.0 ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial Following the instructions described in https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging, I include encrypted output of dmesg.
Created attachment 278375 [details] lshw output
If you can upgrade your kernel, please do so and use a more recent firmware. If you can't upgrade your kernel, please use our backport tree to get the latest version of the driver (just take the master branch of the backport driver). Both firmware and driver are available here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release
Thank you for your response. I tried to upgrade the kernel, but I found that after 4.16, libssl1.1 is required, so I get "linux-headers-x.xx.xx.xxxx-generic depends on libssl1.1 (>= 1.1.0); however: Package libssl1.1 is not installed.". As far as I know, it is not straightforward to install it on Ubuntu 16.04. So the next option was to install the latest version of the driver. There were some SSL errors after "make install". However, I think it installed correctly, because now I get: ~ ethtool -i wlp0s20f3 | grep firmware firmware-version: 38.c0e03d94.0 In any case, the errors are still occurring. I attach dmesg.log and output after "make install".
Created attachment 278479 [details] dmesg after firmware upgrade dmesg after firmware upgrade
Created attachment 278481 [details] make install output Includes SSL errors
Do you still see assert 942? Sorry, my system with the key is shut down right now.
Yes, I still see 0x00000942 | ADVANCED_SYSASSERT. The only difference I see between the old and new dmesg output is that after the crash, the line "0x00000070 | ADVANCED_SYSASSERT" is not showing anymore in firmware 38.c0e03d94.0. I hope that helps. Let me know if you need more information.
Ok, thanks. We'll need to involve the firmware team.
Sure. Thanks for your help.
Can you please collect a firmware dump when the error occurs? Please check here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging Thanks.
This bug is related to PHY and antennas. Can you please tell us what platform do you have? Laptop? If so, what is the model. Can you try to move the screen of the laptop? Thanks.
This is a laptop. The model is Dell G7 15 7588 (https://www.dell.com/en-us/work/shop/dell-laptops-and-notebooks/dell-g7-15-gaming-laptop/spd/g-series-15-7588-laptop). I moved the screen to different angles but the crashes are still occurring. I'm also including a couple of firmware dumps after crashes. I did it manually, so let me now if I should also try to do it automatically with SUBSYSTEM=="devcoredump", ACTION=="add", RUN+="/sbin/iwlfwdump.sh".
Created attachment 278517 [details] firmware dump 1
Created attachment 278519 [details] firmware dump 2
Thanks. I'll take a look on Sunday.
Great. Thanks!
An update to this issue: Since you mentioned that this bug was related to PHY and antennas and thought about changing the mode used by the router. It was set by default to 802.11b/g/n, so I changed it to 802.11g and now there is no more crashes, although there are a few messages with iwlwifi 0000:00:14.3: Unhandled alg: 0x71b. I include dmesg output and a screenshot of the wireless configuration page in case this is relevant.
Created attachment 278547 [details] dmesg with mode 802.11g
Created attachment 278549 [details] screenshot of wireless configuration page
Created attachment 278551 [details] dmesg with mode 802.11g
I have sent the data to the firmware team. That's pretty much all I can do for now. I'll update when I get news from them.
Have you tried -41.ucode?
No, I haven't. Is that a new version with potential fix? By the way, I recently changed the mode to 802.11b/g/n but with Channel Width = 20MHz (instead of Auto 20/40MHz) and that also fixes the crashes. Let me know if I should try -41.ucode.
I just pushed -43.ucode, so it'd be even better to test that one (with our backport driver)
So how does it feel with -43.ucode? Please take it from our Linux firmware repository, mainline also has -43.ucode but it has a bug. I sent a pull request but they haven't pulled yet.
Hi again, Sorry. I haven't been able to test the update during the holidays. I will give it a try right now.
Uhm... what is the correct repository? I can see this one https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git with a commit relevant to this issue, but I'm not sure if it contains the latest fix. In any case, should I install in the same way as suggested here (https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release) - "How to install the driver" ? Thanks!
Yes to both
Thanks! I changed the WLAN settings back to Auto 20/40 MHz (which was triggering this issue initially) and it is working really well. I didn't notice any freezes and no errors were shown in /var/log/syslog during heavy traffic. I will keep testing and report back if anything changes, but as I said, it looks really good. Regards
please send the output of iw wlp2s0 link
Sure. Is this the correct command? ➜ ~ iw wlp0s20f3 link Connected to xx:xx:xx:xx:xx:xx (on wlp0s20f3) SSID: WirelessNet freq: 2437 RX: 11121023 bytes (2907715 packets) TX: 54319409 bytes (501439 packets) signal: -37 dBm tx bitrate: 300.0 MBit/s MCS 15 40MHz short GI bss flags: short-slot-time dtim period: 1 beacon int: 98
Yes, you are using 40MHz, I wanted to check that the AP is not using 20 MHz despite being in auto mode. So it seems the situation is indeed better.
I am closing this bug. Please reopen if needed. Thank you.
Awesome. Thank you!