Bug 205513

Thanks, this message is because the ACPI tables in the BIOS are not correct.  It is meaningless to have WGDS without WRDS.

The original idea was to print it out as an error because:

- The message text gives important information for BIOS developers;
- It's not a driver-developer-only message, it informs about a system-wide bug;
- The error causes the SAR (specific-absorption-rate) functionality not to be enabled.  So the device won't be SAR-compliant as it is claims to be.

You did the right thing, contacting Dell about the issue.  There is a bug in the ACPI tables, so they can contact us if they need more help.

I tend to agree that this should be reduced to a warning instead of an error, not because it's not an important error, but because of the apparently large amount of platforms with this issue.  I'll discuss this internally.

If you want to help dig into the root cause of the error, you can dump the ACPI table of your computer to a file with acpidump and attach it here.  You may want to encrypt the file, as described in our wiki[1], to avoid potential privacy concerns.

[1] https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#privacy_aspects

Hmmm, I understand your arguments, but I'm afraid things don't work out that way:

* I think manufacturers don't test their BIOSes with linux,
and even if they do, they won't check the logs closely
as soon as everything seems to work.

For my current dell notebook, this is the only BIOS-related error I get,
but the three dell notebooks I had before all produced several BIOS-related
errors on booting which would have been easy to avoid if someone had ever
tested with linux and checked the logs...

* Most people won't even notice. I boot in text mode, with no boot logo,
so errors show up on the console and are visible (and annoying) at login.
But 99 % of the distributions boot in graphics mode with a nice boot logo.
If I had only used the pre-installed ubuntu instead of my home-grown gentoo, 
most likely I wouldn't have noticed the message at all.

* Even if someone at dell noticed the message (or gets error reports 
from users), I'm not sure he will be able to route it
to the correct internal channels (ACPI tables) based on the message text
(and "correct channels" most likely means a third-party company 
delivering the generic code in the bios?).
My contact at dell definitely did not make that connection.

So the message does not serve the purpose you intended it for...

I will upload my acpi tables for you to check.

I'm not sure if it helps when I contact dell again in the current situation.
Perhaps things get going if I contact them after you have more detailled information what's actually wrong with their bios and what needs to be done.

But as we both noticed, several users are getting that message, not only on dell notebooks. Perhaps the bios builders (OEM bios builders) need better guidelines or training on how to provide correct bioses for your chip?

Created attachment 285997 [details]
acpi tables dump

I understand your arguments too. :)

We have reference platforms and documentation on how the ACPI tables should be written.  I don't know what is the cause of this wave of broken BIOSes, but I'll try to figure it out.

Regarding testing on Windows, I'll also check what the Windows driver is doing when it encounters a BIOS with this problem.

Thanks for the dump.  I'll take a look at it.

Can you tell me what's in the firmware node path of your device, so I can find the right section in the ACPI table?

cat /sys/class/ieee80211/phy0/device/firmware_node/path

