Unable to wake from sleep

[Eric_Rowen]

Not an answer to the various problems, just my experience with WoL

Plug in Ethernet & WoL Gen 11 and Windows 11

After discovering that the Power Management (PM) tabs are not there for NIC or k/b or mouse {as they are in W10} (and all the registry edits don’t bring it back) you can see PM tab in the USB entries in Device Manager. I disabled (removed tick from the save power entry) from these and somehow and with mains adapter connected got the FW to wake from sleep. Sorting out IF it really had woken (as pressing a key wakes it anyway) I used ping to a virtual Ethernet adapter I had installed to see i…

[Eric_Rowen]

I added a link to the post above which was my separate post on WoL with Windows 11 and 11th Gen i7 Framework.

This added the text, and also truncated it.

I have tried hundreds of WoL configs on PCs over the years the Framework inc UEFO BIOS takes the biscuit.

[Angus_Gratton]

Unsure if these will all turn out to be be related, but I have the same intermittent issue with a Gen12 i5-1240P DIY Edition and Linux. I thought it might be Thunderbolt related (seems to only happen when docked), but @Calvin_Bullock’s posts suggests it might just be AC power related.

BIOS is 3.06 beta, kernel 6.3.3-arch1-1 but it’s been happening for several kernel versions. mem_sleep is the default “s2idle”.

System logs don’t seem to give any meaningful clues. Here’s the last lines that made it to disk from a suspend which gets stuck and needed a forced power cycle:

May 26 09:13:16 hostname systemd-sleep[316448]: Entering sleep state 'suspend'...
May 26 09:13:16 hostname kernel: PM: suspend entry (s2idle)

Click to see a previous suspend (same kernel, same connected peripherals, etc.) that woke up successfully.

May 25 15:18:49 hostname systemd-sleep[143675]: Entering sleep state 'suspend'...
May 25 15:18:49 hostname kernel: PM: suspend entry (s2idle)
May 25 15:18:49 hostname kernel: Filesystems sync: 0.023 seconds
May 25 15:18:49 hostname wpa_supplicant[1919]: wlp166s0: CTRL-EVENT-DSCP-POLICY clear_all
May 25 15:18:49 hostname wpa_supplicant[1919]: nl80211: deinit ifname=wlp166s0 disabled_11b_rates=0
May 25 15:18:49 hostname bluetoothd[1833]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x002d
May 25 16:13:46 hostname kernel: Freezing user space processes
May 25 16:13:46 hostname kernel: Freezing user space processes completed (elapsed 0.005 seconds)
May 25 16:13:46 hostname kernel: OOM killer disabled.
May 25 16:13:46 hostname kernel: Freezing remaining freezable tasks
May 25 16:13:46 hostname kernel: Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
May 25 16:13:46 hostname kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 25 16:13:46 hostname kernel: ACPI: EC: interrupt blocked
May 25 16:13:46 hostname kernel: ACPI: EC: interrupt unblocked
May 25 16:13:46 hostname kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.5.1
May 25 16:13:46 hostname kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
May 25 16:13:46 hostname kernel: iwlwifi 0000:a6:00.0: WRT: Invalid buffer destination
May 25 16:13:46 hostname kernel: i915 0000:00:02.0: [drm] HuC authenticated
May 25 16:13:46 hostname kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
May 25 16:13:46 hostname kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
May 25 16:13:46 hostname kernel: i915 0000:00:02.0: [drm] GuC RC: enabled
May 25 16:13:46 hostname kernel: iwlwifi 0000:a6:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x1f
May 25 16:13:46 hostname kernel: iwlwifi 0000:a6:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
May 25 16:13:46 hostname kernel: iwlwifi 0000:a6:00.0: WFPM_AUTH_KEY_0: 0x80
May 25 16:13:46 hostname kernel: iwlwifi 0000:a6:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
May 25 16:13:46 hostname kernel: thunderbolt 1-0:3.1: new retimer found, vendor=0x8087 device=0x15ee
May 25 16:13:46 hostname kernel: thunderbolt 1-3: new device found, vendor=0xf0 device=0xe56
May 25 16:13:46 hostname kernel: thunderbolt 1-3: HP Inc. HP Thunderbolt 3Dock
May 25 16:13:46 hostname kernel: OOM killer enabled.
May 25 16:13:46 hostname kernel: Restarting tasks ... 

(bluetoothd log line is in there because it’s logging at debug level, for unrelated reasons.)

ectool console seems to only go back about 3 minutes and I was too slow to dump it after resetting this time. I’ll try again next time, judging from the timestamps it seems like the EC doesn’t reset itself so there might be a clue in there.

[ry1]

Ive observed similar issues with my own framework, but it goes to include locking up after a restart and some other diverging issues. i believe the core cause of the issue is the same as this threads issue, but have created a separate instance for mine due to the crashing, bluescreening, and locking up when power is connected for me (Framework freezes on hibernation/plugging in power)

[Angus_Gratton]

@Angus_Gratton

ectool console seems to only go back about 3 minutes and I was too slow to dump it after resetting this time

Got an ectool console log this time (Framework went to sleep on battery power, was plugged into an unpowered TB3 dock while asleep, dock was powered on, and then Framework failed to wake).

This console dump is from immediately after cycling power with the power button and booting linux. I haven’t dug into any of the values here, possible it’s nothing to do with the EC and purely in the BIOS.

