Bug 1790231

Summary:	AX200 in Lenovo P1 Gen 2 fails and prevents shutdown; appears to load incorrect firmware
Product:	[Fedora] Fedora	Reporter:	daniel.a.jenson
Component:	iwlwifi-firmware	Assignee:	Lubomir Rintel <lkundrak>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	31	CC:	bgalvani, blueowl, christian.ohrfandl, daniel.a.jenson, dcaratti, dcbw, extras-orphan, john.j5live, lkundrak, matthias
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-09 15:11:30 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:

Description daniel.a.jenson 2020-01-12 20:45:30 UTC

Description of problem: Fedora 31 fresh install with Lenovo P1 Gen 2 and AX 200 wireless/bluetooth card fails to connect to the internet. After reboot, internet dies and am unable to change any settings.


Version-Release number of selected component (if applicable): wpa_supplicant v2.9


How reproducible: Every boot (and install).


Steps to Reproduce:
1. Install Fedora 31 netinstall.
2. Update all packages.
3. Reboot.

Actual results:
Internet unavailable until wpa_supplicant is stopped and disabled.


Expected results: Internet available.


Additional info:

Comment 1 daniel.a.jenson 2020-01-14 15:56:55 UTC

This now seems more related to the driver, as it continues to fail sporadically.

Comment 2 daniel.a.jenson 2020-01-15 04:58:05 UTC

Another observation as I try to get this too work: it appears the kernel tries to load version 50, then 49, then 48 of the Intel iwlwifi firmware (which it loads then then fails), but on Intel's website, version 46 is the latest supported for the AX200 and 48 for the AX201, so maybe it's just loading the wrong firmware?

Comment 3 daniel.a.jenson 2020-01-18 00:55:59 UTC

Still an issue in 5.4.10

Comment 4 daniel.a.jenson 2020-01-18 19:39:26 UTC

Looks like this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1738361, which was previously closed.

Comment 5 daniel.a.jenson 2020-01-18 19:43:39 UTC

Log:

Jan 18 11:35:06 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 18 11:35:06 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 18 11:35:06 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 18 11:35:06 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 18 11:35:06 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 18 11:35:06 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 18 11:35:06 m2 NetworkManager[1408]: <info>  [1579376106.1987] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.6/0000:52:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Jan 18 11:35:05 m2 kernel: iwlwifi 0000:52:00.0 wlp82s0: renamed from wlan0
Jan 18 11:35:05 m2 kernel: iwlwifi 0000:52:00.0: base HW address: dc:71:96:d9:e5:95
Jan 18 11:35:05 m2 kernel: iwlwifi 0000:52:00.0: Allocated 0x00400000 bytes for firmware monitor.
Jan 18 11:35:05 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 18 11:35:05 m2 kernel: iwlwifi 0000:52:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
Jan 18 11:35:04 m2 kernel: iwlwifi 0000:52:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
Jan 18 11:35:04 m2 kernel: iwlwifi 0000:52:00.0: Found debug configuration: 0
Jan 18 11:35:04 m2 kernel: iwlwifi 0000:52:00.0: Found debug destination: EXTERNAL_DRAM
Jan 18 11:35:04 m2 kernel: iwlwifi 0000:52:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
Jan 18 11:35:04 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
Jan 18 11:35:04 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
Jan 18 11:35:04 m2 kernel: iwlwifi 0000:52:00.0: enabling device (0000 -> 0002)
Jan 18 11:21:58 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 18 11:21:58 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 18 11:21:58 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 18 11:21:54 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 18 11:21:54 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 18 11:21:54 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 18 11:21:54 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 18 11:21:54 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 18 11:21:54 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 18 11:21:54 m2 NetworkManager[1399]: <info>  [1579375314.2360] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.6/0000:52:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Jan 18 11:21:53 m2 kernel: iwlwifi 0000:52:00.0 wlp82s0: renamed from wlan0
Jan 18 11:21:53 m2 kernel: iwlwifi 0000:52:00.0: base HW address: dc:71:96:d9:e5:95
Jan 18 11:21:53 m2 kernel: iwlwifi 0000:52:00.0: Allocated 0x00400000 bytes for firmware monitor.
Jan 18 11:21:53 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 18 11:21:53 m2 kernel: iwlwifi 0000:52:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
Jan 18 11:21:52 m2 kernel: iwlwifi 0000:52:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
Jan 18 11:21:52 m2 kernel: iwlwifi 0000:52:00.0: Found debug configuration: 0
Jan 18 11:21:52 m2 kernel: iwlwifi 0000:52:00.0: Found debug destination: EXTERNAL_DRAM
Jan 18 11:21:52 m2 kernel: iwlwifi 0000:52:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
Jan 18 11:21:52 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
Jan 18 11:21:52 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
Jan 18 11:21:52 m2 kernel: iwlwifi 0000:52:00.0: enabling device (0000 -> 0002)

