I’m using ryzenadj to monitor only, I’m not actually tweaking anything. Needless to say, performance is badly capped in this state.
Can you specifically try comparing /sys/kernel/debug/amd_pmf/current_power_limits in a failure vs non failure? That would help confirm if there is an EC bug with a power limiter.
It’s difficult for me to pinpoint which change brought this behavior back.
I think a likely cause is the EC triggering thermal throttling; but I don’t have a good way to prove that by reading any registers or so. Maybe if you can monitor the EC debug log in one tab you can check the last messages it emits?
To get the system unstuck, I tried changing the power profile, stopping or re-starting the PPD service, setting scaling_governor (this used to fix it for me) or energy_performance_preference manually, plugging or un-plugging power supply, suspending and resuming (both on AC and on battery), to no avail.
None of those things working really does make me suspect thermal throttling by the EC as well…
By chance - did you happen to unplug the power adapter while in suspend when this issue happened? I’m aware of a bug report in kernel bugzilla with another manufacturer that has a bug with this. It LOOKS like a thermal event sequencing problem with that manufacturer, but if you can confirm the same thing is happening on your Framework 13 that would be a really interesting data point.
Any hints on what to try to get the system unstuck?
If it’s the same thing as that other manufacturer and caused by power adapter changes while in suspend, plug in and then unplug the power adapter after you’ve resumed. See if that brings it back to normal.
Thanks for your quick reply! My system is unstuck again for now (hibernate / resume / unload wifi kernel module / reinsert kernel module), but I’ll check these as soon as I get a chance.
I don’t remember for sure, but this might be the case. I’ll try that this weekend, to see if I can reproduce this.
So far, I haven’t been able to reproduce the behavior.
I’m pretty sure the power limits shown by ryzenadj were not lowered when the system was stuck. The power consumption stayed way below the limits I could see (was running watch -n 1 ryzenadj in a terminal while the system was stuck. I didn’t take a screenshot though).
FWIW I don’t think it’s just you. I think it’s probably your combination of devices/chargers triggering a bug somewhere. My educated guess from these kinds of bugs is that it’s most likely in the EC or PD controller.
Note down EXACT order of events and what devices caused it. Did you have it plugged in before suspend, did you unplug during suspend? How did you wake it? Did you have a dock connected, is it tied to that?
If you can reproduce it at will with a sequence of events and devices then it’s more likely Framweork support can too and then they can capture debug information to fix it!
Me again, been a while. Thanks Mario, I wish I could identify a logical series of steps to recreate, its maddening.
Most of the time I am plugged into a UGREEN 65W charger, but sometimes roam, and the issue still occurs (only in Gnome?, see below)
Curious series of events recently.
Been having a play with Cosmic DE on Fedora 40, the same install as above. Cosmic DE installed via the COPR, nothing too dramatic. (Still using gdm)
Flipping back to Gnome and the stuttering/lag started again (almost immediately), with, again, nothing terribly exciting happening.
Once it happened in Gnome for the 3rd time, I managed to switch back to Cosmic DE and the stuttering/lag remained happening (including gdm) telling me its a fundamental system level funkyness that’s triggered.
The stuttering/lag has yet to begin on Cosmic DE, I’ll be keeping to Cosmic DE for a while (as I am liking the whole proposition).
Hi, so I have had the 544 MHz CPU lock just this afternoon and I cannot reproduce it now, with Framework 13, AMD Ryzen 7840U. No dock, just the charger.
My memory is not very good here, but the timeline supported by kernel logs and charging data from upower is this:
Aug 09 13:46:02 system boot
total of 14 other suspend entry/exit in between
Aug 12 16:38:56 wake from suspend (lid opened)
Aug 12 16:39:03 system detected a charging cable – shows as an error ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Aug 12 17:58:56 Lid closed → sleep
(I think) I pulled the cable out, but it is also possible that it was out shortly before sleep. Last charging entry is 17:58:46.
Aug 12 18:02:41 Lid opened → resume
laptop is slower, laggier, CPU frequency stuck at 544 MHz is displayed in cpupower frequency-info, switching PPD to power_saver, or balanced, does not help. Playing a HW-accelerated video in Firefox works fine, though.
Aug 12 20:46:47 Lid closed → sleep
Aug 12 20:55:01 Lid opened – laptop is still slow
Aug 12 21:28:01 Connected charging cable → unlocked the CPU frequency.
The problem is that it only happens very very rarely now, I cannot remember the last occurrence, and I could not collect any EC logs from this time, as my system had the security=lockdown set.
I suspect it happened from unplugging the cable during sleep. There seems to be something that we t wrong there. Try specifically to reproduce it using that action and the real Framework charger if you can.
I will try with FW charger but it will have to wait until next week. Also I am unable to replicate this right now, I have tried at least 8 times already, with different timing.
It is true that I primarily use a Dell TB4 dock at home, which normally charges my laptop, and normally I have the FW charger with me, but right now I cannot get back to it
