My windows install is also working fine with default power settings. My issues are all in Linux.
Been experiencing this issue for a little bit now as well. I just updated my BiOS to v3.06 and the Driver Bundle to 10/29/2021. Currently on Windows 11 right now, thought it was possibly an issue with the OS, but reading through the thread I am wondering if it is maybe the driver bundle still causing the issue. I had previously reinstalled the OS on my laptop to correct the issue and had installed the 07/08/2021. No freezing on sleep issues after I had did that, but have returned on the 10/29/2021 bundle. I’m going to try restoring my power settings to default as well, just to see if this may help me.
EDIT: Power settings being reset to Default did not correct my issue. Still freezing up on lock up. Any further ideas would be appreciated!
I am also having sleep/wake problems with Windows 11. Today it was as described previously: system is asleep (pulsing power light) but would not wake up. Had to power it off and back on. It had been on the dock overnight, but I had taken it off before trying to wake it up because I needed to use it away from my desk.
I’ve also had many times when it wouldn’t sleep correctly. The screen (attached via the dock) will go dark, and then immediately come back on to the login screen. I believe this is also happening away from the dock; there have been multiple times when I thought I had put it in sleep mode and came back to find it awake. (This especially worries me because I often have to travel with my laptop and leave it in the trunk for many hours. If it is waking up/running while in the bag, I’m concerned about heat damage.)
I installed the latest BIOS (3.07) and driver package earlier this week. I will try to gather more detailed info going forward.
1 Like
Similar situation currently. Everything was working great until I opened the lid last night. And now I get the same issue as the posted video earlier in this thread…October 12, 2021 - YouTube
2 Likes
After spending the morning testing with my new framework I believe this is a kernel issue (at least on linux). Testing with Kubuntu 21.10 I see sleep functioning normally on kernel 5.13, but if I switch to 5.15 I just get the black screen with constantly-lit power button. I can reliably recreate both scenarios flipping back and forth.
I don’t know enough about linux kernels to suggest a possible root cause, but hopefully this will save some people some headache.
I tried switching to Linux kernel 5.13.0-37-generic (using Pop_OS! 21.10) and this did not fix it for me. I have a DIY edition (see also: Framework and PopOS - #101 by aos)
Just curious to know if others have had any issues with this. I still seem to not be able to wake from deep sleep, I just updated to the latest kernel on PopOS (5.17.5). I was able to get hibernate working, and that’s given me some level of battery life.
Same problem with Windows 11 here. But only seems to be an issue when connected to wall power; ie: when the power brick is connected. So maybe this has something to do with the battery management system preventing the system from going to sleep while it’s plugged in to prevent the system from overcharging?
Hi and welcome to the forum.
a) The system won’t overcharge. Li-ion batteries of this type are not passive receptors of current, they have their own built in monitor and balancer to ensure the battery only gets what it ‘wants’ not what the charger ‘wants’ to provide.
b) Secondly current only flows from a high voltage to a low voltage. A fully charged battery in the Framework will be around 17.5V and the maximum charge can be set in the BIOS. For example I set mine to 78% which corresponds to a max voltage of 16.5V so I could leave it for a year and the battery would not overcharge.
On the topic subject:
A bit too much for me to read, maybe you could clarify your issue as this topic was created a year ago with a different BIOS etc.
You are saying the only issue is that you cannot wake from sleep if it is charging?
Testing:
- Sleep whilst charging/plugged in and wakes with no problem
- Sleep whilst charging, pull plug and wakes with no problem
- Sleep whilst uplugged wakes with no problem
- Sleep whilst uplugged then plug in > wakes as soon as I plugged in
There are so many settings it’s possible you don’t have anywhere near the same as i have.
Windows 11 Home BIOS 3.09
Having this windows 11. With or without and external display. Systems sleeps then will not wake up. Will eventually do a full hard reboot.
Going to try the firmware update when it gets back up from the last cycle of this.
Started experiencing this issue about a month ago. It seems most prevalent when I sleep with my eGPU connected (for 11 months of ownership+egpu use, sleep was absolutely fine). About an hour after suspending the laptop, its fans will kick on at medium speed and ramp up to full, with power button still pulsing. If I try and wake the laptop, nothing happens, and I have to use a force power off to be able to use it. Event Viewer is unhelpful.
Windows 10 Pro, 11th gen i5, bios 3.10. I did not have this problem when I was on bios 3.09, but I only started experiencing this a month after I swapped to 3.10 so I don’t think it’s the bios.
1 Like
Update to my previous post since I’m unable to edit it: disabling USB Selective Suspend and USB 3 Link Power Management when on AC power in my power plan advanced options fixed my freezes in sleep. You will need to use the registry to show these options in the menu, there are many tutorials online to unhide them.
Update to the update: This did not, in fact, fix the issue. It was just my egpu being picky about when it decides to hang during sleep. The only fix is disconnecting the egpu before every sleep and reconnecting it after every wake. It’s annoying.
Update 3: It’s been two weeks and I haven’t had an issue, so I’m confident I found a fix. Nvidia Control Panel → Power Management Mode → change from Auto to Prefer Maximum Performance!
2 Likes
I have also had the problem of sleep not wakening. I have a DIY intel 12th gen edition. I have noticed that the issue seems to happen when plugged into power but not on battery. It also happens seemingly at random. The power button will pulse and keyboard and power button are un-responsive unless I reboot with the power button.
I am running:
Kubuntu 23.04
6.2.0-20 generic kernel
Not an answer to the various problems, just my experience with WoL
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.
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.
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)
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]
2 Likes
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.
1 Like
Any update on this issue please? Between this and the boot up fan noise I’m considering returning the Framework Laptop under warranty.
1 Like