Public bug reported: == Comment: #0 - Shilpasri G. Bhat +++ This bug was initially created as a clone of Bug #163527 +++
---Problem Description--- Error in CPU frequency reporting when nominal and min pstates are same The patch for this issue is accepted to linux-next as 3fa4680b860bf48b437d6a2c039789c4abe202ae cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin Some OpenPOWER boxes can have same pstate values for nominal and pmin pstates. In these boxes the current code will not initialize 'powernv_pstate_info.min' variable and result in erroneous CPU frequency reporting. This patch fixes this problem. Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index) Reported-by: Alvin Wang <[email protected]> Signed-off-by: Shilpasri G Bhat <[email protected]> Acked-by: Viresh Kumar <[email protected]> Cc: 4.8+ <[email protected]> # 4.8+ Signed-off-by: Rafael J. Wysocki <[email protected]> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-163614 severity-high targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-163614 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746174 Title: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq) Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Shilpasri G. Bhat +++ This bug was initially created as a clone of Bug #163527 +++ ---Problem Description--- Error in CPU frequency reporting when nominal and min pstates are same The patch for this issue is accepted to linux-next as 3fa4680b860bf48b437d6a2c039789c4abe202ae cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin Some OpenPOWER boxes can have same pstate values for nominal and pmin pstates. In these boxes the current code will not initialize 'powernv_pstate_info.min' variable and result in erroneous CPU frequency reporting. This patch fixes this problem. Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index) Reported-by: Alvin Wang <[email protected]> Signed-off-by: Shilpasri G Bhat <[email protected]> Acked-by: Viresh Kumar <[email protected]> Cc: 4.8+ <[email protected]> # 4.8+ Signed-off-by: Rafael J. Wysocki <[email protected]> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
