Bug 2043454
| Summary: | [RHEL9 wireless] stack & drivers general update to v5.16+ | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Íñigo Huguet <ihuguet> |
| Component: | kernel | Assignee: | Íñigo Huguet <ihuguet> |
| kernel sub component: | Wifi | QA Contact: | Ken Benoit <kbenoit> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | ajb, jarod, jbenc, kbenoit, ngompa13, phil, toracat |
| Version: | 9.0 | Keywords: | 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: | Environment: | ||
| Last Closed: | 2022-05-17 15:44:52 UTC | Type: | Bug |
| 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: | |||
| Bug Blocks: | 2025325, 2035849 | ||
|
Description
Íñigo Huguet
2022-01-21 09:41:55 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" @kbenoit kind reminder to verify this when you can to see if we can avoid exception request. Thanks! (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. @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? (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. (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? 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. 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. 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 |