Hard block after resume from suspend-to-ram with iwlwifi

[AndyM48]

Artix Linux (Linux slimbook 7.0.12-artix1-1 #1 SMP PREEMPT_DYNAMIC Wed, 10 Jun 2026 16:57:23 +0000 x86_64 GNU/Linux)
Slimbook Executive 14 Intel Core ULTRA 7 255H Model No: Executive 14-UC2
Intel{8086][7740] Arrow Lake CNVi WiFi
Modules: iwlwifi iwlmvm cfg80211 mac80211 rfkill

Suspend standby and freeze work as expected
Suspend-to-RAM (mem) invokes a hardware block on phy0 so that wifi is blocked on resume and cannot be released without restarting the laptop.

Messages for Suspend and Resume are attached

 

[Trml]

The log has a crash after resume due to the rfkill.

There is a kernel config option rfkill.default_state=1 but I suspect it won't help. https://docs.kernel.org/admin-guide/kernel-parameters.html

What happens when you disassociate any wifi and bluetooth connections before the suspend?

Does Artix have the iwlwifi firmware and wireless-regdb packages installed?

 

[AndyM48]

The log has a crash after resume due to the rfkill.

Yes

There is a kernel config option rfkill.default_state=1 but I suspect it won't help. https://docs.kernel.org/admin-guide/kernel-parameters.html

I can try this. I will report back.

What happens when you disassociate any wifi and bluetooth connections before the suspend?

I have tried removing all the modules before suspending, and re inserting them after. No joy.
I have to say I don't understand why this does not work.

Does Artix have the iwlwifi firmware and wireless-regdb packages installed?

Yes, both.

Thank you for the response

 

[AndyM48]

I can try this. I will report back.

You are correct, this did not do help

I have tried removing all the modules before suspending, and re inserting them after. No joy.
I have to say I don't understand why this does not work.

I suppose this could mean that it has nothing to do with rfkill. Something in the BIOS is activating the BIOS hard block on suspend (mem) and rfkill is simply reporting this on resume.
This would be what Intel suggested here:

HW RFKILL is an interrupt from the HW that the driver gets, and then it enables rfkill.
This is not a Linux SW flow, but a HW interrupt we receive from the pci connection.
sharing here the code section:
/* HW RF KILL switch toggled */
if (inta_hw & MSIX_HW_INT_CAUSES_REG_RF_KILL)
iwl_pcie_handle_rfkill_irq(trans);
In this case, the next thing to do will be to get in contact directly with HP for further assistance on this matter.

Unfortunately Slimbook Technical Support will not engage with me on this because I am not running SlimbookOS.

 

[Trml]

Unfortunately Slimbook Technical Support will not engage with me on this because I am not running SlimbookOS.

The reports you link in the Intel community forum are other brands with the same symptom. They could, of course, all run the same Bios base (AMI probably). Does the Bios give power management options that related to PCIe devices? I suppose not, but you never know.

What about slimbook modules? Do they distribute their own module? If yes, that may have options to toggle related to power management.

The machine probably has a hotkey wifi toggle. What happens when you use it before suspend and after?