Bug 2035849

Summary:	[RHEL9] iwlwifi: backport patches to prevent firmware resets
Product:	Red Hat Enterprise Linux 9	Reporter:	Neal Gompa <ngompa13>
Component:	kernel	Assignee:	Íñigo Huguet <ihuguet>
kernel sub component:	Wifi	QA Contact:	Ken Benoit <kbenoit>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	acaringi, adscvr, airlied, alciregi, andersonkw2, bskeggs, bstinson, carl, danili, davide, extras-qa, hdegoede, hkrzesin, ihuguet, jarod, jarodwilson, jeremy, jglisse, jonathan, josef, jwboyer, kbenoit, kernel-maint, lgoncalv, linville, markus.falb, masami256, mchehab, michel, ngompa13, ptalbert, steved
Version:	CentOS Stream	Keywords:	TestOnly, Triaged
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kernel-5.14.0-69.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2035833	Environment:
Last Closed:	2022-05-17 15:43:54 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2043454
Bug Blocks:

Description Neal Gompa 2021-12-28 02:57:12 UTC

+++ This bug was initially created as a clone of Bug #2035833 +++

I would like to request two patches to be backported to the current kernel. 

There was a iwlwifi issue that would cause firmware resets and cause
performance to significantly degrade to around ~500Kb/s till the
interface was brought down and then up again. Upstream identified the
issue and there are 2 patches that fix the issue by increasing the
scan timeout[1] and in cases where the firmware resets allows it to
recover quicker[2]. The patch to allow for quicker firmware recovery
is present in Linus' tree and present in the 5.16 rc releases while
the patch to prevent the firmware from crashing in the instance is in
net-next for 5.17.

I believe this impacts any Intel WiFi 6 cards, but it particularly
affects the AX210 on the Framework laptop.

[1] - https://bugzilla.kernel.org/show_bug.cgi?id=214549
[2] - https://bugzilla.kernel.org/show_bug.cgi?id=214693

The two patches can be found upstream and they are attached to the upstream bugs.

Comment 1 Íñigo Huguet 2022-01-24 07:47:38 UTC

Hi, thanks for reporting.

I will ensure to include the patches in the next planned wireless updated, tracking BZ 2043454. Also in the RHEL8 wireless update, tracking BZ 2043453.

Comment 3 Íñigo Huguet 2022-02-08 14:19:15 UTC

Shifting DTM to 24 to match the wireless update's DTM

Comment 7 Íñigo Huguet 2022-03-01 09:25:55 UTC

Wireless update to v5.16 and later fixes has been merged. It includes the patches reported to fix this BZ. Setting state to ON_QA.

@kbenoit reproduction steps from https://bugzilla.kernel.org/show_bug.cgi?id=214693#c0:
1. Start iperf to generate network load.
2. Perform `nmcli device wifi rescan`.
3. Expect: no device restart. Actual: device restarts (see logs) and network speeds become abysmally slow or non-responsive until disconnecting and reconnecting to WiFi network.

Note that this was very likely to only happen if the driver and the card has the 6GHz band enabled, but not required to be connected to 6GHz channel.

@ngompa13 may you want and be able to test it as well? This is RHEL9 bug, I've also asked the same for RHEL8 bug.

Comment 8 Neal Gompa 2022-03-01 13:41:51 UTC

I don't have a Framework Laptop on hand to test with at the moment, but maybe @carl could? I believe he has one.

Comment 10 Ken Benoit 2022-03-02 16:42:18 UTC

Ran testing against RHEL-9.0.0-20220301.3 on an Intel AX211 using the steps from comment 7. Only saw a momentary dip in speed (a drop of ~100 Mbps for only 1 second) if the rescan was performed and then the speed went right back to normal. Marking as verified.

Comment 12 Carl George 🤠 2022-05-11 04:31:59 UTC

I do have a framework laptop but I'm currently using it and cannot install a different operating system for testing at this time.

Comment 14 errata-xmlrpc 2022-05-17 15:43:54 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: kernel), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3907