Bug 203055 - iwlwifi: 8265: BAD_COMMAND - FW error in SYNC CMD TDLS_CONFIG_CMD - WIFI-21193
Summary: iwlwifi: 8265: BAD_COMMAND - FW error in SYNC CMD TDLS_CONFIG_CMD - WIFI-21193
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: DO NOT USE - assign "network-wireless-intel" component instead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-26 23:00 UTC by jgdavies24
Modified: 2019-06-02 02:13 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.0.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (105.88 KB, text/plain)
2019-03-26 23:00 UTC, jgdavies24
Details
firmware with TDLS disabled (2.30 MB, application/octet-stream)
2019-05-16 14:23 UTC, Emmanuel Grumbach
Details
TDLS Setup Request Packet (383 bytes, application/octet-stream)
2019-06-01 20:27 UTC, Matt Berry
Details
dmesg using attached firmware (106.15 KB, text/plain)
2019-06-01 20:28 UTC, Matt Berry
Details

Description jgdavies24 2019-03-26 23:00:59 UTC
Created attachment 282043 [details]
dmesg

Hardware info:
Lenovo carbon x1 6th gen, Intel AC 8265 wireless running firmware 36.9f0a2d68.0




Currently experiencing issues when my ionic debugging webserver with Android hot reload/logging is started (runs a nodejs webserver listening on a few different ports).



firmware-version: 36.9f0a2d68.0
Comment 1 Emmanuel Grumbach 2019-05-16 14:23:51 UTC
Created attachment 282793 [details]
firmware with TDLS disabled

Hi,

the firmware was advertising support for TDLS when it wasn't really supporting it.

We disabled the advertisement of the feature in the firmware.
Please test.

Thank you.
Comment 2 Emmanuel Grumbach 2019-05-23 06:35:34 UTC
I assume it works.
Comment 3 Matt Berry 2019-06-01 20:24:58 UTC
I have the 8260, on a 4th gen X1, and experienced the same issue. I replaced my firmware with the attached, but am still seeing the same symptoms.

slate% sha256sum /usr/lib/firmware/iwlwifi-8265-36.ucode 
7929ec4a6eb513f6a9780a49587323926458a3ee03c0c466c8725d376164e4e5  /usr/lib/firmware/iwlwifi-8265-36.ucode

04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
	Subsystem: Intel Corporation Wireless 8260
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

[   10.188846] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[   10.201399] iwlwifi 0000:04:00.0: loaded firmware version 36.9f0a2d68.0 op_mode iwlmvm
[   10.343925] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[   10.421309] iwlwifi 0000:04:00.0: base HW address: 34:f3:9a:60:99:24
[   10.536301] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[  107.146571] iwlwifi 0000:04:00.0: Microcode SW error detected.  Restarting 0x82000000.
[  107.146813] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
[  107.146818] iwlwifi 0000:04:00.0: Status: 0x00000100, count: 6
[  107.146822] iwlwifi 0000:04:00.0: Loaded firmware version: 36.9f0a2d68.0

I've attached dmesg and the culprit TDLS setup request frame
Comment 4 Matt Berry 2019-06-01 20:27:20 UTC
Created attachment 283023 [details]
TDLS Setup Request Packet

The was the last packet that was captured by tcpdump before the firmware error / hardware reset
Comment 5 Matt Berry 2019-06-01 20:28:56 UTC
Created attachment 283025 [details]
dmesg using attached firmware

After booting the attached firmware that doesn't advertise TDLS, I still experienced the issue. This is the dmesg output.
Comment 6 Matt Berry 2019-06-02 02:13:26 UTC
Ok, looks like the 8260 uses the iwlwifi-8000C-*.ucode instead of iwlwifi-8265-*.ucode, so that explains why there's no improvement for me.

Note You need to log in before you can comment on or make changes to this bug.