Thanks, @Anachron. I’ve just submitted a ticket, but if anyone in the community has ideas for debugging or that might fix, let me know. I’ll update here with support’s verdict too.
For those interested, I had and still have the same issue. Updated the BIOS to the alpha version, re-pasted with PTM7950, double checked the pad locations for the VRMs, the whole nine-yards.
I received a replacement mainboard after months of troubleshooting and the thing idles around 80C and will still clock-throttle down to 400 MHz even at 60C. Then it will constantly jump to 100C and trigger PROCHOT again. I repeated the same procedures that I did with the original board, at my own expense again - no dice. There is something wrong, and I’m not the only one with this issue. I just want to swap to a ryzen board at this point because I’ve never had issues with my other ryzen chips - but I will not at my own expense, it’s not acceptable. I have an early batch 12th gen i7-1280p and have not been able to actually use the thing because of this issue.
I’m going to bump this(sorry folks!) because Intel and Framework really need to look into the throttling and power delivery issues, I’m linking my previous reply on another thread below for visibility here.
I’d like to see feedback from the community so that we can aggregate how many people are seeing this issue.
All I want is the best for the community and company and we are aware that FW are relatively green still, but we need these issues at the top of the queue so that reputation isn’t tarnished. I would expect that it is in the company’s best interest to uphold sustainable and long-term usage, but many of us can’t even get short-term usage OOB.
I understand first-hand the hardships that come with working with (external) partners and vendors, but I feel it’s been a good amount of time to really start a conversation.
And believe me, I have tried everything and gone above and beyond, spent a lot of my own money and provided more than adequate diagnostic information to the FW support team. (I’m sure they would love to fire me as a customer! )
But, jokes aside - I get it, the new launch is coming and the pressure is certainly on. It just feels like in certain circumstances it’s a situation of “biting off more than one can chew”, but I can only make assumptions.
I am willing to run as many diagnostics as possible and provide as much data as I can and I encourage the community to do so as well. (I do this to an extent for a living) Just let me know what you would like to see.
My experience thus far: | (Unusable since received October of 2022)
“Hi there, don’t know if anybody else tried this, but I may have found a workaround to keep this problem from happening:
The only caveats are that it keeps the CPU from using the full speed available, but it keeps the laptop stable, and if you update the BIOS it resets the settings, so make sure to keep an eye on that.
If you go into BIOS and set CPU to Max-Non Turbo Performance and Disable Intel SpeedStep, SpeedShift and Turbo Boost Max, then it should keep the problem from happening.
This is with a Intel 11 i5, 16gb RAM and Windows 11, but it also fixed the problem on a Intel 12 i5 as well.
Hope this helps somebody!”
I tried this but kept intel SpeedStep enabled, and the 400Mhz problem went away but also kept a partial boost so I’m not stuck at 1.7Ghz. So in conclusion lower boost but also lower throttle. I sure hope this helps you in addition to the other information that was copied!
Update:
I re enabled speedshift and turbo boost max again, as for some reason the E-cores will just idle if those settings are disabled. Somehow after running windows with those settings disabled and re-enabling them seems to have solved the 400Mhz issue. Don’t know whats going on or how it somehow worked, but it did.
I experienced this issue today on my 12th gen i7-1260p Framework Laptop 13 running Fedora 38. I think it was triggered by the laptop waking up from suspend in my bag, failing to suspend again and getting very hot yesterday evening (draining a lot of the battery). After that, I charged it and used it for a bit before suspending it overnight. I’ve been very frustrated today trying to figure out why my laptop had gotten so slow but was able to reproduce the same behaviour using s-tui as in the OP.
I wasn’t able to fix it by restarting (I tried several times) but was able to eventually resolve it by shutting the laptop down, leaving it off for about 10-15 minutes and then turning it on again. I hope it doesn’t come back
Looks like I am not the only one. And it seems to be getting worse over time as well for me. I contacted Support today to see if they have a solution for this. If not, then the framework has to go. It is becoming unbearable.
After struggling with this issue for half a year now I’d like to share my experience: Turns out, that taking out the RAM module and plugging it back in helps fix the issue consistently for a few weeks. So my problem is probably, that the module wiggles itself out of a “stable” state where it doesn’t have to throttle.
)