58009.687831 HC 0x98]
226 HC 0x97]
[57993.685270 HC 0x98]
+++(++)[57994.232099 charge_request(16600mV, 0mA)]
[57994.810070 charge_request(16592mV, 0mA)]
[57995.389016 charge_request(16584mV, 0mA)]
[57995.967044 charge_request(16592mV, 0mA)]
[57996.545056 event set 0x0000000000000080]
[57996.546067 event clear 0x0000000000000080]
[57996.546685 ACPI query = 8]
PORT80: 0008
[57997.125661 charge_request(16568mV, 0mA)]
[57997.906106 charge_request(16592mV, 0mA)]
[57998.484442 charge_request(16568mV, 0mA)]
[57999.062479 charge_request(16528mV, 0mA)]
[57999.741837 charge_request(16552mV, 0mA)]
[58000.420908 charge_request(16496mV, 0mA)]
[58001.678921 charge_request(16512mV, 0mA)]
[58002.256843 charge_request(16488mV, 0mA)]
[58002.835912 charge_request(16512mV, 0mA)]
[58003.516107 charge_request(16528mV, 0mA)]
[58003.711639 HC 0x97]
[58003.712876 HC 0x98]
+++(++)[58003.795506 event set 0x0000000200000000]
[58003.796656 event clear 0x0000000200000000]
[58003.797314 ACPI query = 34]
PORT80: 0022
[58004.299488 Battery 79% (Display 82.4 %) / 15h:36 to empty]
[58004.300467 Charge Limit mode = 0]
[58004.304377 charge_request(16536mV, 0mA)]
[58004.883281 Battery 79% (Display 82.4 %) / 16h:32 to empty]
[58004.884216 Charge Limit mode = 0]
[58004.886784 charge_request(17600mV, 712mA)]
[58006.044202 event set 0x0000000000000080]
[58006.045492 event clear 0x0000000000000080]
[58006.046110 ACPI query = 8]
PORT80: 0008
[58006.699087 event set 0x0000000200000000]
[58006.700808 event clear 0x0000000200000000]
[58006.701466 ACPI query = 34]
PORT80: 0022
[58007.305735 Battery 80% (Display 82.4 %) / 4h:16 to full]
[58007.306736 Charge Limit mode = 1]
[58007.309231 charge_request(16840mV, 0mA)]
[58007.889494 Battery 80% (Display 82.4 %) / 3h:49 to full]
[58007.890495 Charge Limit mode = 1]
[58007.892989 charge_request(16848mV, 0mA)]
[58008.472335 charge_request(16664mV, 0mA)]
[58009.254410 charge_request(16592mV, 0mA)]
[58009.682145 HC 0x02]
[58009.685621 HC 0x0b]
[58009.686784 HC 0x97]

[Calvin_Bullock]

I have found this on the arch wiki, I don’t know if it is the issue but it sounds possible:

"Users with Alder Lake-P 12th gen mobile processor laptops from various vendors experienced freeze and black-screen after waking up from suspending. It is because many laptop vendors ship an incorrect VBT (Video BIOS Table) that wrongly describe the actual ports connected to the iGPU. Considering most vendors will not publish a BIOS update for a laptop with a properly working Windows OS, Linux users could only address the issue on the kernel side. You can mitigate the issue by patching and rebuilding the kernel as a temporary remedy:

drivers/gpu/drm/i915/display/intel_display.c.patch

--- a/drivers/gpu/drm/i915/display/intel_display.c
+++ b/drivers/gpu/drm/i915/display/intel_display.c
@@ -8835,7 +8835,7 @@ static void intel_setup_outputs(struct drm_i915_private *dev_priv)
                intel_ddi_init(dev_priv, PORT_TC1);
        } else if (IS_ALDERLAKE_P(dev_priv)) {
                intel_ddi_init(dev_priv, PORT_A);
-               intel_ddi_init(dev_priv, PORT_B);
+               // intel_ddi_init(dev_priv, PORT_B);
                intel_ddi_init(dev_priv, PORT_TC1);
                intel_ddi_init(dev_priv, PORT_TC2);
                intel_ddi_init(dev_priv, PORT_TC3);

"
issue 6.18
https://wiki.archlinux.org/title/intel_graphics

I haven’t tried this fix yet as I don’t fully understand it so if anyone here could help me make sense of it I would aprachate it, or Ill reply back when i figure it out or find it is not my issue.

[Simon_Knight]

Any update on this issue please? Between this and the boot up fan noise I’m considering returning the Framework Laptop under warranty.

[dosssman]

@Simon_Knight

Any update on this issue please? Between this and the boot up fan noise I’m considering returning the Framework Laptop under warranty.

That issue was largely fixed in the later kernel release.

I have a i7 1260P running Arch Linux, and back then linux was around 5.9.
In my case I had better luck using linux-clear kernel as they incorporated the fix a bit earlier than the main linux kernel version. Nowadays even the default kernel should sleep and wake up without issue.

Might want to specify your FW’s specs, and OS distribution and kernel version ?

On a tangential note, I did not have any boot up fan noise problem though. Fan would be noisier than usually even on relatively light workloads, but this essentially gone after I installed autocpu-freq.

[Simon_Knight]

Might want to specify your FW’s specs

You’re absolutely right @dosssman , I’m on Windows 11 with a Framework Laptop DIY Edition (12th Gen). I’m having issues with both fan noise and hibernation wake.