Failed to wake NIC for hcmd on the Intel Wireless 7260 miniPCI card

Hi there,
I see the following error message in my syslog.

[49394.098626] iwlwifi 0000:06:00.0: Failed to wake NIC for hcmd
[49394.104461] iwlwifi 0000:06:00.0: Error sending BEACON_TEMPLATE_CMD: enqueue_hcmd failed: -5
[49394.112964] iwlwifi 0000:06:00.0: Failed updating beacon data
[49394.137569] iwlwifi 0000:06:00.0: Failed to wake NIC for hcmd
[49394.143386] iwlwifi 0000:06:00.0: Error sending MAC_CONTEXT_CMD: enqueue_hcmd failed: -5
[49394.151536] iwlwifi 0000:06:00.0: Failed to send MAC context (action:2): -5
[49394.158525] iwlwifi 0000:06:00.0: failed to update MAC 7c:5c:f8:d3:24:9e
[49400.183737] iwlwifi 0000:06:00.0: Failed to wake NIC for hcmd
[49400.189664] iwlwifi 0000:06:00.0: Error sending BEACON_TEMPLATE_CMD: enqueue_hcmd failed: -5
[49400.198178] iwlwifi 0000:06:00.0: Failed updating beacon data
[49400.223241] iwlwifi 0000:06:00.0: Failed to wake NIC for hcmd
[49400.229095] iwlwifi 0000:06:00.0: Error sending MAC_CONTEXT_CMD: enqueue_hcmd failed: -5
[49400.237242] iwlwifi 0000:06:00.0: Failed to send MAC context (action:2): -5
[49400.244238] iwlwifi 0000:06:00.0: failed to update MAC 7c:5c:f8:d3:24:9e
[49406.269563] iwlwifi 0000:06:00.0: Failed to wake NIC for hcmd
[49406.275418] iwlwifi 0000:06:00.0: Error sending BEACON_TEMPLATE_CMD: enqueue_hcmd failed: -5
[49406.283907] iwlwifi 0000:06:00.0: Failed updating beacon data
[49406.308379] iwlwifi 0000:06:00.0: Failed to wake NIC for hcmd
[49406.314187] iwlwifi 0000:06:00.0: Error sending MAC_CONTEXT_CMD: enqueue_hcmd failed: -5
[49406.322372] iwlwifi 0000:06:00.0: Failed to send MAC context (action:2): -5
[49406.329413] iwlwifi 0000:06:00.0: failed to update MAC 7c:5c:f8:d3:24:9e

Do you have a tip what I can do?
Greetings from Stefan Harbich

Only when I deactivate the minipci card does the error message no longer appear. What can I do? I have already switched to the OpenWRT version 21.02.1. Same error message.
The wifi miniPCI Card is:

