Did you check which service were using how much resource? 27 Tem 2024 Cmt 07:10 tarihinde <2qdxy4rzwzuui...@potatochowder.com> şunu yazdı:
> On 2024-07-26 at 17:59:15 -0500, > "David C. Rankin" <drankina...@gmail.com> wrote: > > > On 7/26/24 8:38 AM, 2qdxy4rzwzuui...@potatochowder.com wrote: > > > I would include logs and version numbers, but I'm not sure where to > > > start. :-) > > > > > > I checked the BBS, but I didn't immediately't see anything related. > > > > > > Any ideas? > > > > A guess, > > > > First - what model laptop/CPU? > > It's a Sager/Clevo NP8852P. > > $ grep Intel /proc/cpuinfo|sed 2q > vendor_id : GenuineIntel > model name : 12th Gen Intel(R) Core(TM) i7-12700H > > > I ask because if I recall correctly, one of the changes the 6.10 kernel > > brought it was "improved" scaling of CPU core speed. This would have been > > from the release notes either from The Register or Phronix. My only > thought > > is you may have a CPU/chipset, or or passing kernel parameters on boot > that > > isn't playing nice with the new CPU scaling preventing your core > processor > > speed from idling down. > > > > (top would still show 100% idle -- but your CPU may be idling a 3.5GHz) > > > > You can check if your cores are idling down with: > > > > grep '^processor\|^cpu MHz' /proc/cpuinfo > > processor : 0 > cpu MHz : 400.000 > processor : 1 > cpu MHz : 400.000 > processor : 2 > cpu MHz : 400.000 > processor : 3 > cpu MHz : 400.000 > processor : 4 > cpu MHz : 851.190 > processor : 5 > cpu MHz : 400.000 > processor : 6 > cpu MHz : 400.000 > processor : 7 > cpu MHz : 400.000 > processor : 8 > cpu MHz : 1083.960 > processor : 9 > cpu MHz : 400.000 > processor : 10 > cpu MHz : 1006.537 > processor : 11 > cpu MHz : 400.000 > processor : 12 > cpu MHz : 942.949 > processor : 13 > cpu MHz : 968.000 > processor : 14 > cpu MHz : 1361.782 > processor : 15 > cpu MHz : 1400.012 > processor : 16 > cpu MHz : 400.000 > processor : 17 > cpu MHz : 400.000 > processor : 18 > cpu MHz : 400.000 > processor : 19 > cpu MHz : 1384.733 > > And I just re-opened the lid to check for activity on my post. > > > If your cores are running at full-speed, this may be an area worth > further > > investigating. > > Bingo. > > My issue isn't resolved, but I at least I have something to go on. > > Thanks, David. > > Regards, > Dan >
