https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #24 from commit-h...@freebsd.org --- A commit references this bug: Author: cem Date: Fri Jan 31 17:40:42 UTC 2020 New revision: 357336 URL: https://svnweb.freebsd.org/changeset/base/357336 Log: hwpstate(4): Ignore CurPstateLimit by default Add a sysctl knob to allow users to re-enable it, and document the knob and default in cpufreq.4. (While here, add a few unrelated updates to cpufreq.4.) It seems that the register value in some hardware simply reflects the configured P-state. This results in an inadvertent and unintended outcome where the P-state can only walk down, and then the driver becomes "stuck" in the slowest possible P-state. The Linux driver never consults this register, so that's some evidence that ignoring the contents are relatively harmless. PR: 234733 Reported by: sigsys AT gmail.com, Erich Dollanksy <freebsd.ed.lists AT sumeritec.com> Changes: head/share/man/man4/cpufreq.4 head/sys/x86/cpufreq/hwpstate_amd.c -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
