Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
AceLan Kao | ||
Focal |
Fix Released
|
Undecided
|
AceLan Kao |
Bug Description
[Impact]
It dumps some debug messages while loading iwlwifi firmware every time after booted up and finally got below errors
[ 5.632845] iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
[ 5.632849] iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
[ 5.645491] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
[Fix]
It looks like it fails to load the firmware since mainline v5.4 kernel, and got fixed at v5.6-rc1. After bisect the kernel, the first bad commit is
b3bd6416fc77 iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg
To avoid conflicts, we have to backport the following commits from mainline kernel
b81b7bd02eda iwlwifi: remove some outdated iwl22000 configurations
c042f0c77f3d iwlwifi: allocate more receive buffers for HE devices
5661925a9b38 iwlwifi: pcie: rx: use rxq queue_size instead of constant
bfc3e9fdbfb8 iwlwifi: 22000: fix some indentation
3681021fc6af iwlwifi: remove IWL_DEVICE_
[Test]
Verified on Dell XPS 9300 with Killer AX1650i wifi card and XPS 13 2-1 platform, wifi keeps working after reboot 10 times.
[Regression Potential]
Medium, the code changes a lot, although the test results are all positive, it's still hard to evaluate the regression potential.
CVE References
tags: | added: oem-priority originate-from-1865829 ouagadougou |
Changed in linux (Ubuntu Focal): | |
status: | New → In Progress |
assignee: | nobody → AceLan Kao (acelankao) |
description: | updated |
Changed in hwe-next: | |
status: | New → Fix Released |
tags: |
added: verification-done-focal removed: verification-needed-focal |
There are some public bug reports on bugzilla, but none of them look similar to ours.
https:/ /bugzilla. kernel. org/show_ bug.cgi? id=205749
It claims the fix lands on v5.4.16 and v5.5, and this patch already has been included in our focal kernel. It doesn't work for us.
https:/ /bugzilla. kernel. org/show_ bug.cgi? id=206329
This one is still open, and doesn't get fixed at v5.6-rc3, so not the same as ours.
https:/ /bugzilla. kernel. org/show_ bug.cgi? id=206719
The error message pretty similar to ours and fails at v5.4.22, but no one follow up
https:/ /bugzilla. kernel. org/show_ bug.cgi? id=206661
Another regression after v5.6-rc1, no fix until v5.6-rc4, affects our linux-5.6 oem kernel.
https:/ /bugzilla. kernel. org/show_ bug.cgi? id=206607
Similar errors, no follow up
https:/ /bugzilla. kernel. org/show_ bug.cgi? id=206395
Similar errors, but doesn't verify it with latest v5.6 mainline kernel.
This is our test results
5.3.0 - Good
5.3.18 - Good
5.4-rc1 - NG
5.4-rc4 - NG
5.4-rc8 - NG
5.4.0 - NG
5.4.16 - NG
5.4.24 - NG
5.5.0 - NG
5.5.8 - NG
5.6-rc1 - Good