RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2043454 - [RHEL9 wireless] stack & drivers general update to v5.16+
Summary: [RHEL9 wireless] stack & drivers general update to v5.16+
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kernel
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Íñigo Huguet
QA Contact: Ken Benoit
URL:
Whiteboard:
Depends On:
Blocks: 2025325 2035849
TreeView+ depends on / blocked
 
Reported: 2022-01-21 09:41 UTC by Íñigo Huguet
Modified: 2022-05-17 15:59 UTC (History)
7 users (show)

Fixed In Version: kernel-5.14.0-69.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:44:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/src/kernel centos-stream-9 merge_requests 493 0 None None None 2022-02-11 10:20:41 UTC
Red Hat Issue Tracker RHELPLAN-109073 0 None None None 2022-01-21 09:43:18 UTC
Red Hat Product Errata RHBA-2022:3907 0 None None None 2022-05-17 15:45:23 UTC

Description Íñigo Huguet 2022-01-21 09:41:55 UTC 
General update of wireless stack & drivers for RHEL9.0 to upstream version 5.16 and later fixes
Comment 1 Íñigo Huguet 2022-01-25 10:02:44 UTC 
Note for ourselves: ensure to check that this commit, which is part of this update, doesn't break ath11k hardware (i.e. WCN6855 or QCA6390)
72f412434772 Revert "ath11k: add read variant from SMBIOS for download board data"
Comment 3 Íñigo Huguet 2022-02-15 15:16:22 UTC 
@kbenoit kind reminder to verify this when you can to see if we can avoid exception request. Thanks!
Comment 4 Ken Benoit 2022-02-15 15:49:20 UTC 
(In reply to Íñigo Huguet from comment #3)
> @kbenoit kind reminder to verify this when you can to see if we
> can avoid exception request. Thanks!

Sorry I missed this. I thought I had already tested this but apparently I didn't. Ran testing against RHEL-9.0.0-20220210.0 with kernel-5.14.0-57.mr493_220209_0952.el9 manually against an Intel AX201 and an Intel AX211. Testing passed without issue. Marking as Verified:Tested,SanityOnly and pushing the ITM ahead so the kernel has a chance to land in the nightlies.
Comment 7 Íñigo Huguet 2022-02-22 13:00:44 UTC 
@kbenoit: Jiri has asked this during his review, could you help asking?
  This is an update of a large number of drivers just before the freeze. What testing was done? In bugzilla, it's indicated that only two Intel wifi cards were tested. I don't think that's enough for such massive update. Could you please clarify this?
Comment 8 Ken Benoit 2022-02-22 13:14:30 UTC 
(In reply to Íñigo Huguet from comment #7)
> @kbenoit: Jiri has asked this during his review, could you help
> asking?
>   This is an update of a large number of drivers just before the freeze.
> What testing was done? In bugzilla, it's indicated that only two Intel wifi
> cards were tested. I don't think that's enough for such massive update.
> Could you please clarify this?

Given the limited timeframe as we're closing in on the deadline, I can only run testing on a selection of recent cards for the rebase. We have weekly regression testing runs against the most recent nightly. I will also run through a different selection of cards each week through the release with a recent nightly. This is the most I am capable of while staying within the schedule of the release though, especially given late requests for enablement.
Comment 9 Jiri Benc 2022-02-22 14:08:20 UTC 
(In reply to Ken Benoit from comment #8)
> This is the most I am capable of while staying within the
> schedule of the release though, especially given late requests for
> enablement.

Isn't it an indication that this should rather be postponed to RHEL 9.1?
Comment 12 Ken Benoit 2022-02-22 16:53:18 UTC 
Ran testing against RHEL-9.0.0-20220215.4 with kernel-5.14.0-65.mr493_220221_1051.el9. Testing passed without issue against an Intel 9560, Intel AX201, QCA6390, Intel 7265, Intel AX210, Intel AX211, MT7921, and Intel 8260. Leaving Verified:Tested and SanityOnly intact.
Comment 17 Ken Benoit 2022-03-02 19:52:23 UTC 
Performed manual wireless regression testing against RHEL-9.0.0-20220301.3 against a variety of wireless cards. Testing passed without issue. This being a rebase means that I was only able to do some patch verification on top of general testing. Verifying as SanityOnly.
Comment 19 errata-xmlrpc 2022-05-17 15:44:52 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
Note You need to log in before you can comment on or make changes to this bug.