root@rome01:~# lspci -kvnn | sed -n '/Network/,/^$/ p'
lspci: Unable to load libkmod resources: error -12
06:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070]
	Flags: fast devsel, IRQ 32
	Memory at f7d00000 (64-bit, non-prefetchable) [virtual] [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 7c-5c-f8-ff-ff-d3-24-9e
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>
	Kernel driver in use: iwlwifi

The Kernel-Version is:

root@rome01:~# uname -a
Linux rome01.intern.example.com 5.4.154 #0 SMP Sun Oct 24 09:01:35 2021 x86_64 GNU/Linux

The way I see it, there is a bug in the kernel version?

Report it...

Hi there,
I reported a bug some time ago. Even provided the solution. However, this has not yet been adopted in Git. See also:
OpenWRT Bug
Why should I now create another bug that is not processed?

AP mode is not supported on most Intel cards with the iwlwifi driver. This is a known limitation.

What source did you get the information from?

do an iw list, is AP listed in Supported interface modes ?

root@rome01:~# lspci | grep Network
04:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter
06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
root@rome01:~# iw phy0 info | grep AP
	Device supports AP-side u-APSD.
		 * AP
		 * AP/VLAN
		 * #{ AP, mesh point } <= 8, #{ managed } <= 1,
		   total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
	Maximum associated stations in AP mode: 128
root@rome01:~# iw phy1 info | grep AP
	Device supports AP-side u-APSD.
		 * AP
		 * AP/VLAN
		 * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,

Both wireless adapters support AP mode.
Only when I deactivated the Intel adapter are the error messages no longer displayed.
I think the firmware is faulty?

And if you look further (iw phy phy0 info), you'll notice that all 5 GHz channels will be marked NO-IR, which prevents AP mode on these (all 5 GHz-) channels. Yes, some of the more modern Intel wireless cards can do basic AP mode (as a side effect of Intel pushing WiFi-Direct/ p2p), but only in the 2.4 GHz band - which makes them rather pointless for OpenWrt uses.

root@rome01:~# iw phy phy0 info
Wiphy phy0
	wiphy index: 0
	max # scan SSIDs: 20
	max scan IEs length: 425 bytes
	max # sched scan SSIDs: 20
	max # match sets: 11
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * P2P-client
		 * P2P-GO
		 * P2P-device
	Band 1:
		Capabilities: 0x11ee
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT Max RX data rate: 300 Mbps
		HT TX/RX MCS rate indexes supported: 0-15
		Frequencies:
			* 2412 MHz [1] (22.0 dBm)
			* 2417 MHz [2] (22.0 dBm)
			* 2422 MHz [3] (22.0 dBm)
			* 2427 MHz [4] (22.0 dBm)
			* 2432 MHz [5] (22.0 dBm)
			* 2437 MHz [6] (22.0 dBm)
			* 2442 MHz [7] (22.0 dBm)
			* 2447 MHz [8] (22.0 dBm)
			* 2452 MHz [9] (22.0 dBm)
			* 2457 MHz [10] (22.0 dBm)
			* 2462 MHz [11] (22.0 dBm)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
	Band 2:
		Capabilities: 0x11ee
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT Max RX data rate: 300 Mbps
		HT TX/RX MCS rate indexes supported: 0-15
		VHT Capabilities (0x038071a0):
			Max MPDU length: 3895
			Supported Channel Width: neither 160 nor 80+80
			short GI (80 MHz)
			TX STBC
			SU Beamformee
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		Frequencies:
			* 5180 MHz [36] (22.0 dBm) (no IR)
			* 5200 MHz [40] (22.0 dBm) (no IR)
			* 5220 MHz [44] (22.0 dBm) (no IR)
			* 5240 MHz [48] (22.0 dBm) (no IR)
			* 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
			* 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
			* 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
			* 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
			* 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
			* 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
			* 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
			* 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
			* 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
			* 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
			* 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
			* 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
			* 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
			* 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
			* 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
			* 5720 MHz [144] (22.0 dBm) (no IR, radar detection)
			* 5745 MHz [149] (22.0 dBm) (no IR)
			* 5765 MHz [153] (22.0 dBm) (no IR)
			* 5785 MHz [157] (22.0 dBm) (no IR)
			* 5805 MHz [161] (22.0 dBm) (no IR)
			* 5825 MHz [165] (22.0 dBm) (no IR)
	valid interface combinations:
		 * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
		   total <= 3, #channels <= 2
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	max # scan plans: 2
	max scan plan interval: 65535
	max scan plan iterations: 254
	Supported extended features:
		* [ VHT_IBSS ]: VHT-IBSS
		* [ RRM ]: RRM
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
		* [ EXT_KEY_ID ]: Extended Key ID support
		* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
		* [ DEL_IBSS_STA ]: deletion of IBSS station support
		* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
		* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

That means I can't use this WLAN card in AP mode?

Correct, respectively only in the 2.4 GHz band (where it's least useful - and even there, these chipsets aren't validated in AP mode, you will find bugs in AP mode).

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.