(In reply to Luca Coelho from comment #5)
> Can you tell me what's in the firmware node path of your device, so I can
> find the right section in the ACPI table?
> 
> cat /sys/class/ieee80211/phy0/device/firmware_node/path

\_SB_.PCI0.RP07.PXSX

Hmmm... The ACPI tables actually look fine.  There must be a bug in the driver then.

Can you unload and reload the iwlwifi module with debug=0x80?

modprobe -r iwlwifi
modprobe iwlwifi debug=0x80

And post the logs here?

(In reply to Luca Coelho from comment #7)
> Can you unload and reload the iwlwifi module with debug=0x80?
> 
> modprobe -r iwlwifi
> modprobe iwlwifi debug=0x80
> 
> And post the logs here?

No, I can't.
This is a statically linked kernel, no modules here.
The module loader is not even configured into the kernel.

If you tell me how to do the same with kernel command line parameters,
I can try tomorrow. Is it iwlwifi.debug=0x80 ?

(off for today, 22:30 local time).

Yes, iwlwifi.debug=0x80 as a kernel command line parameter should work.

Thanks a lot for all the help so far!

(I'm off for today too, 23:30 local time) ;)

(In reply to Luca Coelho from comment #9)
> Yes, iwlwifi.debug=0x80 as a kernel command line parameter should work.

I'm not sure if the debug flag really works:
I don't get any additional dmesg output up to the 
"BIOS contains WGDS but no WRDS" message.
(I tried both 0x80 and 0xff for debug)

This is a dmesg grepped for iwlwifi:

 
[    0.183015] Kernel command line: root=/dev/nvme1n1p1 ro net.ifnames=0 quiet init=/lib/systemd/systemd mitigations=off iwlwifi.debug=0xff 
[    1.716452] iwlwifi 0000:6f:00.0: enabling device (0000 -> 0002)
[    1.724831] iwlwifi 0000:6f:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[    1.724834] iwlwifi 0000:6f:00.0: Found debug destination: EXTERNAL_DRAM
[    1.724835] iwlwifi 0000:6f:00.0: Found debug configuration: 0
[    1.724981] iwlwifi 0000:6f:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[    1.725002] iwlwifi 0000:6f:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    1.738207] iwlwifi 0000:6f:00.0: Applying debug destination EXTERNAL_DRAM
[    1.738378] iwlwifi 0000:6f:00.0: Allocated 0x00400000 bytes for firmware monitor.
[    1.914016] iwlwifi 0000:6f:00.0: base HW address: d0:ab:d5:e5:5a:6a
[    4.063929] iwlwifi 0000:6f:00.0: Applying debug destination EXTERNAL_DRAM
[    4.238279] iwlwifi 0000:6f:00.0: FW already configured (0) - re-configuring
[    4.250689] iwlwifi 0000:6f:00.0: BIOS contains WGDS but no WRDS
[    4.980877] iwlwifi 0000:6f:00.0: RF_KILL bit toggled to disable radio.
[    4.980878] iwlwifi 0000:6f:00.0: reporting RF_KILL (radio disabled)
[   81.352951] iwlwifi 0000:6f:00.0: RF_KILL bit toggled to enable radio.
[   81.352952] iwlwifi 0000:6f:00.0: reporting RF_KILL (radio enabled)
[   81.366575] iwlwifi 0000:6f:00.0: Applying debug destination EXTERNAL_DRAM
[   81.542272] iwlwifi 0000:6f:00.0: FW already configured (0) - re-configuring
[   81.554803] iwlwifi 0000:6f:00.0: BIOS contains WGDS but no WRDS
[   84.546257] iwlwifi 0000:6f:00.0: Unhandled alg: 0x707
[   84.985290] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
[   84.985497] iwlwifi 0000:6f:00.0: Start IWL Error Log Dump:
[   84.985502] iwlwifi 0000:6f:00.0: Status: 0x00000080, count: 6
[   84.985506] iwlwifi 0000:6f:00.0: Loaded firmware version: 48.4fa0041f.0
[   84.985510] iwlwifi 0000:6f:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
[   84.985514] iwlwifi 0000:6f:00.0: 0x000022F0 | trm_hw_status0
[   84.985517] iwlwifi 0000:6f:00.0: 0x00000000 | trm_hw_status1
[   84.985520] iwlwifi 0000:6f:00.0: 0x004F8E3C | branchlink2
[   84.985523] iwlwifi 0000:6f:00.0: 0x004E4FF4 | interruptlink1
[   84.985526] iwlwifi 0000:6f:00.0: 0x004E4FF4 | interruptlink2
[   84.985529] iwlwifi 0000:6f:00.0: 0x000067F4 | data1
[   84.985532] iwlwifi 0000:6f:00.0: 0x00001000 | data2
[   84.985535] iwlwifi 0000:6f:00.0: 0xF0000008 | data3
[   84.985538] iwlwifi 0000:6f:00.0: 0x01415B41 | beacon time
[   84.985542] iwlwifi 0000:6f:00.0: 0x84128B24 | tsf low
[   84.985545] iwlwifi 0000:6f:00.0: 0x000001E5 | tsf hi
[   84.985548] iwlwifi 0000:6f:00.0: 0x00000000 | time gp1
[   84.985551] iwlwifi 0000:6f:00.0: 0x003733E7 | time gp2
[   84.985554] iwlwifi 0000:6f:00.0: 0x00000001 | uCode revision type
[   84.985557] iwlwifi 0000:6f:00.0: 0x00000030 | uCode version major
[   84.985560] iwlwifi 0000:6f:00.0: 0x4FA0041F | uCode version minor
[   84.985563] iwlwifi 0000:6f:00.0: 0x00000340 | hw version
[   84.985566] iwlwifi 0000:6f:00.0: 0x00489000 | board version
[   84.985569] iwlwifi 0000:6f:00.0: 0x80D2FD0D | hcmd
[   84.985572] iwlwifi 0000:6f:00.0: 0x00020000 | isr0
[   84.985575] iwlwifi 0000:6f:00.0: 0x00000000 | isr1
[   84.985578] iwlwifi 0000:6f:00.0: 0x08F0000A | isr2
[   84.985581] iwlwifi 0000:6f:00.0: 0x00C1FFCC | isr3
[   84.985584] iwlwifi 0000:6f:00.0: 0x00000000 | isr4
[   84.985587] iwlwifi 0000:6f:00.0: 0x060B001C | last cmd Id
[   84.985590] iwlwifi 0000:6f:00.0: 0x000067F4 | wait_event
[   84.985593] iwlwifi 0000:6f:00.0: 0x00004208 | l2p_control
[   84.985596] iwlwifi 0000:6f:00.0: 0x00000020 | l2p_duration
[   84.985599] iwlwifi 0000:6f:00.0: 0x0000033F | l2p_mhvalid
[   84.985602] iwlwifi 0000:6f:00.0: 0x000000A0 | l2p_addr_match
[   84.985605] iwlwifi 0000:6f:00.0: 0x00000009 | lmpm_pmg_sel
[   84.985608] iwlwifi 0000:6f:00.0: 0x00000000 | timestamp
[   84.985611] iwlwifi 0000:6f:00.0: 0x0000C018 | flow_handler
[   84.985835] iwlwifi 0000:6f:00.0: Start IWL Error Log Dump:
[   84.985838] iwlwifi 0000:6f:00.0: Status: 0x00000080, count: 7
[   84.985842] iwlwifi 0000:6f:00.0: 0x20101208 | ADVANCED_SYSASSERT
[   84.985846] iwlwifi 0000:6f:00.0: 0x00000000 | umac branchlink1
[   84.985849] iwlwifi 0000:6f:00.0: 0xC008CC3C | umac branchlink2
[   84.985852] iwlwifi 0000:6f:00.0: 0xC0087808 | umac interruptlink1
[   84.985855] iwlwifi 0000:6f:00.0: 0x00000000 | umac interruptlink2
[   84.985858] iwlwifi 0000:6f:00.0: 0x00000001 | umac data1
[   84.985861] iwlwifi 0000:6f:00.0: 0x000003FF | umac data2
[   84.985864] iwlwifi 0000:6f:00.0: 0xDEADBEEF | umac data3
[   84.985867] iwlwifi 0000:6f:00.0: 0x00000030 | umac major
[   84.985870] iwlwifi 0000:6f:00.0: 0x4FA0041F | umac minor
[   84.985873] iwlwifi 0000:6f:00.0: 0x003733D8 | frame pointer
[   84.985876] iwlwifi 0000:6f:00.0: 0xC0887588 | stack pointer
[   84.985880] iwlwifi 0000:6f:00.0: 0x00550502 | last host cmd
[   84.985883] iwlwifi 0000:6f:00.0: 0x00000000 | isr status reg
[   84.986036] iwlwifi 0000:6f:00.0: Fseq Registers:
[   84.986089] iwlwifi 0000:6f:00.0: 0x20000000 | FSEQ_ERROR_CODE
[   84.986143] iwlwifi 0000:6f:00.0: 0x80290001 | FSEQ_TOP_INIT_VERSION
[   84.986197] iwlwifi 0000:6f:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[   84.986250] iwlwifi 0000:6f:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[   84.986304] iwlwifi 0000:6f:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[   84.986357] iwlwifi 0000:6f:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[   84.986411] iwlwifi 0000:6f:00.0: 0x00100530 | FSEQ_CNVI_ID
[   84.986465] iwlwifi 0000:6f:00.0: 0x00000532 | FSEQ_CNVR_ID
[   84.986518] iwlwifi 0000:6f:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[   84.986574] iwlwifi 0000:6f:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[   84.986630] iwlwifi 0000:6f:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   84.986685] iwlwifi 0000:6f:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   84.986934] iwlwifi 0000:6f:00.0: Collecting data: trigger 2 fired.
[   85.718603] iwlwifi 0000:6f:00.0: Applying debug destination EXTERNAL_DRAM
[   85.894955] iwlwifi 0000:6f:00.0: FW already configured (0) - re-configuring
[   85.909414] iwlwifi 0000:6f:00.0: BIOS contains WGDS but no WRDS

I noticed several things:

1. "BIOS contains WGDS but no WRDS" does *not* appear when iwlwifi 
  is initialized for the first time (around system uptime 1.7)

2. "BIOS contains WGDS but no WRDS" is logged whenever iwfwifi changes state,
  three times in the log above, especially whenever I toggle rfkill.

3. There are always three messages logged together:
  Applying debug destination EXTERNAL_DRAM
  FW already configured (0) - re-configuring
  BIOS contains WGDS but no WRDS

I've also run into this with a new Thinkpad T490.  I get exactly the same symptoms (wifi works fine, three messages logged together EXTERNAL_DRAM, FW already configured and BIOS contains WGDS but no WRDS).  Please let me know if there's any additional information I can provide that might help...

I see this as well, on an LG Gram 17 (Intel(R) Dual Band Wireless AC 9560, REV=0x318), 4.19.82-gentoo-x86_64.

Comment#7 indicates this is a bug in the driver, so maybe the title should be changed?

I also have this error on a brand new Dell Precision 7540 with Ubuntu installed from Dell. Just adding to show it seems to be pretty consistent error showing.


[    7.875259] iwlwifi 0000:6f:00.0: BIOS contains WGDS but no WRDS

Can run test if needed as well.

I ran into this bug as well trying to upgrade from kernel 5.3 to 5.4 on a dell precision 7540.  Same message as Peter Nguyen on startup, then the boot fails.

I also get this message on an Intel NUC NUC7i5BNK running Arch Linux with 5.4.19-1-lts and 5.5.3-arch1-1. The system boots and WiFi works fine.

[    4.545464] iwlwifi 0000:3a:00.0: enabling device (0000 -> 0002)
[    4.553118] iwlwifi 0000:3a:00.0: Found debug destination: EXTERNAL_DRAM
[    4.553121] iwlwifi 0000:3a:00.0: Found debug configuration: 0
[    4.553659] iwlwifi 0000:3a:00.0: loaded firmware version 36.952d9faa.0 op_mode iwlmvm
[    4.793992] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[    4.802019] iwlwifi 0000:3a:00.0: Applying debug destination EXTERNAL_DRAM
[    4.802331] iwlwifi 0000:3a:00.0: Allocated 0x00400000 bytes for firmware monitor.
[    4.858897] iwlwifi 0000:3a:00.0: base HW address: f8:63:3f:4b:fd:b6
[    4.944177] iwlwifi 0000:3a:00.0 wlp58s0: renamed from wlan0
[    6.134636] iwlwifi 0000:3a:00.0: Applying debug destination EXTERNAL_DRAM
[    6.276305] iwlwifi 0000:3a:00.0: Applying debug destination EXTERNAL_DRAM
[    6.343676] iwlwifi 0000:3a:00.0: FW already configured (0) - re-configuring
[    6.362043] iwlwifi 0000:3a:00.0: BIOS contains WGDS but no WRDS
[    6.398893] iwlwifi 0000:3a:00.0: Applying debug destination EXTERNAL_DRAM
[    6.534238] iwlwifi 0000:3a:00.0: Applying debug destination EXTERNAL_DRAM
[    6.600875] iwlwifi 0000:3a:00.0: FW already configured (0) - re-configuring
[    6.613854] iwlwifi 0000:3a:00.0: BIOS contains WGDS but no WRDS

Just adding there are a number of Fedora users seeing the same thing:
https://bugzilla.redhat.com/show_bug.cgi?id=1720324

Tagging comment #15 private per submitter's request.

Seen on Dell XPS 8930, running Ubuntu 18.04.4, kernel 5.3.0-40-generic, wifi card Intel Wireless-AC 9260:

$ dmesg | grep iwlwifi
[    3.985080] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[    3.990632] iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM
[    3.990633] iwlwifi 0000:03:00.0: Found debug configuration: 0
[    3.990820] iwlwifi 0000:03:00.0: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm
[    4.011714] iwlwifi 0000:03:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324
[    4.019006] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[    4.019492] iwlwifi 0000:03:00.0: Allocated 0x00400000 bytes for firmware monitor.
[    4.059011] iwlwifi 0000:03:00.0: base HW address: 80:32:53:a3:f4:d5
[    4.549381] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[    5.098757] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[    5.214168] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[    5.284819] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[    5.310879] iwlwifi 0000:03:00.0: BIOS contains WGDS but no WRDS

$ lspci | grep 03:00.0
03:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)

