Recent content by jnolla

  1. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    cat /boot/config-5.15.0-91-generic | grep PSTATE CONFIG_X86_INTEL_PSTATE=y CONFIG_X86_AMD_PSTATE=y
  2. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    modinfo amd_pstate name: amd_pstate filename: (builtin) license: GPL file: drivers/cpufreq/amd_pstate description: AMD Processor P-state Frequency Driver author: Huang Rui <ray.huang@amd.com>
  3. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    journalctl -b 0 | grep pstate Jan 29 09:25:17 x1 kernel: Command line: BOOT_IMAGE=/vmlinuz-5.15.0-91-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro i8042.reset quiet nosplash debug intel_pstate=disable amd-pstate=active initcall_blacklist=acpi_cpufreq_init amd_pstate.shared_mem=1 Jan 29...
  4. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    sudo grep . /sys/devices/system/cpu/cpu0/cpufreq/* /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0 /sys/devices/system/cpu/cpu0/cpufreq/bios_limit:3800000 /sys/devices/system/cpu/cpu0/cpufreq/cpb:1 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:2800000...
  5. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    @CyklonDX your information is correct. No one stated this is overclocking the system, just that this in the only value in BIOS we have tweaked to keep clock at 3800Mhz. The issue as stated above is that the system is not respecting when UP limit is set to 3800MHZ ----WORKING AT 2800MHZ----...
  6. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    I am not sure what you are referring too. OC Tweaker if manual, multiplier and voltage will be set based on user selection. If we set to 3800 it will stay at that clock speed.
  7. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    It the same command, does not work. It's either boost enabled or manual clocking, which as per the initial post, it causes all CPU to run at 3800 all the time.
  8. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    cpupower frequency-set -g ondemand -d 1.8GHz -u 3.8GHz This parameter is not working, keep boosting right pass 3.8GHz
  9. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    Thank you for the quick response. How can we configure properly to achieve this? We have no experience with this.
  10. J

    Limit boost to 3800 for Threadripper PRO 5965WX

    Hi Team, We are running into an issue with our Threadripper PRO servers. We are trying to ensure they do not go above 3800 on their boost. We can set the speed manually on the BIOS, but if we want to allow the CPU to run at lower speeds and just boost to 3800, it goes past it up to 4400 causing...
  11. J

    PCIe Gen 4 bifurcation risers and NVMe SSDs

    Some testing on our end: Drives: Micron_9400_MTFDKCC15T3TGH Backplane: BPN-NVME3-216N-S4 Retimer cards: AOC-SLG4-4E4T-O MB: H12SSL-NT sudo zpool status idisk pool: idisk state: ONLINE config: NAME STATE READ WRITE CKSUM idisk ONLINE 0 0 0...
  12. J

    Supermicro H12SSL-i, H12SSL-C, H12SSL-NT, H12SSL-CT boards - notes, experiences

    Learned something new! Thought it would be useful for offline troubleshooting, but really not much help.
  13. J

    Supermicro H12SSL-i, H12SSL-C, H12SSL-NT, H12SSL-CT boards - notes, experiences

    Agreed, and IPMI showed memory as good, so we never thought it would be a memory issue. Took us all day to figure out.
  14. J

    Supermicro H12SSL-i, H12SSL-C, H12SSL-NT, H12SSL-CT boards - notes, experiences

    It was a mistake, not intentionally. They were ECC, just not buffered. We used them on the Threadripper servers, and got mixed. :(
  15. J

    Supermicro H12SSL-i, H12SSL-C, H12SSL-NT, H12SSL-CT boards - notes, experiences

    Thanks everyone, it was the memory. Given the system would not boot up, it would have never applied the new bios. We had installed ECC non buffered. Once we swapped the memory it worked on all BIOS.