Comment 6 daniel.a.jenson 2020-01-20 21:42:10 UTC

Is there anyone who can instruct me on how to patch this? I have a brand new Lenovo P1 Gen 2 and I have to disable the wifi card on startup every time before it fails; I'm currently running off a tiny USB wifi card (that used to belong to my raspberry pi).

Comment 7 daniel.a.jenson 2020-01-22 03:31:50 UTC

Still a problem in 5.4.12

Comment 8 daniel.a.jenson 2020-01-27 16:05:54 UTC

Still a problem in 5.4.13

Jan 27 08:03:09 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 27 08:03:09 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 27 08:03:09 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:05 m2 NetworkManager[1457]: <info>  [1580140985.4611] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.6/0000:52:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0 wlp82s0: renamed from wlan0
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: base HW address: dc:71:96:d9:e5:95
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Allocated 0x00400000 bytes for firmware monitor.
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Found debug configuration: 0
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Found debug destination: EXTERNAL_DRAM
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: enabling device (0000 -> 0002)

Comment 9 daniel.a.jenson 2020-01-27 16:06:08 UTC

Still a problem in 5.4.13

Jan 27 08:03:09 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 27 08:03:09 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 27 08:03:09 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: BIOS contains WGDS but no WRDS
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: FW already configured (0) - re-configuring
Jan 27 08:03:05 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:05 m2 NetworkManager[1457]: <info>  [1580140985.4611] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.6/0000:52:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0 wlp82s0: renamed from wlan0
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: base HW address: dc:71:96:d9:e5:95
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Allocated 0x00400000 bytes for firmware monitor.
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Applying debug destination EXTERNAL_DRAM
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Found debug configuration: 0
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Found debug destination: EXTERNAL_DRAM
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
Jan 27 08:03:04 m2 kernel: iwlwifi 0000:52:00.0: enabling device (0000 -> 0002)

Comment 10 daniel.a.jenson 2020-01-31 18:17:30 UTC

Still a problem in 5.4.14

Comment 11 daniel.a.jenson 2020-02-01 01:48:01 UTC

Even with a completely fresh install this morning, it returns after a cold boot. [kernel 5.4.14]

Comment 12 daniel.a.jenson 2020-02-02 20:59:56 UTC

Still an issue in 5.4.15.

Comment 13 daniel.a.jenson 2020-02-04 16:53:54 UTC

Something in the most recent kernel is causing it to be even flakier than before. Even turning off the wired connection at boot, which previously at least allowed me to use my external USB wifi card, NetworkManager, etc now freezes within minutes of boot.

Can someone at least respond -- a link, anything? This is a brand-new top of the line lenovo, and I can't use it for more than a couple hours at best before needing to do a hard reboot because iwlwifi crashes, and cascades into wpa_supplicant and NetworkManager.

Comment 14 daniel.a.jenson 2020-02-19 02:29:20 UTC

Still an issue in 5.4.19.

Comment 15 christian.ohrfandl 2020-04-15 00:57:31 UTC

This still seems to be a problem in kernel 5.6.2 (tested on Fedora 32; 5.6.2-301.fc32.ppc64le).

Could someone investigate and reopen this bug report please? For additional info see my latest comment and uploaded log in this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1738361.

I am willingly going to provide any analysis that is necessary to fix this issue! Thank you in advance!