I changed the original wifi card (Kille Wireless-AC 1535), because I was under the impression it could be an issue with the card itself (was seeing the same error message), but obviously that's not the case.

(Continuation from comment 19) - wifi works, but it's very unreliable. It hang a lot (non necessarily under network load) and the following traces are produced:

[ 1535.011213] iwlwifi 0000:03:00.0: Error sending STATISTICS_CMD: time out after 2000ms.
[ 1535.011217] iwlwifi 0000:03:00.0: Current CMD queue read_ptr 199 write_ptr 200
[ 1535.259691] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 1535.259692] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 6
[ 1535.259693] iwlwifi 0000:03:00.0: Loaded firmware version: 46.6bf1df06.0
[ 1535.259694] iwlwifi 0000:03:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[ 1535.259694] iwlwifi 0000:03:00.0: 0x000022F0 | trm_hw_status0
[ 1535.259695] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 1535.259696] iwlwifi 0000:03:00.0: 0x0048853E | branchlink2
[ 1535.259696] iwlwifi 0000:03:00.0: 0x00479392 | interruptlink1
[ 1535.259697] iwlwifi 0000:03:00.0: 0x00479392 | interruptlink2
[ 1535.259697] iwlwifi 0000:03:00.0: 0x0001ACA2 | data1
[ 1535.259698] iwlwifi 0000:03:00.0: 0xFF000000 | data2
[ 1535.259699] iwlwifi 0000:03:00.0: 0x50000008 | data3
[ 1535.259699] iwlwifi 0000:03:00.0: 0x8E403CCE | beacon time
[ 1535.259700] iwlwifi 0000:03:00.0: 0x93BF1302 | tsf low
[ 1535.259700] iwlwifi 0000:03:00.0: 0x000000B1 | tsf hi
[ 1535.259701] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 1535.259702] iwlwifi 0000:03:00.0: 0x5B2E426B | time gp2
[ 1535.259702] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 1535.259703] iwlwifi 0000:03:00.0: 0x0000002E | uCode version major
[ 1535.259703] iwlwifi 0000:03:00.0: 0x6BF1DF06 | uCode version minor
[ 1535.259704] iwlwifi 0000:03:00.0: 0x00000000 | hw version
[ 1535.259705] iwlwifi 0000:03:00.0: 0x00000000 | board version
[ 1535.259705] iwlwifi 0000:03:00.0: 0x00000000 | hcmd
[ 1535.259706] iwlwifi 0000:03:00.0: 0x00000000 | isr0
[ 1535.259706] iwlwifi 0000:03:00.0: 0x00000000 | isr1
[ 1535.259707] iwlwifi 0000:03:00.0: 0x00000000 | isr2
[ 1535.259707] iwlwifi 0000:03:00.0: 0x00000000 | isr3
[ 1535.259708] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[ 1535.259709] iwlwifi 0000:03:00.0: 0x00000000 | last cmd Id
[ 1535.259709] iwlwifi 0000:03:00.0: 0x00000000 | wait_event
[ 1535.259710] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[ 1535.259710] iwlwifi 0000:03:00.0: 0x00000000 | l2p_duration
[ 1535.259711] iwlwifi 0000:03:00.0: 0x00000000 | l2p_mhvalid
[ 1535.259711] iwlwifi 0000:03:00.0: 0x00000000 | l2p_addr_match
[ 1535.259712] iwlwifi 0000:03:00.0: 0x00000000 | lmpm_pmg_sel
[ 1535.259713] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 1535.259713] iwlwifi 0000:03:00.0: 0x00000000 | flow_handler
[ 1535.259758] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 1535.259759] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 7
[ 1535.259759] iwlwifi 0000:03:00.0: 0x20000066 | NMI_INTERRUPT_HOST
[ 1535.259760] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 1535.259761] iwlwifi 0000:03:00.0: 0xC008888E | umac branchlink2
[ 1535.259761] iwlwifi 0000:03:00.0: 0xC0084414 | umac interruptlink1
[ 1535.259762] iwlwifi 0000:03:00.0: 0xC0084414 | umac interruptlink2
[ 1535.259762] iwlwifi 0000:03:00.0: 0x01000000 | umac data1
[ 1535.259763] iwlwifi 0000:03:00.0: 0xC0084414 | umac data2
[ 1535.259763] iwlwifi 0000:03:00.0: 0xDEADBEEF | umac data3
[ 1535.259764] iwlwifi 0000:03:00.0: 0x0000002E | umac major
[ 1535.259765] iwlwifi 0000:03:00.0: 0x6BF1DF06 | umac minor
[ 1535.259765] iwlwifi 0000:03:00.0: 0x5B2E4257 | frame pointer
[ 1535.259766] iwlwifi 0000:03:00.0: 0xC088627C | stack pointer
[ 1535.259766] iwlwifi 0000:03:00.0: 0x00C60502 | last host cmd
[ 1535.259767] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[ 1535.259772] iwlwifi 0000:03:00.0: Fseq Registers:
[ 1535.259842] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE
[ 1535.259976] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION
[ 1535.260111] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION
[ 1535.260246] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION
[ 1535.260380] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_CONTENT_VERSION
[ 1535.260515] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ALIVE_TOKEN
[ 1535.260650] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVI_ID
[ 1535.260784] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVR_ID
[ 1535.260919] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVI_AUX_MISC_CHIP
[ 1535.261054] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
[ 1535.261188] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 1535.261323] iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 1535.261497] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[ 1535.261498] ieee80211 phy0: Hardware restart was requested
[ 1537.612126] iwlwifi 0000:03:00.0: Queue 0 is inactive on fifo 2 and stuck for 2500 ms. SW [199, 200] HW [162, 162] FH TRB=0x0a5a5a5a2
[ 1565.938771] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [kworker/0:1:4241]
[ 1565.938946] Modules linked in: rfcomm uhid algif_hash algif_skcipher af_alg ccm aufs overlay cmac bnep nls_iso8859_1 intel_rapl_msr nvidia_uvm(OE) 8250_dw mei_hdcp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel snd_hda_codec_realtek aes_x86_64 crypto_simd snd_hda_codec_generic nvidia_drm(POE) snd_hda_codec_hdmi cryptd ledtrig_audio nvidia_modeset(POE) glue_helper nvidia(POE) intel_cstate iwlmvm mac80211 intel_rapl_perf libarc4 dell_wmi dell_smbios dcdbas snd_hda_intel idma64 iwlwifi dell_wmi_descriptor snd_hda_codec sparse_keymap wmi_bmof virt_dma intel_wmi_thunderbolt mxm_wmi snd_hda_core snd_hwdep intel_lpss_pci intel_lpss i915 snd_pcm cfg80211 snd_seq_midi snd_seq_midi_event snd_rawmidi drm_kms_helper btusb btrtl snd_seq btbcm drm btintel bluetooth ipmi_devintf snd_seq_device ipmi_msghandler snd_timer i2c_algo_bit snd ucsi_ccg fb_sys_fops mei_me typec_ucsi syscopyarea joydev
[ 1565.938966]  ecdh_generic sysfillrect input_leds typec ecc soundcore sysimgblt mei ie31200_edac acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid ahci alx libahci mdio i2c_nvidia_gpu wmi video
[ 1565.938973] CPU: 0 PID: 4241 Comm: kworker/0:1 Tainted: P           OE     5.3.0-40-generic #32~18.04.1-Ubuntu
[ 1565.938974] Hardware name: Dell Inc. XPS 8930/0T2HR0, BIOS 1.1.10 10/31/2019
[ 1565.938983] Workqueue: events iwl_fw_error_dump_wk [iwlwifi]
[ 1565.938985] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 1565.938986] Code: 3d 00 e9 7c ff ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 c6 07 00 0f 1f 40 00 48 89 f7 57 9d <0f> 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 1565.938987] RSP: 0018:ffff9c3281f77cc8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
[ 1565.938988] RAX: ffffffffc0961ad0 RBX: ffff90ae32fd0018 RCX: 0000000000000003
[ 1565.938988] RDX: 000000000c000005 RSI: 0000000000000246 RDI: 0000000000000246
[ 1565.938988] RBP: ffff9c3281f77cc8 R08: 0000000000003a98 R09: 0000000000000000
[ 1565.938989] R10: 0000000000000000 R11: 0000000000000008 R12: 00000000fffffff7
[ 1565.938989] R13: ffff9c3281f77d00 R14: 0000000000400000 R15: 00000000001be2e5
[ 1565.938990] FS:  0000000000000000(0000) GS:ffff90ae40a00000(0000) knlGS:0000000000000000
[ 1565.938990] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1565.938991] CR2: 00007fde9bfffa08 CR3: 0000001011d14002 CR4: 00000000003606f0
[ 1565.938991] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1565.938991] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 1565.938991] Call Trace:
[ 1565.938997]  iwl_trans_pcie_release_nic_access+0x61/0x70 [iwlwifi]
[ 1565.939000]  iwl_trans_pcie_read_mem+0x99/0xc0 [iwlwifi]
[ 1565.939004]  iwl_fw_dump_mem.isra.21.part.22+0x50/0x90 [iwlwifi]
[ 1565.939008]  iwl_fw_error_dump_file.isra.23+0xe10/0xff0 [iwlwifi]
[ 1565.939011]  iwl_fw_dbg_collect_sync+0x301/0x530 [iwlwifi]
[ 1565.939012]  ? __mutex_lock_slowpath+0x13/0x20
[ 1565.939015]  iwl_fw_error_dump_wk+0x57/0x80 [iwlwifi]
[ 1565.939017]  process_one_work+0x1fd/0x3f0
[ 1565.939018]  worker_thread+0x34/0x410
[ 1565.939019]  kthread+0x121/0x140
[ 1565.939020]  ? process_one_work+0x3f0/0x3f0
[ 1565.939020]  ? kthread_park+0xb0/0xb0
[ 1565.939021]  ret_from_fork+0x1f/0x40
[ 1565.939285] iwlwifi 0000:03:00.0: Queue 10 is inactive on fifo 2 and stuck for 10000 ms. SW [33, 52] HW [162, 162] FH TRB=0x0a5a5a5a2
[ 1566.424152] iwlwifi 0000:03:00.0: Hardware error detected. Restarting.
[ 1566.470617] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 8 [0xa5a5a5a2]
[ 1566.491783] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 1566.608801] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 1566.673783] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 1566.685985] iwlwifi 0000:03:00.0: BIOS contains WGDS but no WRDS

