Community
cancel
Showing results for 
Search instead for 
Did you mean: 
gastondelar
Beginner
27 Views

Wi Fi 6 AX201 randomly crashing, then can't be loaded by any OS

Hello everyone, I'd like to report a problem I've been consistently having with my Intel Wi-Fi 6 Ax201 which came in my MSI GF 65 Thin 10SDR laptop.

It is a dual boot system with Windows 10 and Arch linux. (Windows Fast Start Up and Hibernation are turned OFF)

The behavior goes something like this. Linux starts normally, I use iwd to connect to wifi and everything seems ok. Then seemingly randomly (this has happened while the laptop was connected but idle in terms of user input) the driver crashes and briefly after , system load goes very high and system becomes unusable. Every following boot after this happens both OSs fail to load the card (it's listed by lspci but not as an interface in ip). For a brief period of time I thought power cycling the laptop brought it back working but that could've been a coincidence as this is no longer the case.  Then equally randomly the card will load successfully again in both OSs. Most of the times after at least a few hours of the laptop being powered off. I haven't observed the crash happening from Windows since I rarely use the OS and when I do it is for a brief period of time. When the OS can load the card it works flawlessly in terms of connection stability and speed.

The device uses iwlwifi driver, version fo the kernel is 5.12.9-arch1-1. Firmware in use is iwlwifi-Quz-a0-hr-b0-62, though i've tried versions 59, 55, 53, 50 and 48 of the firmware without any noticeable changes. Tried loading iwlwifi at runtime which results in the same error message from the boot attempt to load the card. I get -110 ucode errors, I'll attach the whole trace below with the dmesg output.  I've tried all the following options as kernel parameters with no success

iwlwifi.11n_disable=1 
iwlwifi.swcrypto=0
iwlwifi.bt_coex_active=0
iwlwifi.power_save=0 iwlmvm.power_scheme=1 iwlwifi.uapsd_disable=1
iommu=soft

 

The file BOOT_DMESG_FAILED_STATE.txt is an example dmesg of a failed boot after a crash happened. I've noticed that in this failure state, after the detection fo the Wi Fi 6 card, there's always a failed to read out thermal zone like in 1.930277 in this example. Then the trace starts at 2.935155. The wlan1 thing at the end is when I plugged a usb wifi adapter.

 

The file JOURNALCTL_OK_STATE_THEN_CRASH.txt is the output of journalctl --system containing a session where it booted ok but then the driver crashed and the whole system with it. You can look for the crash specifically by the time, it was at 00:48:32, at that m oment I wasn't doing anything at all with the system. There are some messages about how iwd couldn't be killed that called my attention at around 01:21 as well. In this file there are readings from sensord from minutes before the crash happen which are pretty normal I think but from the crash on the temp sensor is unreadable.

At the moment of writing this I've added mac80211.probe_wait_ms=5000 as a kernel parameter at a suggestion of an other Arch user mainly because of these messages from the journal I've attached

Jun 07 00:48:32 chachopenaloza kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.

Jun 07 00:48:32 chachopenaloza kernel: ieee80211 phy0: Hardware restart was requested

Jun 07 00:48:34 chachopenaloza kernel: iwlwifi 0000:00:14.3: Firmware error during reconfiguration - reprobe!
Jun 07 00:48:34 chachopenaloza kernel: iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
Jun 07 00:48:34 chachopenaloza kernel: iwlwifi 0000:00:14.3: Failed to start RT ucode: -110

It's back working from the last boot I did about an hour ago so I haven't been able to observe if the crash happens or not with that new parameter. I'll report back when something happens.

 

From the Windows side I've tried version 21.60.0.5 of the driver downloaded from MSI's page for my laptop which reports that the device cannot be started with an error code 10, and version  22.50.1 downloaded from Intel's website which reports an error code 43. I've also tried whatever driver Windows installs automatically when told to do so. I've tried the network reset option in settings and also deleting the device with and without deleting the driver before installing some other one or letting windows do it by scanning for hardware changes. I don't know if other system output could be of help here as I don't know this OS at all.

I really like the laptop,  and spent a ton of time setting it up so i'd like to keep it, but I'm kind of on a timer now to fix it before the warranty expires. Please let me know if there is further information I can  provide and thanks in advance for your help.

Labels (1)
0 Kudos
1 Reply
AndrewG_Intel
Moderator
8 Views

Hello @gastondelar

Thank you for posting on the Intel® communities. Please review the following steps and kindly provide details of the outcome.

 

For Windows:

Regarding the Code 10 error on Windows® 10, we recommend following the steps and recommendations in this guide:

Code 10 Error in Device Manager for Bluetooth or Wireless (Wi-Fi) Devices

 

One of the processes recommended in the guide is to perform a Clean Installation of the Wireless and Bluetooth drivers. For this, we recommend test using your computer manufacturer (OEM) drivers from MSI*: (Intel BlueTooth Driver 21.60.0.4 and Intel Wireless LAN Driver 21.60.0.5). Here is the download link from MSI*: https://www.msi.com/Laptop/support/GF65-Thin-10SX-GTX?sub_product=GF65-Thin-10SDR#down-driver

 

If you still get the error after re-installing these, then try the Intel Generic drivers for Bluetooth or Wireless adapters:

 

For error code 43, you may try the following:

  1. Open Internet Explorer, select Tools  > Internet options.
  2. Go to the Connections tab
  3. Click LAN Settings
  4. uncheck Automatically detect settings
  5. You may also test by uninstalling your Antivirus Software. (Check with your Antivirus Software vendor or computer manufacturer (OEM) before trying this and for proper assistance.

 

For Linux:

Please refer to the following link for the latest firmware for Linux Wireless and make sure the proper firmware is installed based on your wireless model.

 

If the behavior persists please provide the following details:

1- When did it start to happen? Did it work fine before? Were you able to have your wireless connection in a normal/expected performance before? Please provide details.

2- In Linux operating system, please type the following command to the terminal: # lspci​ and provide us with the outcome.

 

3- In Windows® please run the Intel® System Support Utility (Intel® SSU) to gather more details about the system.

  • Download the Intel® SSU and save the application on your computer
  • Open the application, check the "Everything" checkbox, and click "Scan" to see the system and device information. The Intel® SSU defaults to the "Summary View" on the output screen following the scan. Click the menu where it says "Summary" to change to "Detailed View".
  • To save your scan, click Next and click Save.
  • Once you have saved the file (.txt file), please attach it to your reply.
  • To upload and attach a file, use the "Drag and drop here or browse files to attach" option below the response textbox.

 

Best regards,

Andrew G.

Intel Customer Support Technician

 

Reply