You are not logged in.

#1 2019-09-21 06:37:41

grobber
Member
Registered: 2018-02-09
Posts: 29

5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

I am on an Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz running Linux x86_64 (Slackware), with a custom-compiled 5.3.0-rc4 (.config attached).                                                                                                   
                                                                                                                                                                                                                                             
I am using the Intel wifi adapter on this machine:                                                                                                                                                                                           
                                                                                                                                                                                                                                             
02:00.0 Network controller: Intel Corporation Device 24fb (rev 10)                                                                                                                                                                           
                                                                                                                                                                                                                                             
with the iwlwifi driver, on kernel 5.3.0-arch1-1-ARCH.

I see multiple iwlwifi-related errors in dmesg:

[ 1338.555746] iwlwifi 0000:02:00.0: FW Error notification: type 0x00000000 cmd_id 0x05
[ 1338.555750] iwlwifi 0000:02:00.0: FW Error notification: seq 0x0026 service 0x00000005
[ 1338.555755] iwlwifi 0000:02:00.0: FW Error notification: timestamp 0x0000000038938C83
[ 1338.555806] iwlwifi 0000:02:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT
[ 1338.556221] iwlwifi 0000:02:00.0: Failed to get geographic profile info -5

Furthermore,

$ iw dev wlp2s0 scan

results in a 'scan aborted' error.

I believe the newest 5.3.0 kernel falls foul of this issue noted on LKML:

https://lkml.org/lkml/2019/8/17/7

Edit:

I can also confirm that linux-lts (which I am on as we speak) does not exhibit the problem. I can scan for networks just fine.

Last edited by grobber (2019-09-21 06:53:37)

Offline

#2 2019-09-21 11:32:21

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,415

Re: 5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

As you've already identified a relevant upstream discussion, what's the goal of this thread? Is it just informational or do you want to ask for an update outside of the official stable releases or?

Online

#3 2019-09-21 12:28:06

sobralense
Member
Registered: 2015-08-24
Posts: 9

Re: 5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

Have the same "problem" but just some messages are the same. I can scan and connect like before, but I'm flooded with error messages on login screen.
Using a Lenovo Thinkpad L460.

Kernel:  5.3.0-arch1-1-ARCH #1 SMP PREEMPT Mon Sep 16 03:29:01 UTC 2019 x86_64 GNU/Linux

From lspci:
03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

From dmesg:
[   28.029272] iwlwifi 0000:00:1c.2: 00000200: 2201001e 0028281f 40a0280f
[   28.029807] iwlwifi 0000:03:00.0: iwlwifi root port (0000:00:1c.2) AER cap structure:
[   28.030360] iwlwifi 0000:00:1c.2: 00000000: 14010001 00000000 00010000 00060011 00000000 00002000 00000000 00000000
[   28.030963] iwlwifi 0000:00:1c.2: 00000020: 00000000 00000000 00000000 00000000 00000000 00000000
[   28.031517] iwlwifi 0000:03:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT
[   28.032139]  iwl_trans_pcie_send_hcmd+0x547/0x560 [iwlwifi]
[   28.032149]  iwl_trans_send_cmd+0x59/0xb0 [iwlwifi]
[   28.032186] iwlwifi 0000:03:00.0: Failed to get geographic profile info -5
[   28.032769] WARNING: CPU: 1 PID: 269 at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1874 iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 [iwlmvm]

I'd say you can revert back the kernel to an older version, like wiki suggests. But when doing so, some services like acpi and drivers may show errors. Just keep the LTS version if everything is going fine.
https://wiki.archlinux.org/index.php/Do … the_kernel

Last edited by sobralense (2019-09-21 12:34:38)

Offline

#4 2019-09-21 14:07:43

grobber
Member
Registered: 2018-02-09
Posts: 29

Re: 5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

V1del wrote:

As you've already identified a relevant upstream discussion, what's the goal of this thread? Is it just informational or do you want to ask for an update outside of the official stable releases or?

The thread serves both purposes you mention regardless of my intentions, so I might turn around and ask you what the goal of your reply is.

The discussion is certainly not pointless: the upstream thread I linked identifies some temporary measures (simple patching one might apply to the kernel). If the Arch kernel package maintainers have this information, they might opt to apply those temporary fixes to mitigate the problem until it is solved upstream.

