@diewald, this seems to have regressed how max CPU freq shows on AMD hosts running 5.15.0-140-generic .
I recompiled `5.15.0-140-generic` without `cpufreq: ACPI: Fix max- frequency computation` and that fixed the issue observed. I reported this upstream to https://lore.kernel.org/all/aDaB63tDvbdcV0cg@HQ-GR2X1W2P57/ The patch was targeted to 6.14 and was merged into 5.15.179 through https://lore.kernel.org/all/2025031356-rerun-remold-30b9@gregkh/ Depending how this goes upstream, could that patch be pulled out of 5.15? I have not checked if this actually impact the CPU effectively available, but it is at least impacting things like container scheduler that now believe the host is roughly half the capacity it used to be causing container scheduling issue for lack of CPU resources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2106026 Title: Jammy update: v5.15.179 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106026/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
