Hi@all,
I recognize a wire behavior / issue with my pve installation.
My servers running most likely the same both have an Gigabyte MC12-LE0 with 32GB RAM.
One server has an AMD R5 3600 and the other one an AMD R7 3700x.
I installed pve on a NVME SSD on the server with the R5 3600.
On the server with the R7 3700x, I installed pve on two 240 GB SSD with zfs RAID1.
My issue is ...
when I setup the /etc/default/grub that amd_pstate_epp is enabled
"amd_pstate=active initcall_blacklist=acpi_cpufreq_init"
I got two differents resulte.
R5 3600 - Everything is fine and the CPU is stepping down
R7 3700X - no change and the journalctl -b 0 | grep pstate promt with amd_pstate: driver load is disabled, boot with specific mode to enable this.
I made a crosscheck and installed a fresh pve on the NVME SSD on the R7 3700x and setup the /etc/default/grub with both parameters and is working.
Can somebody explain what happen and why?
I guess that the /etc/default/grub will not be concidered by the boot if you are using a zfs boot pool.
Any ideas how to solve this?
I recognize a wire behavior / issue with my pve installation.
My servers running most likely the same both have an Gigabyte MC12-LE0 with 32GB RAM.
One server has an AMD R5 3600 and the other one an AMD R7 3700x.
I installed pve on a NVME SSD on the server with the R5 3600.
On the server with the R7 3700x, I installed pve on two 240 GB SSD with zfs RAID1.
My issue is ...
when I setup the /etc/default/grub that amd_pstate_epp is enabled
"amd_pstate=active initcall_blacklist=acpi_cpufreq_init"
I got two differents resulte.
R5 3600 - Everything is fine and the CPU is stepping down
R7 3700X - no change and the journalctl -b 0 | grep pstate promt with amd_pstate: driver load is disabled, boot with specific mode to enable this.
I made a crosscheck and installed a fresh pve on the NVME SSD on the R7 3700x and setup the /etc/default/grub with both parameters and is working.
Can somebody explain what happen and why?
I guess that the /etc/default/grub will not be concidered by the boot if you are using a zfs boot pool.
Any ideas how to solve this?