Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
7430 Discussions

Kernel 4.9.140 with WiFi 8265 AC crashes at iwl_mvm_rs_tx_status in softap mode.

YAdle2
Beginner
1,595 Views

I'm using Ubuntu18.04 and running hotspot (softap) with:

sudo nmcli device wifi hotspot ifname wlan0 ssid test password "test1234"

 

admin@localhost:~$ modinfo iwlwifi | grep 8265

firmware:    iwlwifi-8265-26.ucode

 

admin@localhost:~$ ll /lib/firmware/ | grep 8265

-rw-r--r-- 1 root root 2389968 Nov 18 2017 iwlwifi-8265-21.ucode

-rw-r--r-- 1 root root 1811984 Apr 24 2018 iwlwifi-8265-22.ucode

-rw-r--r-- 1 root root 2234528 Dec 6 2017 iwlwifi-8265-27.ucode

-rw-r--r-- 1 root root 2307104 Dec 6 2017 iwlwifi-8265-31.ucode

-rw-r--r-- 1 root root 2440780 Apr 25 2018 iwlwifi-8265-34.ucode

-rw-r--r-- 1 root root 2498044 Jul 12 2019 iwlwifi-8265-36.ucode

 

 

WiFi starts working and looks fine. After few minutes, CPU (Nvidia) reboots and dmesg show:

[  43.306894] ------------[ cut here ]------------

[  43.307064] WARNING: CPU: 1 PID: 4421 at /dvs/git/dirty/git-master_linux/kernel/kernel-4.9/drivers/net/wireless/intel/iwlwifi/mvm/rs.c:1212 iwl_mvm_rs_tx_status+0x2ec/0x9f8 [iwlmvm]

[  43.307310] Modules linked in: fuse ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack zram overlay uvcvideo cdc_acm iwlmvm mac80211 iwlwifi cfg80211 nvgpu bluedroid_pm ip_tables x_tables

 

[  43.307443] CPU: 1 PID: 4421 Comm: irq/819-iwlwifi Not tainted 4.9.140-tegra #1

[  43.307446] Hardware name: Jetson-AGX (DT)

[  43.307450] task: ffffffc3d79d6200 task.stack: ffffffc3b47b8000

[  43.307518] PC is at iwl_mvm_rs_tx_status+0x2ec/0x9f8 [iwlmvm]

[  43.307564] LR is at iwl_mvm_rs_tx_status+0x7c/0x9f8 [iwlmvm]

[  43.307570] pc : [<ffffff8001349b6c>] lr : [<ffffff80013498fc>] pstate: 60c00045

[  43.307573] sp : ffffffc3b47bb990

[  43.307577] x29: ffffffc3b47bb990 x28: ffffffc3aa280818 

[  43.307584] x27: ffffffc3aa280ad8 x26: 0000000000000000 

[  43.307592] x25: 000000000d9afffb x24: 00000000ffffffea 

[  43.307600] x23: 0000000000000000 x22: 0000000000000000 

[  43.307607] x21: 0000000000000000 x20: ffffffc3ada995e8 

[  43.307614] x19: ffffffc39293c228 x18: 000000000000b63c 

[  43.307621] x17: 0000000000000002 x16: 0000000000000003 

[  43.307628] x15: ffffffc3ecfbee28 x14: 000200000017ff05 

[  43.307636] x13: 0002000000000000 x12: ffffff800c000064 

[  43.307642] x11: 000000000000000b x10: 0101010101010101 

[  43.307651] x9 : ffffff800134a140 x8 : 0000000000000001 

[  43.307658] x7 : 000000000000002c x6 : 0000000053a3ded7 

[  43.307665] x5 : 0000000000000033 x4 : 0000000000000000 

[  43.307672] x3 : ffffffc39293c228 x2 : 00000000000000ff 

[  43.307680] x1 : 0000000000000001 x0 : ffffff8001371c22 

 

[  43.307689] ---[ end trace 03aac47687aeda0a ]---

[  43.307775] Call trace:

[  43.307852] [<ffffff8001349b6c>] iwl_mvm_rs_tx_status+0x2ec/0x9f8 [iwlmvm]

[  43.307901] [<ffffff800134a1ec>] iwl_mvm_rs_tx_status+0x96c/0x9f8 [iwlmvm]

[  43.307999] [<ffffff800124e404>] ieee80211_tx_status+0x3ac/0x758 [mac80211]

[  43.308044] [<ffffff800133c080>] iwl_mvm_rx_tx_cmd+0x288/0x678 [iwlmvm]

[  43.308089] [<ffffff8001330bec>] iwl_mvm_rx_chub_update_mcc+0x3ec/0x17c8 [iwlmvm]

[  43.308134] [<ffffff8001330ecc>] iwl_mvm_rx_chub_update_mcc+0x6cc/0x17c8 [iwlmvm]

[  43.308174] [<ffffff80012194d0>] iwl_pci_unregister_driver+0x1288/0x1910 [iwlwifi]

[  43.308199] [<ffffff800121a71c>] iwl_pcie_irq_handler+0x17c/0x788 [iwlwifi]

[  43.308207] [<ffffff80081246d8>] irq_thread_fn+0x30/0x80

[  43.308212] [<ffffff8008124a14>] irq_thread+0x11c/0x1a8

[  43.308218] [<ffffff80080dbee4>] kthread+0xec/0xf0

[  43.308224] [<ffffff8008083850>] ret_from_fork+0x10/0x40

 

 

0 Kudos
1 Reply
AndrewG_Intel
Employee
1,419 Views

Hello YAdle2

 

Thank you for posting on the Intel® communities.

 

Regarding the crashing issues when running UBUNTU® using Intel® Dual Band Wireless-AC 8265 we would like to inform you that we support issues related to the download and installation of software only. For more information please refer to Linux* Support for Intel® Wireless Adapters.

 

Linux drivers are part of the upstream Linux* kernel. They're available through the regular channels, distributions, or the Linux* kernel archives. We recommend you using the driver the Ubuntu distribution provides or the one in the following link:

https://www.intel.com/content/www/us/en/support/articles/000005511/network-and-i-o/wireless-networking.html

 

For general questions about Intel Wi-Fi on Linux, please email linuxwifi@intel.com.

To report a bug or issue, follow the guidance on the bugs and support page.

Additionally, you can check this issue further with the Linux UBUNTU® Forums*:

https://ubuntuforums.org/

 

Regards,

 

Andrew G.

Intel Customer Support Technician

 

*Links to third-party sites and references to third-party trademarks are provided for convenience and illustrative purposes only. Unless explicitly stated, Intel® is not responsible for the contents of such links, and no third party endorsement of Intel® or any of its products is implied.

0 Kudos
Reply