Closed justanerd closed 3 years ago
Hello,
Register_CPU_Idle
is not implemented for AMD but Register_CPU_Freq
& Register_Governor
are.
Do you confirm from /proc/modules
that any previous registered cpufreq
is unloaded ?
The current has to be force removed (b/c Kernel does not like to live without a cpufreq driver once registered ! some Mutex reasons according to its source code)
My SysLinux/ArchLinux command line, for an Intel Westmere W3690` is the folowing:
BOOT_IMAGE=../vmlinuz-linux root=/dev/disk/by-label/ROOT rw rootdelay=0 quiet loglevel=3 rd.udev.log-priority=3 break=n agp=off ipv6.disable=1 selinux=0 plymouth.enable=0 consoleblank=0 vt.color=0x03 nmi_watchdog=0 modprobe.blacklist=pcspkr,iTCO_wdt,acpi_cpufreq,pcc_cpufreq,intel_cstate,intel_uncore,intel_powerclamp,i7core_edac,i5500_temp,coretemp,asus_atk0110,nouveau idle=halt intel_pstate=disable cpufreq.off=0 pcie_aspm=off intremap=off cpu0_hotplug audit=0 intel_idle.max_cstate=0 sysrq_always_enabled=1 acpi_enforce_resources=lax iommu=pt initrd=../intel-ucode.img,../initramfs-linux.img
Btw: if you boot with Kernel parametercpufreq.off=1
, then CoreFreq should take the leadership on the P-States (no driver options required).
I tried cpufreq.off=1 corefreq-cli shows all drivers off Any way to verify if the P-State control is working?
I tried cpufreq.off=1 corefreq-cli shows all drivers off Any way to verify if the P-State control is working?
Yes, if you can increase the Max
or any Boosted 1C
, 2C
; it means that my driver is in control of the P-States. The Target TGT
is also related to P-States, as a limiter.
Please, gently raise the frequently ratio with one bin, as a starter
I tried to change all the PSTATE settings I can choose the ratios but they will not get applied.
Was this on the master
branch ? May-be try the current develop
I forgot to say : Core Performance Boost has to be disabled prior setting new ratios I saw BIOS screenshots calling it Manual OC
Technologies
window and press Turbo OFFThat worked. Sadly I can't increase past 3.7Ghz.
That worked. Sadly I can't increase past 3.7Ghz.
Did you get a stable frequency ? For the whole Processor or for distinct Core(s) ? What's the max frequency ratio you can set in BIOS or other tools ?
That worked. Sadly I can't increase past 3.7Ghz.
Did you get a stable frequency ? Yes For the whole Processor or for distinct Core(s) ? whole What's the max frequency ratio you can set in BIOS or other tools ? With https://github.com/r4m0n/ZenStates-Linux I can enable the OC mode for all core to whatever I want. But the P-State stuff is also not working with higher frequencies.
3970X is advertized with a frequency boost up to 4.5 GHz. How high your BIOS let you set in manual OC ? Do you them read the same frequency ratio between BIOS and CoreFreq and Kernel ?
I haven't tried the Custom P-State option yet but with a static divider I can set what ever I want. I mostly run the system with PBO because all core overclocks are not good for single core performance.
On Sat, May 16, 2020 at 6:52 PM CYRIL INGENIERIE notifications@github.com wrote:
3970X is advertized with a frequency boost up to 4.5 GHz. How high your BIOS let you set in manual OC ? Do you them read the same frequency ratio between BIOS and Kernel ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cyring/CoreFreq/issues/181#issuecomment-629675000, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAF7RJKB2GRG75G6DK7PT33RR3AFZANCNFSM4MP656SQ .
Hello,
Could you try the develop
branch and post back the Topology in text mode:
corefreq-cli -s -m
Thank you
sure output.txt
I'm not sure about the caches size: with 64 x SMT Cores, I'm decoding for a double value, compared to AMD datasheet. Can you tell which sum is written for L1 L2 L3 in the UI header ?
Thanks. AMD says:
Total cache L1 = 2MB
Total cache L2 = 16MB
Total cache L3 = 128MB
Considering 32 physical Cores, L1 and L2 unit size in KB is ok, but L3 is wrong. Still searching but I'm using the same algorithm for Ryzen and Threadripper
Hello,
I'm rolling back to the AMD L3 cache size formula where register is given in 512 KB units.
Can you pull and try the latest develop
branch.
Thank you.
Hello,
I'm trying to read the thermal sensor per node which to my understanding counts more than one with EPYC & Threadripper
Could you please try the develop
version. Once UI is running go to Settings > Thermal scope
and change it to Thread
, such as below.
Thanks for trying Regards
Hello, Among the last changes in issue #195 , an I/O ASM access to the FCH have been added: can you please check if the last CoreFreq version is starting fine ? Thank you
Yes, runs fine.
Yes, runs fine.
Thank you very much
Hello,
For your testings, the cpufreq is available in the develop
branch
You will have to blacklist any current cpufreq driver, like acpi-cpufreq
, to leave the room to the CoreFreq driver
CoreFreq's cpufreq can be registered from its kernel module using these two options:
insmod corefreqk.ko Register_CPU_Freq=1 Register_Governor=1
or from the Client: you first register the governor then CPU-Freq
Remark: CPU-Idle is not implemented yet.
Once CoreFreq's cpufreq well registered, you can play with:
freq=3500000; for cpu in /sys/devices/system/cpu/cpufreq/policy*/scaling_setspeed ; do echo $freq > $cpu; done
### where freq is one of your available frequencies (ratio shown in cyan color)
echo 0 > /sys/devices/system/cpu/cpufreq/boost
echo 1 > /sys/devices/system/cpu/cpufreq/boost
### and many other file attributes in the tree /sys/devices/system/cpu/cpufreq
Any change made on command line should be reflected in the UI
Cyril
Hello,
In the develop
branch is available a fix to monitor the temperature per CCD.
Could you please try with the Threadripper ?
Settings
and change the Thermal scope
to Core
or Thread
; next you stress per CPU with the Tools > Turbo Select CPU...
If things works OK, CPUs belonging to the same CCD should raise their temperature together.
It shows temps but they are completely in sync.
It shows temps but they are completely in sync.
Thanks for testing.
Can you post the full output of the topology using corefreq-cli -m
I have to check the CCD resulting of Threadripper
Be aware you have to stress differently CPUs to observe temps
You can now switch to the master branch
Hello,
In the develop
branch is available a fix to enumerate the CCD and CCX identifiers.
Can you please provide the topology output ?
To my understanding CCX refers to the L3 cache shared by a group of 4 cores; whereas CCD is the complex die gathering 8 Cores
Fyi here is my Ryzen 3950X map:
CPU Pkg Apic Core/Thread Caches (w)rite-Back (i)nclusive
# ID ID CCD CCX ID/ID L1-Inst Way L1-Data Way L2 Way L3 Way
000:BSP 0 0 0 0 0 32 8 32 8 512 8 i 65536 16w
001: 0 2 0 0 1 0 32 8 32 8 512 8 i 65536 16w
002: 0 4 0 0 2 0 32 8 32 8 512 8 i 65536 16w
003: 0 6 0 0 3 0 32 8 32 8 512 8 i 65536 16w
004: 0 8 0 1 4 0 32 8 32 8 512 8 i 65536 16w
005: 0 10 0 1 5 0 32 8 32 8 512 8 i 65536 16w
006: 0 12 0 1 6 0 32 8 32 8 512 8 i 65536 16w
007: 0 14 0 1 7 0 32 8 32 8 512 8 i 65536 16w
008: 0 16 1 0 8 0 32 8 32 8 512 8 i 65536 16w
009: 0 18 1 0 9 0 32 8 32 8 512 8 i 65536 16w
010: 0 20 1 0 10 0 32 8 32 8 512 8 i 65536 16w
011: 0 22 1 0 11 0 32 8 32 8 512 8 i 65536 16w
012: 0 24 1 1 12 0 32 8 32 8 512 8 i 65536 16w
013: 0 26 1 1 13 0 32 8 32 8 512 8 i 65536 16w
014: 0 28 1 1 14 0 32 8 32 8 512 8 i 65536 16w
015: 0 30 1 1 15 0 32 8 32 8 512 8 i 65536 16w
016: 0 1 0 0 0 1 32 8 32 8 512 8 i 65536 16w
017: 0 3 0 0 1 1 32 8 32 8 512 8 i 65536 16w
018: 0 5 0 0 2 1 32 8 32 8 512 8 i 65536 16w
019: 0 7 0 0 3 1 32 8 32 8 512 8 i 65536 16w
020: 0 9 0 1 4 1 32 8 32 8 512 8 i 65536 16w
021: 0 11 0 1 5 1 32 8 32 8 512 8 i 65536 16w
022: 0 13 0 1 6 1 32 8 32 8 512 8 i 65536 16w
023: 0 15 0 1 7 1 32 8 32 8 512 8 i 65536 16w
024: 0 17 1 0 8 1 32 8 32 8 512 8 i 65536 16w
025: 0 19 1 0 9 1 32 8 32 8 512 8 i 65536 16w
026: 0 21 1 0 10 1 32 8 32 8 512 8 i 65536 16w
027: 0 23 1 0 11 1 32 8 32 8 512 8 i 65536 16w
028: 0 25 1 1 12 1 32 8 32 8 512 8 i 65536 16w
029: 0 27 1 1 13 1 32 8 32 8 512 8 i 65536 16w
030: 0 29 1 1 14 1 32 8 32 8 512 8 i 65536 16w
031: 0 31 1 1 15 1 32 8 32 8 512 8 i 65536 16w
If you find the Threadripper map OK, can you also try the per CCD temperature ?
Thank you
looks better:
zenpower output for reference:
Thanks for your return.
Do you mind to post the topology output ?
To my concern, I don't understand why some groups of temperature remain at zero:
Here showing my Ryzen case:
We can see a CCD at 36° , the other one at 51°C
Warning: if you are using another monitoring tool while CoreFreq is running, then my driver has to be built in a special way to share a kernel mutex among all tools going through the SMU (presuming they are doing the same)
The build for a kernel protected SMU access is:
make HWM_CHIPSET=COMPATIBLE clean all
Remark HWM_CHIPSET=COMPATIBLE
has not been intensively tested. So If you rather want to stay with the CoreFreq driver standard way:
make clean all
then you have to make to sure no other software and their respective driver are not accessing the SMU: zenpower being one of them.
New change again in the develop
branch to count 4 Cores per CCD
Previous results don't look like any screenshots of Threadrippers I can see on the Internet
Sorry for this new change and thank you for providing the topology output.
First and third temps are always the same.
topology:
https://pastebin.ubuntu.com/p/S3sCNfghK9/
First and third temps are always the same.
Thank you for your returns
Based on the PPR specs above, it appears that one every two CCD is wired; may be because of the Threadripper design.
Based on the current develop
branch, could you replace this source code:
https://github.com/cyring/CoreFreq/blob/dba5cc60d7f1fda33ef027e65d3072b6e6aa1698/corefreqk.c#L11023
with this:
Core_AMD_SMN_Read( TccdSensor,
SMU_AMD_THM_TCTL_CCD_REGISTER_F17H
+ ((2 * Core->T.Cluster.CCD) << 2),
SMU_AMD_INDEX_REGISTER_F17H,
SMU_AMD_DATA_REGISTER_F17H );
Please build, reload driver all and test temperatures.
Fyi, this change is interlacing the CCD when querying the SMU for sensors; a series of computed IDs, as follows 0 2 4 6
looks better now:
first and last CCX still have the same temperature
first and last CCX still have the same temperature
Probably applying load per CPU may help to understand the temperature relatively to the CCD and CCX clusters.
Sharing my readings of the specs:
up to eight core/cache complex dies (CCD) and a single I/O die (IOD).
SP3 consists of from two to eight CCDs plus one IOD
The two CCXs of a CCD share a single GMI2 Fabric port to the IOD.
A single CCX consists of ... Four cores ... single-thread mode (1T) or two-thread SMT mode (2T)
I'm trying to find in specs for a discriminant register to refine the topology among the 8 x CCD registers.
We could also count the CCD ID based on the architecture code-name but we have to consider the 3990X case and other EPYC 64 Cores where all the 8 CCD should be wired; and where the above code trick won't make it.
Can you please post the CPUID dump
corefreq-cli -u
I'm especially interested by the latest physical Core of your Threadripper which would be CPU #31
Can you please output this ?
lspci -n
00:00.0 0600: 1022:1480 00:00.2 0806: 1022:1481 00:01.0 0600: 1022:1482 00:02.0 0600: 1022:1482 00:03.0 0600: 1022:1482 00:04.0 0600: 1022:1482 00:05.0 0600: 1022:1482 00:07.0 0600: 1022:1482 00:07.1 0604: 1022:1484 00:08.0 0600: 1022:1482 00:08.1 0604: 1022:1484 00:14.0 0c05: 1022:790b (rev 61) 00:14.3 0601: 1022:790e (rev 51) 00:18.0 0600: 1022:1490 00:18.1 0600: 1022:1491 00:18.2 0600: 1022:1492 00:18.3 0600: 1022:1493 00:18.4 0600: 1022:1494 00:18.5 0600: 1022:1495 00:18.6 0600: 1022:1496 00:18.7 0600: 1022:1497 01:00.0 1300: 1022:148a 02:00.0 1300: 1022:1485 02:00.3 0c03: 1022:148c 20:00.0 0600: 1022:1480 20:00.2 0806: 1022:1481 20:01.0 0600: 1022:1482 20:02.0 0600: 1022:1482 20:03.0 0600: 1022:1482 20:03.1 0604: 1022:1483 20:04.0 0600: 1022:1482 20:05.0 0600: 1022:1482 20:07.0 0600: 1022:1482 20:07.1 0604: 1022:1484 20:08.0 0600: 1022:1482 20:08.1 0604: 1022:1484 21:00.0 0300: 10de:1b06 (rev a1) 21:00.1 0403: 10de:10ef (rev a1) 22:00.0 1300: 1022:148a 23:00.0 1300: 1022:1485 23:00.1 1080: 1022:1486 23:00.3 0c03: 1022:148c 40:00.0 0600: 1022:1480 40:00.2 0806: 1022:1481 40:01.0 0600: 1022:1482 40:01.1 0604: 1022:1483 40:02.0 0600: 1022:1482 40:03.0 0600: 1022:1482 40:03.1 0604: 1022:1483 40:03.2 0604: 1022:1483 40:03.3 0604: 1022:1483 40:03.4 0604: 1022:1483 40:04.0 0600: 1022:1482 40:05.0 0600: 1022:1482 40:07.0 0600: 1022:1482 40:07.1 0604: 1022:1484 40:08.0 0600: 1022:1482 40:08.1 0604: 1022:1484 41:00.0 0604: 1022:57ad 42:01.0 0604: 1022:57a3 42:02.0 0604: 1022:57a3 42:03.0 0604: 1022:57a3 42:04.0 0604: 1022:57a3 42:05.0 0604: 1022:57a3 42:08.0 0604: 1022:57a4 42:09.0 0604: 1022:57a4 42:0a.0 0604: 1022:57a4 43:00.0 0108: 144d:a808 44:00.0 0200: 8086:1563 (rev 01) 44:00.1 0200: 8086:1563 (rev 01) 46:00.0 0c03: 1b21:2142 47:00.0 0106: 1b21:0612 (rev 02) 48:00.0 0280: 8086:2723 (rev 1a) 49:00.0 1300: 1022:1485 49:00.1 0c03: 1022:149c 49:00.3 0c03: 1022:149c 4a:00.0 0106: 1022:7901 (rev 51) 4b:00.0 0106: 1022:7901 (rev 51) 4c:00.0 0108: 144d:a808 4d:00.0 0108: 1987:5012 (rev 01) 4e:00.0 0108: 144d:a808 4f:00.0 0108: 144d:a808 50:00.0 1300: 1022:148a 51:00.0 1300: 1022:1485 60:00.0 0600: 1022:1480 60:00.2 0806: 1022:1481 60:01.0 0600: 1022:1482 60:02.0 0600: 1022:1482 60:03.0 0600: 1022:1482 60:04.0 0600: 1022:1482 60:05.0 0600: 1022:1482 60:07.0 0600: 1022:1482 60:07.1 0604: 1022:1484 60:08.0 0600: 1022:1482 60:08.1 0604: 1022:1484 61:00.0 1300: 1022:148a 62:00.0 1300: 1022:1485
Thanks.
I was expecting to decode this statement from the Specs:
The processor includes configuration space registers located in both BCS and ECS. Processor configuration space is accessed through bus 0, devices 18h to 1Fh, where device 18h corresponds to node 0 and device 1Fh corresponds to node 7
and find one device per enabled CCD; but in fact, comparing to my 3950X ...
00:00.0 0600: 1022:1480
00:00.2 0806: 1022:1481
00:01.0 0600: 1022:1482
00:01.1 0604: 1022:1483
00:01.2 0604: 1022:1483
00:02.0 0600: 1022:1482
00:03.0 0600: 1022:1482
00:03.1 0604: 1022:1483
00:04.0 0600: 1022:1482
00:05.0 0600: 1022:1482
00:07.0 0600: 1022:1482
00:07.1 0604: 1022:1484
00:08.0 0600: 1022:1482
00:08.1 0604: 1022:1484
00:08.2 0604: 1022:1484
00:08.3 0604: 1022:1484
00:14.0 0c05: 1022:790b (rev 61)
00:14.3 0601: 1022:790e (rev 51)
00:18.0 0600: 1022:1440
00:18.1 0600: 1022:1441
00:18.2 0600: 1022:1442
00:18.3 0600: 1022:1443
00:18.4 0600: 1022:1444
00:18.5 0600: 1022:1445
00:18.6 0600: 1022:1446
00:18.7 0600: 1022:1447
01:00.0 0108: 1987:5016 (rev 01)
02:00.0 0604: 1022:57ad
03:03.0 0604: 1022:57a3
03:05.0 0604: 1022:57a3
03:06.0 0604: 1022:57a3
03:08.0 0604: 1022:57a4
03:09.0 0604: 1022:57a4
03:0a.0 0604: 1022:57a4
04:00.0 0200: 10ec:8125
05:00.0 0200: 8086:1539 (rev 03)
06:00.0 0280: 8086:2723 (rev 1a)
07:00.0 1300: 1022:1485
07:00.1 0c03: 1022:149c
07:00.3 0c03: 1022:149c
08:00.0 0106: 1022:7901 (rev 51)
09:00.0 0106: 1022:7901 (rev 51)
0a:00.0 0300: 10de:1086 (rev a1)
0a:00.1 0403: 10de:0e09 (rev a1)
0b:00.0 1300: 1022:148a
0c:00.0 1300: 1022:1485
0c:00.1 1080: 1022:1486
0c:00.3 0c03: 1022:149c
0c:00.4 0403: 1022:1487
0d:00.0 0106: 1022:7901 (rev 51)
0e:00.0 0106: 1022:7901 (rev 51)
... I'm just finding the same device 00:18.nn
which means node 0
and nothing like 00:19.nn
up to 00:1F.nn
I don't expect more solution from the PCI enumeration.
80000008:00000000
0000703f
where 3f
means 63 + 1 = 64 SMT Cores0000701f
where 1f
means 31 + 1 = 32 SMT CoresTo solve a CCD factor:
Example | Avail. Cores | SMT | ECX | factor |
---|---|---|---|---|
3990X | 64 | 128 | 7f ? | 1 |
3970X | 32 | 64 | 3f | 2 |
3960X | 24 | 48 | 2f | 2 |
3950X | 16 | 32 | 1f | 1 |
3900X | 12 | 24 | 17 | 1 |
EDIT: dump found at instlatx64
CPUID 80000008: 00003030-018CB757-0000702F-00010000
CPUID 80000008: 00003030-010EB757-00007017-00010000
and then to apply the CCD_factor into the SMU query
Core_AMD_SMN_Read( TccdSensor,
SMU_AMD_THM_TCTL_CCD_REGISTER_F17H
+ (( CCD_factor * Core->T.Cluster.CCD) << 2),
SMU_AMD_INDEX_REGISTER_F17H,
SMU_AMD_DATA_REGISTER_F17H );
I would also like to count the SMU registers by counting the number of UMC
modprobe msr
rdmsr -aX 0x0000017b
corefreq-cli -M
rdmsr:
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
corefreq-cli -M
Zen UMC [1493]
Controller #0 Quad Channel
Bus Rate 0 MT/s Bus Speed 0 MHz DRAM Speed 0 MHz
Cha CL RCDR RCDW RP RAS RC RRDS RRDL FAW WTRS WTRL WR clRR clWW
#0 18 18 18 18 39 57 4 6 26 3 9 18 3 3
#1 18 18 18 18 39 57 4 6 26 3 9 18 3 3
#2 16 15 14 14 32 46 4 6 20 4 12 12 4 4
#3 16 15 14 14 32 46 4 6 20 4 12 12 4 4
CWL RTP RdWr WrRd scWW sdWW ddWW scRR sdRR ddRR drRR drWW drWR drRRD
#0 12 9 5 1 1 3 3 1 3 3 0 0 0 0
#1 12 9 5 1 1 3 3 1 3 3 0 0 0 0
#2 16 8 8 4 1 7 7 1 5 5 0 0 0 0
#3 16 8 8 4 1 7 7 1 5 5 0 0 0 0
REFI RFC1 RFC2 RFC4 RCPB RPPB sFAW dFAW Ban Page CKE CMD GDM ECC
#0 9360 312 192 132 0 0 0 0 R0W0 0 6 1T OFF 0
#1 9360 312 192 132 0 0 0 0 R0W0 0 6 1T OFF 0
#2 14553 298 192 132 0 0 0 0 R1W1 0 1 1T ON 0
#3 14553 298 192 132 0 0 0 0 R1W1 0 1 1T ON 0
DIMM Geometry for channel #0
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1
DIMM Geometry for channel #1
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1
DIMM Geometry for channel #2
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1 2 16 65536 1024 16384
DIMM Geometry for channel #3
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1 2 16 65536 1024 16384
There should be 2 more memory modules I have actually 4 x 16GB
There should be 2 more memory modules I have actually 4 x 16GB
Very interesting
I have the following output from the MSR:
FFFFFFFFFFFFFFEF
FFFFFFFFFFFFFFEF
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
6F
3950X counts twice the pattern FFFFFFFFFFFFFFEF
whereas 3970X , 8 times
About the UMC, it's still a work in progress.
Thanks for your output, I will check why it does not count 4 DIMMs ?
(Fyi, to format code in Markdown, place 3 anti-quotes before after the code)
Zen UMC [1493]
Controller #0 Quad Channel
Bus Rate 0 MT/s Bus Speed 0 MHz DRAM Speed 0 MHz
Cha CL RCDR RCDW RP RAS RC RRDS RRDL FAW WTRS WTRL WR clRR clWW
#0 18 18 18 18 39 57 4 6 26 3 9 18 3 3
#1 18 18 18 18 39 57 4 6 26 3 9 18 3 3
#2 16 15 14 14 32 46 4 6 20 4 12 12 4 4
#3 16 15 14 14 32 46 4 6 20 4 12 12 4 4
CWL RTP RdWr WrRd scWW sdWW ddWW scRR sdRR ddRR drRR drWW drWR drRRD
#0 12 9 5 1 1 3 3 1 3 3 0 0 0 0
#1 12 9 5 1 1 3 3 1 3 3 0 0 0 0
#2 16 8 8 4 1 7 7 1 5 5 0 0 0 0
#3 16 8 8 4 1 7 7 1 5 5 0 0 0 0
REFI RFC1 RFC2 RFC4 RCPB RPPB sFAW dFAW Ban Page CKE CMD GDM ECC
#0 9360 312 192 132 0 0 0 0 R0W0 0 6 1T OFF 0
#1 9360 312 192 132 0 0 0 0 R0W0 0 6 1T OFF 0
#2 14553 298 192 132 0 0 0 0 R1W1 0 1 1T ON 0
#3 14553 298 192 132 0 0 0 0 R1W1 0 1 1T ON 0
DIMM Geometry for channel #0
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1
DIMM Geometry for channel #1
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1
DIMM Geometry for channel #2
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1 2 16 65536 1024 16384
DIMM Geometry for channel #3
Slot Bank Rank Rows Columns Memory Size (MB)
#0
#1 2 16 65536 1024 16384
The insmod should be enough if acpi_cpufreq is unloaded or am I missing something?
insmod corefreqk.ko Register_CPU_Freq=1 Register_CPU_Idle=1 Experimental=1 Register_Governor=1
dmesg:
cmdline relavant part: idle=halt
kernel config: https://pastebin.com/ja0d9518