Offline

#5 2019-09-21 15:23:32

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: 5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

If you want to contact a package's maintainers about a bug,  please report it on bug tracker.
Few maintainers use the forums and forum staff will not repost the report for you.
Public service announcements are also not allowed on the forum.
Edit:

Luciano Coelho wrote:

You could have just forced that function return false.

I think that would be the following:

diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c
index 5de54d1559dd..3e676c73a7dc 100644
--- a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c
+++ b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c
@@ -882,18 +882,7 @@ int iwl_mvm_sar_select_profile(struct iwl_mvm *mvm, int prof_a, int prof_b)
 
 static bool iwl_mvm_sar_geo_support(struct iwl_mvm *mvm)
 {
-       /*
-        * The GEO_TX_POWER_LIMIT command is not supported on earlier
-        * firmware versions.  Unfortunately, we don't have a TLV API
-        * flag to rely on, so rely on the major version which is in
-        * the first byte of ucode_ver.  This was implemented
-        * initially on version 38 and then backported to 36, 29 and
-        * 17.
-        */
-       return IWL_UCODE_SERIAL(mvm->fw->ucode_ver) >= 38 ||
-              IWL_UCODE_SERIAL(mvm->fw->ucode_ver) == 36 ||
-              IWL_UCODE_SERIAL(mvm->fw->ucode_ver) == 29 ||
-              IWL_UCODE_SERIAL(mvm->fw->ucode_ver) == 17;
+       return false;
 }
 
 int iwl_mvm_get_sar_geo_profile(struct iwl_mvm *mvm)

This is not though

Luciano Coelho wrote:

Yeah, I meant more or less to return false for your NIC.

Possibly check mvm->cfg->device_family or mvm->cfg->name

Last edited by loqs (2019-09-21 15:56:19)

Offline

#6 2019-09-21 19:51:38

grobber
Member
Registered: 2018-02-09
Posts: 29

Re: 5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

loqs wrote:

If you want to contact a package's maintainers about a bug,  please report it on bug tracker.
Few maintainers use the forums and forum staff will not repost the report for you.
Public service announcements are also not allowed on the forum.

Understood. Thank you, and apologies (to everyone) if this was perceived as being on the spammy side.

Offline

#7 2019-09-25 09:01:51

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,415

Re: 5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

There was no malicious/reprimanding intent behind my question,  I wanted to ask for the reasons loqs noted, I could've expanded on the question in the first post sorry about that.

Online

#8 2019-09-25 14:51:30

CarbonChauvinist
Member
Registered: 2012-06-16
Posts: 412
Website

Re: 5.3.0+iwlwifi fails with Intel Corporation Device 24fb (wifi)

According to the bugzilla report for this issue, there has been a patch submitted by Luca Coelho to address. He goes on to say:

I have just sent a fix for this upstream:

https://patchwork.kernel.org/patch/11158395/

It will hopefully be taken to v5.4 soon and from there to stable v5.3, v5.2 and v4.19.

It seems the original issue was, in his words:

There seems to be an issue with the new FW where it doesn't flag support for the new command version, but uses it anyway.  The crash is caused by the driver sending a command in the wrong (i.e. old) format.

I'll fix this and send a patch/new FW version in a bit.

For even further clarity here's the commit message from the above patch:

The intention was to have the GEO_TX_POWER_LIMIT command in FW version
36 as well, but not all 8000 family got this feature enabled.  The
8000 family is the only one using version 36, so skip this version
entirely.  If we try to send this command to the firmwares that do not
support it, we get a BAD_COMMAND response from the firmware.

and further comments in the patch itself which are also useful:

 	 * firmware versions.  Unfortunately, we don't have a TLV API
 	 * flag to rely on, so rely on the major version which is in
 	 * the first byte of ucode_ver.  This was implemented
-	 * initially on version 38 and then backported to 36, 29 and
-	 * 17.
+	 * initially on version 38 and then backported to29 and 17.
+	 * The intention was to have it in 36 as well, but not all
+	 * 8000 family got this feature enabled.  The 8000 family is
+	 * the only one using version 36, so skip this version
+	 * entirely.
 	 */

Last edited by CarbonChauvinist (2019-09-25 14:56:02)


"the wind-blown way, wanna win? don't play"

Offline

Board footer

Powered by FluxBB