We have investigated the issue and it turns out that the reference implementation of the BIOS recommends having WGDS set to NOP values when WRDS is not included.  This is what is causing the problem in so many platforms.  The error message itself is harmless, so I'm going to reduce the logging level as suggested.

The errors reported here containing "NMI_INTERRUPT_UNKNOWN" are different issues and not related to the WGDS error message.

Created attachment 288513 [details]
patch with potential fix

Can someone please test this patch? It's based on Linus' latest master.  (Some rebasing required for < v5.5 kernels)

(In reply to Luca Coelho from comment #23)
> Can someone please test this patch? It's based on Linus' latest master. 
> (Some rebasing required for < v5.5 kernels)

Patch applied to 5.6.3 (applies clean with some offsets).
WGDS message is gone, wifi seems to work fine.
WGDS message was still there before applying the patch.

Great, thanks for checking! I'll send this out for v5.7.

I sent the patch upstream for v5.7-rc*

https://patchwork.kernel.org/patch/11494327/

Unfortunately after bios update i am receiving error "0000:00:14.3: bios contains wgds but no wrds" during ubuntu booting. It is not possible to run system. In my case it is ubuntu 20.04 updated from 19.10 where I got error first (I tried everything from different threads and I am thinking about bios downgrade now). Only case when I don't get this error is when I disable wifi card in bios but system is also not loading :/ I have Dell laptop with ac9560 wifi card. Any help appreciated.

Is it possible to use this patch from recovery mode ?

This error message (if running without my patch) will *not* cause the system not to run.  The message in itself, though unnecessary, is harmless.

You probably have other issues if your machine is not working.

In kernel 5.15.8 the message is at level err again.

The commit that fixed this was:
650d07d9945c iwlwifi: fix WGDS check when WRDS is disabled

I think that the regression reported in comment #30 can be cause by this other one:
78a19d5285d9 iwlwifi: mvm: Read the PPAG and SAR tables at INIT stage

In `iwl_sar_select_profile` the case that WRDS profile exists but it's disabled. However, this is called from the up stage, and after that commit the tables are read at the init stage.

Now the message is printed from `iwl_mvm_get_acpi_tables`. Some check to differentiate between unavailable and disabled WRDS profile should be added there...

(In reply to Íñigo Huguet from comment #31)
> In `iwl_sar_select_profile` the case that WRDS profile exists but it's
> disabled.

Sorry for the typo: In `iwl_sar_select_profile` the case that WRDS profile exists but it's disabled IS CHECKED.